My concern related to logs are getting in server.
DT Envoirnment: 7.0.14
1. Server logs file has filled with below log line:
"Unable to find transformation with id 6580984353170462056 for agent agentname:21738. The event will not be correlated on the server Suppressing this warning for another 60000 ms." - why is it coming and How will it affect?
Cannot set sensortype capture exclude list on disconnected agent agentName:27007: com.dynatrace.diagnostics.collector.agentcenter.AgentPeer setBlackListGlobalSensorTypeCapture:1462 -- Saw as severe log, Why it has backlisted?
"Error setting up an agent connection from 'agentName:25478' at 'x.x.x.41:52834': Software caused connection abort: socket write error" -- It is coming when agents are trying to connect with collector and after above error it's showing agent connected without instrumentation.
Kindly check the above logs, what is the reason behind these logs, and provide the solution for same.
Ashutosh Kumar Singh
Hello do you have any firewall between agents and collector? If yes this is possible that connection is to slow and instrumentation process is failing. This is because collector is making class browsing, instrummenting bytcode and return code back to server. In such case high network load can be generated. So please check if there is firewall if yes be sure that nothing is determining network performance. If this doesn’t help make support archive and open support ticket.
Hello @Ashutosh S.
A firewall introduces latency in the calls between the Agent and Collector. This is often the reason for slow application start-up. The Agent needs to do several 10,000 round trips to the Collector at application start up. Even 1 ms firewall latency adds up to a noticeable time. Therefore, either use a real fast (in latency time) firewall or put the Collector into the same subnet as the Agents.
In the Agents Overview, add two more columns of Average Instrumentor Response Time and Maximum Instrumentor Response Time. Usually maximum time should not be more than 100 ms.
Have a look on the below link for Collector best practices.