AppDynamics Monitoring Extension for use with Elasticsearch

1. Use Case

Elasticsearch is a distributed RESTful search server based on Lucene which provides a distributed multitenant-capable full text search engine. This extension collects cluster health metrics, nodes and indices stats from a Elasticsearch engine and presents them in AppDynamics Metric Browser.

Note: This extension works with a Java Machine Agent.

2. Prerequisites

Before the extension is installed, the prerequisites mentioned here need to be met. Please do not proceed with the extension installation if the specified prerequisites are not met.

3. Installation

  1. Download the file into <machineagent install dir>/monitors/
  2. Unzip the downloaded file
  3. Edit the file config.yml located at <MachineAgent_Dir>/monitors/ The metricPrefix of the extension has to be configured as specified here. Please make sure that the right metricPrefix is chosen based on your machine agent deployment, otherwise this could lead to metrics not being visible in the controller.
  4. In <machineagent install dir>/monitors/ElasticSearchMonitor/, open config.yml and configure the ElasticSearch parameters.
         - displayName: Server1
           uri: "http://localhost:9200"
           username: ""
           password: "" 
           #passwordEncrypted: ""    
    # To get the metrics through CAT apis
      - endPoint: "/_cat/health?v&h=cluster,st,nodeTotal,nodeData,shardsTotal,shardsPrimary,shardsRelocating,shardsInitializing,shardsUnassigned,pendingTasks"
        metricPrefix: "Cluster Stats"
        metricKeys: [
      - endPoint: "/_cat/allocation?v&bytes=b&h=node,shards,diskUsed,diskAvailable,diskTotal,diskPercent"
        # Any prefixes
        metricPrefix: "Allocation"
        # The keys to be used in metric path. Picks up in the same order.
        metricKeys: [
      - endPoint: "/_cat/indices?v&bytes=b&time=s&h=index,health,status,shardsPrimary,shardsReplica,docsCount,docsDeleted,storeSize,,searchQueryTime,searchQueryTotal,searchQueryCurrent,searchFetchTotal,searchFetchTime,searchFetchCurrent,indexingIndexTotal,indexingIndexTime"
        metricPrefix: "Indices"
        metricKeys: [
      - endPoint: "/_cat/recovery?v&bytes=b&h=index,shard,files,files_percent,bytes,bytes_percent"
        metricPrefix: "Recovery"
        metricKeys: [
      - endPoint: "_cat/thread_pool?v&bytes=b&h=host,,bulk.size,bulk.queue,bulk.queueSize,bulk.rejected,bulk.largest,bulk.completed,bulk.min,bulk.max"
        metricPrefix: "ThreadPool"
        metricKeys: [
      - endPoint: "/_cat/shards?v&bytes=b&h=node,index,shard,docs,store"
        metricPrefix: "Shards"
        metricKeys: [
    #encryptionKey: ""
         socketTimeout: 2000
         connectTimeout: 2000   
    # number of concurrent tasks.
    # This doesn't need to be changed unless many instances are configured
    numberOfThreads: 5     
  5. Restart the Machine Agent.

In the AppDynamics Metric Browser, look for: Application Infrastructure Performance | <Tier> | Individual Nodes | <Node> | Custom Metrics | Elastic Search

4. Metrics

Cat Level Statistics: As mentioned

5. WorkBench

Workbench is a feature that lets you preview the metrics before registering it with the controller. This is useful if you want to fine tune the configurations. Workbench is embedded into the extension jar. To use the workbench

  1. Follow all the installation steps
  2. Start the workbench with the command java -jar /path/to/MachineAgent/monitors/MarkLogicMonitor/elasticsearch-monitoring-extension.jar This starts an http server at http://host:9090/. This can be accessed from the browser.
  3. If the server is not accessible from outside/browser, you can use the following end points to see the list of registered metrics and errors. #Get the stats curl http://localhost:9090/api/stats #Get the registered metrics curl http://localhost:9090/api/metric-paths
  4. You can make the changes to config.yml and validate it from the browser or the API
  5. Once the configuration is complete, you can kill the workbench and start the Machine Agent

6. Password Encryption Support

To avoid setting the clear text password in the config.yml, please follow the process to encrypt the password and set the passwordEncrypted and the encryptionKey in the config.yml

  1. Download the util jar to encrypt the password from here
  2. Encrypt password from the commandline
    java -cp "appd-exts-commons-1.1.2.jar" com.appdynamics.extensions.crypto.Encryptor encryptionKey password
  3. These values should be used in the passwordEncrypted and encryptionKey fields in config.yml instead of plain text password

7. Troubleshooting

  1. Please look at the troubleshooting document and make sure that everything is followed correctly.
  2. Verify Machine Agent Data: Please start the Machine Agent without the extension and make sure that it reports data. Verify that the machine agent status is UP and it is reporting Hardware Metrics.
  3. Metric Limit: If there is a metric limit reached error in the logs, please follow the instructions mentioned here
  4. Collect Debug Logs: Edit the file, <MachineAgent>/conf/logging/log4j.xml and update the level of the appender com.appdynamics and com.singularity to debug.

8. Custom Dashboard

9. Contributing

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

9. Support

For any support questions, please contact






Last Update:



2.0 - Added support for CAT apis.

2.1 - Added support for Authentication.

2.2 - Default node stats uri changed to ES ver 1.0

2.3 - Support for additional metrics

2.4 - Added cluster status metric and moved cat endpoints to global

2.4.1 - Updated Licenses, fix for comma in metric path