Metric ingestion

Early Adopter

Metric ingestion provides you a simple way to push any custom metrics to Dynatrace. You can easily push metrics to Dynatrace using a unified ingestion protocol shared among the following channels:

You can also push StatsD metrics to Dynatrace using a Dynatrace-extended StatsD metric format and Telegraf Output Plugin.

Metric ingestion

You can fine-grain your metrics into categories with up to 50 dimensions per data point. Dimensions come very handy for future use of metric, like analysis or charting.

Prerequisites

Local ingestion interface

OneAgent is equipped with the Extension Execution Controller (EEC) module, which provides a secure interface for ingesting metrics from multiple data sources running on the same host. EEC automatically adds the host ID and host name context to each metric. Note that we're already working on more automatic metric enrichments.

Setup

EEC is installed with OneAgent automatically. If your data sources send metrics over default ports, you're all set. Enable metric ingestion, set up your data source, and OneAgent starts ingesting your metrics automatically.

For details, see:

Security

The EEC interface is only available to the localhost addresses and cannot be reached from remote hosts. It uses a channel provided by OneAgent that is fully secure.

Metric API v2

Unlike the local ingestion interface, which adds the topology context automatically (each metric is assigned to a respective host), metrics pushed through the public Metric API v2 are flat by default. This is especially beneficial for business-related metrics that don't have any relation to the topology entities in your environment. However, you can still configure your app to add the dt.entity.host dimension to have events raised for a selected host and have Davis perform causation analysis based on your metrics. For more information, see Metric API v2.

Events

The custom metric ingest channel allows for the ingestion of all types of metric measurements, regardless of the number of entities they relate to. The way an event is raised depends on whether there's no entity, a single entity, or multiple entities assigned to a custom metric. For more information, see Topology awareness.

View metrics on a dashboard

Ingested metrics are available in the Explorer for custom charting. Select Create custom chart and select Try it out in the top banner. For more information, see Explorer.

You can simply search for metric keys of all available metrics and define how you’d like to analyze and chart your metrics. After that you can pin your charts on a dashboard.

Metric alerts

You can also create custom alerts based on the ingested metrics. Form the navigation menu, select Settings > Anomaly detection > Custom events for alerting and select Create custom event for alerting. In the Create custom event for alerting page, search for a metric using its key and define your alert. For more information, see Metric events for alerting.

Licensing

  • Ingested metrics can be booked directly on monitored hosts so that you can take advantage of included host metrics. This applies to metrics assigned to a host, either automatically or by adding the dt.entity.host dimension.
  • Pricing for metric ingest via DDUs
    • Each reported datapoint will consume DDU (with weight 0.001)​
    • A metric reported every minute will consume 526 DDUs per dimension per year​
      cpu.temp,cpu=cpu1,cpu_type=INTEL 50
      cpu.temp,cpu=cpu2,cpu_type=INTEL 55
      
      Two dimensions (cpu1, cpu2) will consume 526 * 2 = 1.052 DDUs per year.​
  • To check the DDU consumption, go to Settings > Accounting > Davis data units overview.

Limits

The following limits apply to metric ingestion using a common ingestion channel. For API ingested metrics, if any limit is exceeded, the API call returns the 400 response code, with details in the response body.

  Limit Description
Metric key length, characters 50  
Number of dimensions per line 50 The number of dimensions in a single line of the payload.
Number of metrics per minute 1,000 The max number of metrics Dynatrace can ingest in every 1-minute interval.
Total number of possible metric keys. 10,000 The max number of metric keys that can be registered in Dynatrace.
Number of tuples per month 20,000,000 The max number of unique metric-dimension key-dimension value-payload type combinations per calendar month.
Length of line, characters 2,000 The maximal length of a single line of the payload.