Skip to main content

Prometheus Emitter

To use this Apache Druid extension, include prometheus-emitter in the extensions load list.


This extension exposes Druid metrics for collection by a Prometheus server (

Emitter is enabled by setting druid.emitter=prometheus configs or include prometheus in the composing emitter list.


All the configuration parameters for the Prometheus emitter are under druid.emitter.prometheus.

druid.emitter.prometheus.strategyThe strategy to expose prometheus metrics.
Should be one of exporter and pushgateway. Default strategy exporter would expose metrics for scraping purpose. Peon tasks (short-lived jobs) should use pushgateway strategy.
druid.emitter.prometheus.portThe port on which to expose the prometheus HTTPServer. Required if using exporter strategy.nonone
druid.emitter.prometheus.namespaceOptional metric namespace. Must match the regex [a-zA-Z_:][a-zA-Z0-9_:]*nodruid
druid.emitter.prometheus.dimensionMapPathJSON file defining the Prometheus metric type, desired dimensions, help text, and conversionFactor for every Druid metric.noDefault mapping provided. See below.
druid.emitter.prometheus.addHostAsLabelFlag to include the hostname as a prometheus label.nofalse
druid.emitter.prometheus.addServiceAsLabelFlag to include the druid service name (e.g. druid/broker, druid/coordinator, etc.) as a prometheus label.nofalse
druid.emitter.prometheus.pushGatewayAddressPushgateway address. Required if using pushgateway strategy.nonone
druid.emitter.prometheus.flushPeriodEmit metrics to Pushgateway every flushPeriod seconds. Required if pushgateway strategy is used.no15
druid.emitter.prometheus.extraLabelsJSON key-value pairs for additional labels on all metrics. Keys (label names) must match the regex [a-zA-Z_:][a-zA-Z0-9_:]*. Example: {"cluster_name": "druid_cluster1", "env": "staging"}.nonone
druid.emitter.prometheus.deletePushGatewayMetricsOnShutdownFlag to delete metrics from Pushgateway on task shutdown. Works only if pushgateway strategy is used. This feature allows to delete a stale metrics from batch executed tasks. Otherwise, the Pushgateway will store these stale metrics indefinitely as there is no time to live mechanism, using the memory to hold data that was already scraped by Prometheus.nofalse
druid.emitter.prometheus.waitForShutdownDelayTime in milliseconds to wait for peon tasks to delete metrics from the Pushgateway on shutdown (e.g. 60_000). Applicable only when pushgateway strategy is used and deletePushGatewayMetricsOnShutdown is set to true. There is no guarantee that a peon task will delete metrics from the gateway if the configured delay is more than the Peon's druid.indexer.task.gracefulShutdownTimeout value. For best results, set this value is 1.2 times the configured Prometheus scrape_interval of Pushgateway to ensure that Druid scrapes the metrics before cleanup.nonone

Ports for colocated Druid processes

In certain instances, Druid processes may be colocated on the same host. For example, the Broker and Router may share the same server. Other colocated processes include the Historical and MiddleManager or the Coordinator and Overlord. When you have colocated processes, specify druid.emitter.prometheus.port separately for each process on each host. For example, even if the Broker and Router share the same host, the Broker runtime properties and the Router runtime properties each need to list druid.emitter.prometheus.port, and the port value for both must be different.

Override properties for Peon Tasks

Peon tasks are created dynamically by middle managers and have dynamic host and port addresses. Since the exporter strategy allows Prometheus to read only from a fixed address, it cannot be used for peon tasks. So, these tasks need to be configured to use pushgateway strategy to push metrics from Druid to prometheus gateway.

If this emitter is configured to use exporter strategy globally, some of the above configurations need to be overridden in the middle manager so that spawned peon tasks can still use the pushgateway strategy.

# Override global prometheus emitter configuration for peon tasks to use `pushgateway` strategy.
# Other configurations can also be overridden by adding `` prefix to above configuration properties.

Metric names

All metric names and labels are reformatted to match Prometheus standards.

  • For names: all characters which are not alphanumeric, underscores, or colons (matching [^a-zA-Z_:][^a-zA-Z0-9_:]*) are replaced with _
  • For labels: all characters which are not alphanumeric or underscores (matching [^a-zA-Z0-9_][^a-zA-Z0-9_]*) are replaced with _

Metric mapping

Each metric to be collected by Prometheus must specify a type, one of [timer, counter, guage]. Prometheus Emitter expects this mapping to be provided as a JSON file. Additionally, this mapping specifies which dimensions should be included for each metric. Prometheus expects histogram timers to use Seconds as the base unit. Timers which do not use seconds as a base unit can use the conversionFactor to set the base time unit. If the user does not specify their own JSON file, a default mapping is used. All metrics are expected to be mapped. Metrics which are not mapped will not be tracked.

Prometheus metric path is organized using the following schema:

<druid metric name> : { 
"dimensions" : <dimension list>,
"type" : <timer|counter|gauge>,
"conversionFactor": <conversionFactor>,
"help" : <help text>

For example:

"query/time" : { 
"dimensions" : ["dataSource", "type"],
"type" : "timer",
"conversionFactor": 1000.0,
"help": "Seconds taken to complete a query."

For metrics which are emitted from multiple services with different dimensions, the metric name is prefixed with the service name. For example:

"druid/coordinator-segment/count" : { "dimensions" : ["dataSource"], "type" : "gauge" },
"druid/historical-segment/count" : { "dimensions" : ["dataSource", "tier", "priority"], "type" : "gauge" }

For most use cases, the default mapping is sufficient.