Correlation Log: Skipping events for agentId not registered on server
Hi,
We see many log entry for Skipping events in Server Correlation log.
2015-09-17 09:15:52 WARNING [CollectorPeer$CorrelationLog] [CollectorPeer] Received events for agent (agentId: fd031113) from collector <collector name> at host <collector host> that is not registered on server. Skipping events.
2015-09-17 09:15:52 WARNING [CollectorPeer$CorrelationLog] [CollectorPeer] Received events for agent (agentId: fd031113) from collector <collector name> at host <collector host> that is not registered on server. Skipping events.
2015-09-17 09:15:52 WARNING [CollectorPeer$CorrelationLog] [CollectorPeer] Received events for agent (agentId: fd031113) from collector <collector name> at host <collector host> that is not registered on server. Skipping events.
Could it have caused due to an app restart? in that case why is agent and server not synchronizing with the new agent id.
-Sreerag
Do you know which agent that is? Check the Agents Overview to see if the agent is there (agent id is a column in the dashboard that you can unhide). And check the other logs such as the Collector logs.
You might consider opening a support ticket.
-- Graeme
Collectoe log has the entry with the agent id in the correlation log. However the agent has a new id and the correlation log has the old agent id. We also have seen that a restart of app process fixes this. I'm trying to find why is this happening and how is it getting fixed by app restart. if it is an id mismatch why is dynatrace agent and server fixing the mismatch automatically. Or at least have an option in server so that dynatrace admin can force the agent id sync with server.
-Sreerag
Welcome the
Dynatrace Community Forums
Check out the Forum User Guide and Forum Guidelines to learn how to get started.Community Member of the Month
August 2017
Announcing Dynatrace's Community Member of the Month for August 2017, Rick B.! Click here to read more! 
