cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

This product reached the end of support date on March 31, 2021.

After changing agent platform from Classic to Appmon, Event count is not updating

nagaraju_bollim
Newcomer

Hi,


Recently, in some of our application servers the platform is changed from Oracle to Open JDK 11. As this version is not supported by Classic agent, monitoring is not working for these servers.

So, we have changed the Agent platform of a particular agent from Classic to Appmon. After the java process is restarted, we have seen that the status is "Invalid Instrumentation state". The next day, when we have checked the status is "Online". But, the event count is not getting updated.

We have taken the restart of the java process again and the status is currently "Invalid Instrumentation state" and the event count is still not updating. But we can see the JVM thread count.

The Agent Bootstrap version is 7.0.0.2469 and the Agent version is 7.2.16.1026.


In the server log, we found the below warning.

WARNING [UnusualEventTimeLogger] The timestamp '2019-10-18 00:37:55' (UTC) of event 'EnhancedHostPerformanceEventRecord' lies in the past. There may be an issue with the time synchronization with agent 'Agent name'. Event details:

EnhancedHostPerformanceEventRecord[


can anyone please let me know how to troubleshoot this issue.


Regards,

Nagaraju


3 REPLIES 3

Joe_Hoffman
Dynatrace Leader
Dynatrace Leader

I find it interesting that the log message shows "Agent Name", rather than the real agent. This makes me think there's something not right about that agent. Have you tried deleting and reinstalling the agent on that host?

Another idea: Is the time on the monitored host significantly different than the AppMon Server?


nagaraju_bollim
Newcomer

Hi Joseph,


I have replaced the real agent with " Agent name" in the warning.

I have installed the new agent on the host. It shows the same issue.

The time on the monitored host and the Appmon server is the same.


Regards,

Nagaraju


The next place I would look is the agent log files.

Otherwise I suggest you open a support case.