Skip to content

Latest commit

 

History

History
146 lines (118 loc) · 8.12 KB

README.md

File metadata and controls

146 lines (118 loc) · 8.12 KB
Raw

AppDynamics RabbitMQ Monitoring Extension:

Use Case

RabbitMQ is open source message broker software that implements the Advanced Message Queuing Protocol (AMQP). The RabbitMQ Monitoring extension collects metrics from an RabbitMQ management API and uploads them to the AppDynamics Controller.

Prerequisite

The RabbitMQ Management Plugin must be enabled. Please refer to this page for more details.

In order to use this extension, you do need a Standalone JAVA Machine Agent or SIM Agent. For more details on downloading these products, please visit here.

The extension needs to be able to connect to RabbitMQ in order to collect and send metrics. To do this, you will have to either establish a remote connection in between the extension and the product, or have an agent on the same machine running the product in order for the extension to collect and send the metrics.

Installation

  1. Download and unzip the RabbitMQMonitor.zip to the "<MachineAgent_Dir>/monitors" directory
  2. Edit the file config.yml as described below in Configuration Section, located in <MachineAgent_Dir>/monitors/RabbitMQMonitor and update the RabbitMQ server(s) details.
  3. All metrics to be reported are configured in metrics.xml. Users can remove entries from metrics.xml to stop the metric from reporting.
  4. Restart the Machine Agent

Please place the extension in the "monitors" directory of your Machine Agent installation directory. Do not place the extension in the "extensions" directory of your Machine Agent installation directory.

Configuration

  1. Configure the "tier" under which the metrics need to be reported. This can be done by changing the value of <TIER ID> in metricPrefix: "Server|Component:<TIER ID>|Custom Metrics|RabbitMQ". For example, 
    metricPrefix: "Server|Component:Extensions tier|Custom Metrics|RabbitMQ"
  2. Configure the RabbitMQ instances by specifying the name(required), host(required), port(required) of the RabbitMQ instance, password (only if authentication enabled), encryptedPassword(only if password encryption required). You can configure multiple instances as follows to report metrics For example, 
    servers:
  - host: "localhost"
    port: 15672
    useSSL: false
    username: "guest"
    password: "guest"
    ##passwordEncrypted : Encrypted Password to be used, In this case do not use normal password field as above
    displayName: "displayName1" //The display name to be used for the metrics of this server, mandatory

  - host: "localhost"
    port: 15673
    useSSL: false
    username: "guest"
    password: "guest"
    displayName: "displayName2" //The display name to be used for the metrics of this server, mandatory

connection:
 socketTimeout: 10000
 connectTimeout: 10000
  3. Configure the encyptionKey for encryptionPasswords(only if password encryption required). For example, 
    #Encryption key for Encrypted password.
encryptionKey: "axcdde43535hdhdgfiniyy576"
  4. Configure the numberOfThreads For example, If number of servers that need to be monitored is 3, then number of threads required is 5 * 3 = 15 
    numberOfThreads: 15
  5. Queue Group Configuration: The queue can be grouped and the metrics for the group of queues can be collected with this feature. The grouping can be used for a scenario where there was a large number of Queues(20+) and they were very short lived (hours to couple of days). Another use case if for example, there are 10 queues working on 'order placement' and 5 queues working on 'user notification', then you can create a group for 'order placement' and get the collective stats. The queue stats will be grouped by the 'groupName' if the 'queueNameRegex' matches the name of the Queue. Example: 
    queueGroups:
  # The stats from Queues matched by the 'queueNameRegex' will be reported under groupName
- groupName: group1
  # A Regex to match the Queue Name
  queueNameRegex: queue.+
  # showIndividualStats  If set to false then the Individual Queue stats will not be reported.This will help if there are several short lived queues and an explosion of metrics in the controller can be avoided
  showIndividualStats: false

- groupName: group2
  queueNameRegex: temp.+
  showIndividualStats: true
  6. Include Filters: Use the regex in includes parameters of filters, to specify the nodes/queues you'd like to collect metrics on. Be default, the config.yml has includes filter set to include all nodes/queues. 
    filter:
  nodes:
    includes: [".*"]
  queues:
    includes: [".*"]
  7. EndPoint Flags: Use endpoint-flags to enable/disable(set flag to true/false) metrics for overview and federation-plugin of RabbitMQ. 
    endpointFlags:
   federationPlugin: "false"
   overview: "true"

Extension Generic Information

Credentials Encryption

Please visit this page to get detailed instructions on password encryption. The steps in this document will guide you through the whole process.

Extensions Workbench

Workbench is an inbuilt feature provided with each extension in order to assist you to fine tune the extension setup before you actually deploy it on the controller. Please review the following document on How to use the Extensions WorkBench

Troubleshooting

  1. Please ensure the RabbitMQ Management Plugin is enabled. Please check "" section of this page for more details.
  2. Please follow the steps listed in this troubleshooting-document in order to troubleshoot your issue. These are a set of common issues that customers might have faced during the installation of the extension. If these don't solve your issue, please follow the last step on the troubleshooting-document to contact the support team.

Support Tickets

If after going through the Troubleshooting Document you have not been able to get your extension working, please file a ticket and add the following information.

Please provide the following in order for us to assist you better.

1. Stop the running machine agent.
2. Delete all existing logs under <MachineAgent>/logs.
3. Please enable debug logging by editing the file <MachineAgent>/conf/logging/log4j.xml. Change the level value of the following <logger> elements to debug.
    <logger name="com.singularity">
    <logger name="com.appdynamics">
4. Start the machine agent and please let it run for 10 mins. Then zip and upload all the logs in the directory <MachineAgent>/logs/*.
5. Attach the zipped <MachineAgent>/conf/* directory here.
6. Attach the zipped <MachineAgent>/monitors/ExtensionFolderYouAreHavingIssuesWith directory here.

For any support related questions, you can also contact help@appdynamics.com.

Contributing

Always feel free to fork and contribute any changes directly here on GitHub.

Version

Name Version
Extension Version 2.0.0
Controller Compatibility 3.7 or Later
Product Tested On 3.2.0+
Last Update 03/021/2018