Splunk AppDynamics

Latest RabbitMQ monitoring extension error

Bazza_12
Path Finder

Seem to be getting an error with the latest RabbitMQ extension - appears as though the username is being substituted for the host url

11:36:22,606  INFO [main] Http4ClientBuilder - Creating the auth scope for host [xxxx.rabbitmq.xxxxxx.net] and port [xxx]
11:36:22,606 DEBUG [main] Http4ClientBuilder - Read the [encryptionKey] from config.yml
11:36:22,715  INFO [main] Http4ClientBuilder - Created credentials for auth scope <any realm>@xxxx.rabbitmq.xxxxxx.net:xxx
11:36:22,793 DEBUG [main] PathResolver - The install directory is resolved to D:\machineagent-bundle-64bit-windows-4.3.5.13
11:36:22,793 DEBUG [main] FileWatchListenerModule - The path [monitors/RabbitMQMonitor/metrics.xml] is resolved to file D:\machineagent-bundle-64bit-windows-4.3.5.13\monitors\RabbitMQMonitor\metrics.xml
11:36:22,824 DEBUG [main] MonitorConfiguration - Attempting to unmarshall the file D:\machineagent-bundle-64bit-windows-4.3.5.13\monitors\RabbitMQMonitor\metrics.xml into com.appdynamics.extensions.rabbitmq.config.input.Stat$Stats
11:36:22,840  INFO [main] MonitorConfiguration - Reloaded the metrics xml [com.appdynamics.extensions.rabbitmq.config.input.Stat$Stats@1b3ee4e] successfully from D:\machineagent-bundle-64bit-windows-4.3.5.13\monitors\RabbitMQMonitor\metrics.xml
11:36:22,840 DEBUG [main] AMonitorJob - Monitor RabbitMQ Monitor Task Runner invoked
11:36:22,840  INFO [main] MetricWriteHelperFactory - The instance of MetricWriteHelperFactory is com.appdynamics.extensions.workbench.metric.WorkbenchMetricStore@1d4937b
11:36:23,043 DEBUG [Monitor-Task-Thread1] RabbitMQMonitorTask - Registering MetricCollectorTask phaser for TestRabbitMQ
11:36:23,043 DEBUG [Monitor-Task-Thread1] RabbitMQMonitorTask - Registering OptionalMetricCollectorTask phaser for TestRabbitMQ
11:36:23,043 DEBUG [Monitor-Task-Thread2] UrlBuilder - The url is initialized to https://yyy-yyy-yyyyy-yyyyyyy:xxx/api/nodes

This gives the following error

11:36:35,429 ERROR [Monitor-Task-Thread2] HttpClientUtils - Exception while executing the request [https://yyy-yyy-yyyyy-yyyyyyy:xxx/api/nodes]
java.net.UnknownHostException: yyy-yyy-yyyyy-yyyyyyy
 at java.net.Inet6AddressImpl.lookupAllHostAddr(Native Method)
 at java.net.InetAddress$2.lookupAllHostAddr(Unknown Source)
 at java.net.InetAddress.getAddressesFromNameService(Unknown Source)
 at java.net.InetAddress.getAllByName0(Unknown Source)
 at java.net.InetAddress.getAllByName(Unknown Source)
 at java.net.InetAddress.getAllByName(Unknown Source)
 at org.apache.http.impl.conn.SystemDefaultDnsResolver.resolve(SystemDefaultDnsResolver.java:45)
 at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:111)
 at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:353)
 at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:380)
 at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:236)
 at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:184)
 at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:88)
 at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110)
 at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184)
 at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
 at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:107)
 at com.appdynamics.extensions.http.HttpClientUtils.getResponse(HttpClientUtils.java:119)
 at com.appdynamics.extensions.http.HttpClientUtils.getResponseAsJson(HttpClientUtils.java:68)
 at com.appdynamics.extensions.http.HttpClientUtils.getResponseAsJson(HttpClientUtils.java:45)
 at com.appdynamics.extensions.rabbitmq.metrics.MetricsCollector.run(MetricsCollector.java:88)
 at com.appdynamics.extensions.MonitorThreadPoolExecutor$2.run(MonitorThreadPoolExecutor.java:102)
 at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
 at java.lang.Thread.run(Unknown Source)

The yaml file is correct & checked

servers:

   - host: "xxxx.rabbitmq.xxxxxx.net"
     port: xxx
     useSSL: true
     username: "yyy-yyy-yyyyy-yyyyyyy"

Labels (1)
0 Karma
1 Solution

Akshay_Srivasta
Engager

Hello Barry,

We have just updated our community page with a new build, please try that build. 

https://www.appdynamics.com/community/exchange/extension/rabbitmq-monitoring-extension/

This issue has been fixed with the latest build. Please try this and let us know.

Thanks,

Akshay

View solution in original post

Akshay_Srivasta
Engager
Hello Barry, We would suggest to create a helpdesk ticket for quicker response. In the helpdesk ticket, please attach the config.yml file you are using and provide complete machine agent DEBUG level logs. Thanks, Akshay
0 Karma

Akshay_Srivasta
Engager

Hello Barry,

We have just updated our community page with a new build, please try that build. 

https://www.appdynamics.com/community/exchange/extension/rabbitmq-monitoring-extension/

This issue has been fixed with the latest build. Please try this and let us know.

Thanks,

Akshay

Bazza_12
Path Finder
Hi Akshay

Thanks that is better I am getting stats now without any issues.

Barry
0 Karma
Get Updates on the Splunk Community!

Splunk Observability Synthetic Monitoring - Resolved Incident on Detector Alerts

We’ve discovered a bug that affected the auto-clear of Synthetic Detectors in the Splunk Synthetic Monitoring ...

Video | Tom’s Smartness Journey Continues

Remember Splunk Community member Tom Kopchak? If you caught the first episode of our Smartness interview ...

3-2-1 Go! How Fast Can You Debug Microservices with Observability Cloud?

3-2-1 Go! How Fast Can You Debug Microservices with Observability Cloud? Learn how unique features like ...