Configure metrics

Enable or disable Dapr metrics

By default, each Dapr system process emits Go runtime/process metrics and has their own Dapr metrics.

Prometheus endpoint

The Dapr sidecar exposes a Prometheus-compatible metrics endpoint that you can scrape to gain a greater understanding of how Dapr is behaving.

Configuring metrics using the CLI

The metrics application endpoint is enabled by default. You can disable it by passing the command line argument --enable-metrics=false.

The default metrics port is 9090. You can override this by passing the command line argument --metrics-port to daprd.

Configuring metrics in Kubernetes

You can also enable/disable the metrics for a specific application by setting the "false" annotation on your application deployment. With the metrics exporter disabled, daprd does not open the metrics listening port.

The following Kubernetes deployment example shows how metrics are explicitly enabled with the port specified as “9090”.

apiVersion: apps/v1
kind: Deployment
  name: nodeapp
    app: node
  replicas: 1
      app: node
        app: node
      annotations: "true" "nodeapp" "3000" "true" "9090"
      - name: node
        image: dapriosamples/hello-k8s-node:latest
        - containerPort: 3000
        imagePullPolicy: Always

Configuring metrics using application configuration

You can also enable metrics via application configuration. To disable the metrics collection in the Dapr sidecars by default, set spec.metrics.enabled to false.

kind: Configuration
  name: tracing
  namespace: default
    enabled: false

High cardinality metrics

When invoking Dapr using HTTP, the legacy behavior (and current default as of Dapr 1.13) is to create a separate “bucket” for each requested method. When working with RESTful APIs, this can cause very high cardinality, with potential negative impact on memory usage and CPU.

Dapr 1.13 introduces a new option for the Dapr Configuration resource spec.metrics.http.increasedCardinality: when set to false, it reports metrics for the HTTP server for each “abstract” method (for example, requesting from a state store) instead of creating a “bucket” for each concrete request path.

The default value of spec.metrics.http.increasedCardinality is true in Dapr 1.13, to maintain the same behavior as Dapr 1.12 and older. However, the value will change to false (low-cardinality metrics by default) in Dapr 1.14.

Setting spec.metrics.http.increasedCardinality to false is recommended to all Dapr users, to reduce resource consumption. The pre-1.13 behavior, which is used when the option is true, is considered legacy and is only maintained for users who have special requirements around backwards-compatibility.

Transform metrics with regular expressions

You can set regular expressions for every metric exposed by the Dapr sidecar to “transform” their values. See a list of all Dapr metrics.

The name of the rule must match the name of the metric that is transformed. The following example shows how to apply a regular expression for the label method in the metric dapr_runtime_service_invocation_req_sent_total:

kind: Configuration
  name: daprConfig
    enabled: true
    increasedCardinality: true
      - name: dapr_runtime_service_invocation_req_sent_total
        - name: method
            "orders/": "orders/.+"

When this configuration is applied, a recorded metric with the method label of orders/a746dhsk293972nz is replaced with orders/.

Using regular expressions to reduce metrics cardinality is considered legacy. We encourage all users to set spec.metrics.http.increasedCardinality to false instead, which is simpler to configure and offers better performance.