Classes are not visible in Class Browser.
We added a new system profile to Dynatrace Server. We were trying to manually add sensors, when we tried to search for Classes using Class Browser, it doesn't search for any class. Is there a setting that needs to be done in the System Profile?
We are in 7.1.13
I had a similar problem several times.
The following steps helped:
1. Collector restart
2. Restarting agents (remember that class browsing is done at the application startup)
Hello Devi,
Would request you to select appropriate agent group when you try to reach for your classed in custom sensor placement. Also you may try to reach with "By Package" option to browser all the package, class & methods.
If you know & are very much sure about your package, class & method name for a particular jvm then there is option to manually add the class for custom sensor capturing.
e.g " com.abc.test.hif.xyz.socket.testconnectionhandler"
Edit profile --> sensors --> select sensor group or add new sensor group --> click on " Add Class..." buttion --> specify the class pattern --> change the match case as per your requirement --> specify the class annotations (check with you developer for this) --> click ok.
& in same way you need to add the method selecting the class.
Then once hot sensor or agent restart is done then check the method in method dashboard.
Cheers,
Ramesh
The agent of that JVM needs to be connected at the time you're querying the class list. Can you verify it's visible in Agent Overview?
There is no setting to allow this in the system profile, but you might want to try it from a user who's an Admin just to be sure it's not a privilege limitation.
Yes the agents are visible in the Agent Overview with the status - "Connected (Hot Sensor Placement available)" status.
If Radoslow's suggestions don't provide any solutions, look at the agent logs and see if there's any messages to indicate why this is happening.
Yes, I know that this is not a solution, but a quick workaround to run a monitoring. We had very similar situations on many enviroments that long-term collectors at some point lost their cache files. Restart caused a quick rebuild of the cache file. Of course, I agree with this to investigate the problem in collector and agent logs.
