Comments have been closed on this page. Please use AppMon & UEM Open Q & A forum for questions about this plugin.



The Dynatrace FastPack for Elasticsearch provides a plugin for Dynatrace which collects various metrics from an Elasticsearch Cluster and sends them to a Dynatrace instance. It also provides a System Profile and a sample Dashboard which visualizes some of the metrics.

Name and Version

Elasticsearch Plugin

Compatible with

Dynatrace 6.2.0+

Elasticsearch 1.3+ (tested 1.3.9, 1.4.5, 1.5.2, 1.6.2, 1.7.5, 2.0.2, 2.1.1, 2.2.2, 2.3.5, 2.4.2, 5.0.2)


Dominik Stadler


Dynatrace BSD

Support Level

Not Supported

Report an Issue


Fix Pack Content

Fastpack download contains:

  • Plugin
  • Dashboard "Elasticsearch" (see below)
  • Profile "Elasticsearch"


Install the plugin

Download the .dtp file and install it on the Dynatrace Server via Tools -> Manage Plugins... -> Install Plugin...

Configure the Elasticsearch Monitor

Configure the provided scheduled task for the Elasticsearch Monitor and define the hostname/port of the Elasticsearch REST interface. The default port number is 9200 unless it was changed in the Elasticsearch configuration.

Optional: Inject Agents in Elasticsearch Nodes

If you want additional metrics like CPU usages, JVM memory and other host/process level metrics you can inject the Dynatrace Agent and use the provided Agent Mapping "Elasticsearch", then some of the process/host-level Dashlets in the Dashboard will show additional information.

System profile/Dashboards

The plugin also includes a system profile 'Elasticsearch' and a Dashboard 'Elasticsearch' with some sample Dashlets.


The plugin provides a number of metrics. The provided System Profile and Dashboard show how you can use them for visualizing various relevant metrics from Elasticsearch. Additionally other functionality like Incidents and Business Transactions can be used to further process or alert on these metrics.



  • Some of the measures only became available in later versions of Elasticsearch, thus if you run an older version of Elasticsearch, some measures might not be populated.
  • The default Scheduled Task is set to run every minute. We saw some overhead of the REST status-calls when an Elasticsearch cluster has a lot of Indexes/Shards, so using shorter time-frames might put some additional load on the cluster.


Feel free to contribute changes or report issues on the GitHub repository


#trackbackRdf ($trackbackUtils.getContentIdentifier($page) $page.title $trackbackUtils.getPingUrl($page))