I am trying to push some custom metrics into AppDynamics but without success so far. I discovered that, in order to push custom metrics (our blockchain metrics), I had to first push metrics from one of your agents. I decided to take the simple root and deploy a basic Hello World microservice in Python using Flask. It is publicly available at (https://helloflask.ocyan.
Despite doing that and following AppD documentation I still get the followin error:
14:19:00,000 WARN [AD Thread-Metric Reporter1] MetricHandler - Metric Reporter Queue full. Dropping metrics.
14:19:02,394 INFO [AD Thread Pool-Global0] ConfigurationChannel - Detected node meta info: [Name:ProcessID, Value:9, Name:appdynamics.ip.addresses, Value:10.0.2.143]
14:19:02,394 INFO [AD Thread Pool-Global0] ConfigurationChannel - Sending Registration request with: Application Name [cs-beta], Tier Name [hello-world], Node Name [node 103f], Host Name [3b564073aee2] Node Unique Local ID [node 103f], Version [Python Agent v4.5.2.0 (proxy v4.5.13.27004, agent-api v4.3.5.0)]
14:19:02,653 ERROR [AD Thread Pool-Global0] ConfigurationChannel - Fatal transport error while connecting to URL [/controller/instance/0/
14:19:02,653 WARN [AD Thread Pool-Global0] ConfigurationChannel - Could not connect to the controller/invalid response from controller, cannot get initialization information, controller host [customername.saas.appdynamics.com], port[443], exception [Fatal transport error while connecting to URL [/controller/instance/0/
14:19:02,653 WARN [AD Thread Pool-Global0] AgentErrorProcessor - Agent error occurred, [name,transformId]=[com.
14:19:02,653 WARN [AD Thread Pool-Global0] AgentErrorProcessor - 0 instance(s) remaining before error log is silenced
14:19:02,653 ERROR [AD Thread Pool-Global0] ConfigurationChannel - Exception: customername.saas.appdynamics.com:443 failed to respond
org.apache.http.
at org.apache.http.impl.conn.
at org.apache.http.impl.conn.
at org.apache.http.impl.io.
at org.apache.http.impl.
at org.apache.http.impl.conn.
at org.apache.http.protocol.
at org.apache.http.protocol.
at org.apache.http.impl.
at org.apache.http.impl.
at org.apache.http.impl.
at org.apache.http.impl.
at org.apache.http.impl.client.
at org.apache.http.impl.client.
at com.singularity.ee.util.
at com.singularity.ee.util.
at com.singularity.ee.rest.f.G(f.
at com.singularity.ee.rest.f.F(f.
at com.singularity.ee.rest.
at com.singularity.ee.rest.
at com.singularity.ee.agent.
at com.singularity.ee.agent.
at com.singularity.ee.agent.
at com.singularity.ee.agent.
at com.singularity.ee.agent.
at com.singularity.ee.util.
at java.util.concurrent.
at com.singularity.ee.util.
at com.singularity.ee.util.
at com.singularity.ee.util.
at com.singularity.ee.util.
at com.singularity.ee.util.
at com.singularity.ee.util.
at com.singularity.ee.util.
Any idea how to fix that? Any help is appreciated!
Thanks,
Gabriele
^ Post edited by @Ryan.Paredez to remove Controller URL info. Please do not share your Controller URL in community posts for security and privacy reasons.
I am trying to push some custom metrics into AppDynamics but without success so far. I discovered that, in order to push custom metrics (our blockchain metrics), I had to first push metrics from one of your agents. I decided to take the simple root and deploy a basic Hello World microservice in Python using Flask. It is publicly available at (https://helloflask.ocyan.
Despite doing that and following AppD documentation I still get the followin error:
14:19:00,000 WARN [AD Thread-Metric Reporter1] MetricHandler - Metric Reporter Queue full. Dropping metrics.
14:19:02,394 INFO [AD Thread Pool-Global0] ConfigurationChannel - Detected node meta info: [Name:ProcessID, Value:9, Name:appdynamics.ip.addresses, Value:10.0.2.143]
14:19:02,394 INFO [AD Thread Pool-Global0] ConfigurationChannel - Sending Registration request with: Application Name [cs-beta], Tier Name [hello-world], Node Name [node 103f], Host Name [3b564073aee2] Node Unique Local ID [node 103f], Version [Python Agent v4.5.2.0 (proxy v4.5.13.27004, agent-api v4.3.5.0)]
14:19:02,653 ERROR [AD Thread Pool-Global0] ConfigurationChannel - Fatal transport error while connecting to URL [/controller/instance/0/
14:19:02,653 WARN [AD Thread Pool-Global0] ConfigurationChannel - Could not connect to the controller/invalid response from controller, cannot get initialization information, controller host [customername.saas.appdynamics.com], port[443], exception [Fatal transport error while connecting to URL [/controller/instance/0/
14:19:02,653 WARN [AD Thread Pool-Global0] AgentErrorProcessor - Agent error occurred, [name,transformId]=[com.
14:19:02,653 WARN [AD Thread Pool-Global0] AgentErrorProcessor - 0 instance(s) remaining before error log is silenced
14:19:02,653 ERROR [AD Thread Pool-Global0] ConfigurationChannel - Exception: customername.saas.appdynamics.com:443 failed to respond
org.apache.http.
at org.apache.http.impl.conn.
at org.apache.http.impl.conn.
at org.apache.http.impl.io.
at org.apache.http.impl.
at org.apache.http.impl.conn.
at org.apache.http.protocol.
at org.apache.http.protocol.
at org.apache.http.impl.
at org.apache.http.impl.
at org.apache.http.impl.
at org.apache.http.impl.
at org.apache.http.impl.client.
at org.apache.http.impl.client.
at com.singularity.ee.util.
at com.singularity.ee.util.
at com.singularity.ee.rest.f.G(f.
at com.singularity.ee.rest.f.F(f.
at com.singularity.ee.rest.
at com.singularity.ee.rest.
at com.singularity.ee.agent.
at com.singularity.ee.agent.
at com.singularity.ee.agent.
at com.singularity.ee.agent.
at com.singularity.ee.agent.
at com.singularity.ee.util.
at java.util.concurrent.
at com.singularity.ee.util.
at com.singularity.ee.util.
at com.singularity.ee.util.
at com.singularity.ee.util.
at com.singularity.ee.util.
at com.singularity.ee.util.
at com.singularity.ee.util.
Any idea how to fix that? Any help is appreciated!
Thanks,
Gabriele
^ Post edited by @Ryan.Paredez to remove Controller URL info. Please do not share your Controller URL in community posts for security and privacy reasons.
do you have a solution? I have a same issue
Did your issue got resolved? i am having the same issue with the DMZ servers.