OneAgent metric API

You can use the local http://localhost:<port>/metrics/ingest API endpoint to push locally retrieved metrics to Dynatrace over a secure and authenticated channel. This endpoint is available only to local clients and cannot be reached from remote hosts.

If you can't push metrics using a local API endpoint, you can also use the public Metric API v2 endpoint.

Enable the OneAgent metric API

The OneAgent metric API comes with OneAgent version 1.201 by default. You only need to enable the OneAgent metric API at the environment or host level. Note that the host-level configuration overrides the environment configuration.

Enable at the environment level

In the Dynatrace menu, go to Settings > Monitoring > Monitored technologies.
In the list of supported technologies, search for the Dynatrace OneAgent StatsD, Pipe, HTTP Metric API entry.
Select Edit.
Turn on Enable Extensions Execution Controller on every host.
Turn on Enable local PIPE/HTTP metric API on every host.

Disable on selected hosts

When enabled at the environment level, you can disable ingestion for selected hosts.

In the Dynatrace menu, select Hosts, and select your host.
Open the browse menu (…) and select Settings.
In the Monitored technologies table, search for the PIPE/HTTP entry. You can sort by Type and look for the Infrastructure insights type.
Edit the entry:
- Turn on Use host configuration.
- Turn off Enable on this host.

Enable for a single host

In the Dynatrace menu, go to Settings > Monitoring > Monitored technologies.
In the list of supported technologies, search for the Dynatrace OneAgent StatsD, Pipe, HTTP Metric API entry.
Select Edit.
Turn off all three options, that is Enable Extension Execution Controller on every host, Enable local PIPE/HTTP metric and Log Ingest API on every host, and Enable Dynatrace StatsD on every host.
In the Dynatrace menu, select Hosts, and select your host.
Open the browse menu (…) and select Settings.
In the Monitored technologies table, search for the Extensions Execution Controller entry. You can sort by Type and look for the Infrastructure insights type. Select Edit and turn on Use host configuration and Enable on this host.
Search for PIPE/HTTP. Select Edit and turn on Use host configuration and Enable on this host.

Topology awareness

Using the local API endpoint, the host ID and host name context are automatically added to each metric as dimensions. Learn how to enrich your metrics with other Dynatrace-specific dimensions and apply Dynatrace-AI causation details to your ingested data.

Metric format

Provided data points must follow the Metrics ingestion protocol.

The request consumes a plain/text payload with the charset=utf-8 character set. The payload is limited to 1,000 lines.

Example

With this curl command, you'll ingest the cpu.temperature metric assigned to the cpu=1 dimension. The metric will be automatically assigned to a respective host ID and host name.

bash
curl --data "cpu.temperature,cpu=1 55" http://localhost:14499/metrics/ingest \
     -H "Content-Type: text/plain; charset=utf-8"

Successful response:

json
{
 "error": null,
 "linesValid": 1,
 "linesInvalid": 0
}

Communication port

The default metric ingestion port is 14499. If necessary, you can use the oneagentctl command to check or change the port. Changing the metric ingestion port requires restart of OneAgent. Add --restart-service to the command to restart OneAgent automatically.

Check the ingestion port

Use the --get-extensions-ingest-port parameter to show the current local ingestion port, 14499 by default.

Linux: ./oneagentctl --get-extensions-ingest-port
Windows: .\oneagentctl.exe --get-extensions-ingest-port

Set a custom ingestion port

Use the --set-extensions-ingest-port=<arg> parameter to set a custom local ingestion port.

Linux: ./oneagentctl --set-extensions-ingest-port=14499 --restart-service
Windows: .\oneagentctl.exe --set-extensions-ingest-port=14499 --restart-service

Configure proxy

Configure your host proxy to allow localhost traffic going to the metric ingestion port, 14499 by default.

Note that changing the port for the OneAgent metric API also affects scripting integration and Telegraf.

Metrics 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 Metrics 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, to have events raised for a selected host and have Dynatrace Davis® perform causation analysis based on your metrics, you can configure your app to add the dt.entity.host dimension. For more information, see Metrics API - POST ingest data points.