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

db-agent doesnt work

SRE.DevNet
Builder

Hello AppDynamics Expert,

There is some issue with our AppDynamics DB Agent. It was working fine 2 weeks ago. I can confirm the network is okay for both the AppD controller and AWS database, and the credential of DB is good, too. But agent.log keeps repeating the below log :
———————
[AD Thread-Metric Reporter1] 28 Apr 2021 07:36:05,475 INFO SystemAgentTransientEventChannel - Full certificate chain validation performed using default certificate file
[AD Thread-Metric Reporter1] 28 Apr 2021 07:36:05,498 ERROR MetricService - HTTP Request failed: HTTP/1.1 500 Internal Server Error
[AD Thread-Metric Reporter1] 28 Apr 2021 07:36:05,499 WARN MetricService - Error sending metric data to controller:null
[AD Thread-Metric Reporter1] 28 Apr 2021 07:36:05,499 ERROR MetricService - Error sending metrics - will requeue for later transmission
com.singularity.ee.agent.commonservices.metricgeneration.metrics.MetricSendException: null
at com.singularity.ee.agent.commonservices.metricgeneration.AMetricSubscriber.publish(AMetricSubscriber.java:350) ~[agent-shared-20.3.0.1.jar:?]
———————

I see a lot of people have the same issue when I google the issue but no resolution yet. Do you have any idea?

2 REPLIES 2

Ryan.Paredez
Community Manager

Hello @SRE.DevNet,

 

After speaking to a co-worker it was suggested you reach out to support for this issue. You can reach them by going to help.appdynamics.com.

 

If you are able to learn anything from the chat with support, please come back and share that knowledge here. Peer to peer support and knowledge sharing are what drives the community.


Thanks,

Ryan, Cisco AppDynamics Community Manager




Found something helpful? Click the Accept as Solution button to help others find answers faster.

Liked something? Click the Thumbs Up button.



Check out Observabiity in Action

new deep dive videos weekly in the Knowledge Base.

Jenna.Ipock
Voyager

Did you find a solution to this issue?  We are having the same problem and have been working with support for 5 days now trying to figure it out.