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

Agent is Connected (Issue: Instrumentation is not available.)

supriya_kamble
Participant

Please find attached snaps of error details with server logs.

error1.pngerror2.pngerror3.png

6 REPLIES 6

Enrico_F
Pro

Did you try restarting the instrumented JBoss process? If it doesn't help and you get the same error messages again try restarting the collector if that's feasible for you.

We had a similar issue a few days ago and above steps helped.

Babar_Qayyum
Leader

Hello Supriya,

Do the following steps:

  • Restart the application/agent one more time and it should fix your problem but if it does not fix then
  • Add the 'wait=60' end of your Java Argument and restart the application/agent one more time

Regards,

Babar

Hi

it is taking too long to connect to your collector. I can think of 3 possibilities:

1) the collector is not powerful enough to service the request

2) the network latency is too high.

3) if you are using collector groups, you might have multiple network interfaces on the collector and some of them are not reachable from the agents. Explicitly defining the listen address will fix this.

For point 1), I saw this recently with a collector running on a VM deployed on a server which was totally saturated.

For point 2), Don't forget that the collector and agent must be "close" to each other (ideally on the same subnet and no firewall in between).

For point 3), if you do have multiple IPs (public , backup or management network for instance), specify the public IP in the advanced screen of the collector configuration screen under override external address.

supriya_kamble
Participant

Hi Babar,

Please find below tracert detailstracert.png

Hello Supriya,

Did you get a chance to restart the agent and collector?

If you already have done the above and issue still persist then you can share the collector logs with us.

Regards,

Babar

adam_gardner
Dynatrace Champion
Dynatrace Champion

The fact that the agent seems to connect and then the connection drops, could this be a collector restart issue? Anything useful in the collector logs?