opentelemetry-exporter-dynatrace-metrics 0.1.0b1

Dynatrace Metric Exporter for OpenTelemetry

Dynatrace OpenTelemetry Metrics Exporter for Python

This exporter is based on the OpenTelemetry Metrics SDK for Python, which is currently in an alpha state and neither considered stable nor complete as of this writing. As such, this exporter is not intended for production use until the underlying OpenTelemetry Metrics API and SDK are stable. See open-telemetry/opentelemetry-python for the current state of the OpenTelemetry SDK for Python.

Getting started

Installation

To install the latest version from PyPI run:

pip install opentelemetry-exporter-dynatrace-metrics

Usage

The general setup of OpenTelemetry Python is explained in the official Getting Started Guide.

# configure API endpoint and authentication token
exporter = DynatraceMetricsExporter(endpoint_url, api_token)

# setup metrics export pipeline
metrics.set_meter_provider(MeterProvider())
meter = metrics.get_meter(__name__)
metrics.get_meter_provider().start_pipeline(meter, exporter, push_interval_sec)

# crate a counter instrument and provide the first data point
counter = meter.create_counter(
    name="MyCounter",
    description="Description of MyCounter",
    unit="1",
    value_type=int
)

counter.add(25, {"dimension-1", "value-1"})

Example

To run the example, clone this repository and change to the opentelemetry-metric-python folder, then run:

pip install .           # install the Dynatrace exporter
export LOGLEVEL=DEBUG   # (optional) Set the log level to debug to see more output (default is INFO)
python example/basic_example.py

A more complete setup routine can be found here, including installing inside a virtual environment and getting required packages. If you just want to see it in action, it should be sufficient to run example/install_and_run.sh from the root folder. This script will install Python, set up a virtual environment, pull in all the required packages and run the example.

The example also offers a simple CLI. Run python example/basic_example.py -h to get more information.

Configuration

The exporter allows for configuring the following settings by passing them to the constructor:

Dynatrace API Endpoint

The endpoint to which the metrics are sent is specified using the endpoint_url parameter.

Given an environment ID myenv123 on Dynatrace SaaS, the metrics ingest endpoint would be https://myenv123.live.dynatrace.com/api/v2/metrics/ingest.

If a OneAgent is installed on the host, it can provide a local endpoint for providing metrics directly without the need for an API token. This feature is currently in an Early Adopter phase and has to be enabled as described in the OneAgent metric API documentation. Using the local API endpoint, the host ID and host name context are automatically added to each metric as dimensions. The default metric API endpoint exposed by the OneAgent is http://localhost:14499/metrics/ingest. If no endpoint is set and a OneAgent is running on the host, metrics will be exported to it automatically using the OneAgent with no endpoint or API token configuration required.

Dynatrace API Token

The Dynatrace API token to be used by the exporter is specified using the api_token parameter and could, for example, be read from an environment variable.

Creating an API token for your Dynatrace environment is described in the Dynatrace API documentation. The scope required for sending metrics is the Ingest metrics scope in the API v2 section:

Metric Key Prefix

The prefix parameter specifies an optional prefix, which is prepended to each metric key, separated by a dot (<prefix>.<namespace>.<name>).

Default Dimensions

The default_dimensions parameter can be used to optionally specify a list of key/value pairs, which will be added as additional dimensions to all data points. Dimension keys are unique, and labels on instruments will overwrite the default dimensions if key collisions appear.

Export Dynatrace Metadata

If running on a host with a running OneAgent, setting the export_dynatrace_metadata option to True will export metadata collected by the OneAgent to the Dynatrace endpoint. If no Dynatrace API endpoint is set, the default exporter endpoint will be the OneAgent endpoint, and this option will be set automatically. Therefore, if no endpoint is specified, a OneAgent is assumed to be running and used as the export endpoint for all metric lines, including metadata. More information on the underlying Dynatrace metadata feature that is used by the exporter can be found in the Dynatrace documentation.

Dimensions precedence

When specifying default dimensions, labels and Dynatrace metadata enrichment, the precedence of dimensions with the same key is as follows: Default dimensions are overwritten by labels passed to instruments, which in turn are overwritten by the Dynatrace metadata dimensions (even though the likeliness of a collision here is very low, since the Dynatrace metadata only contains Dynatrace reserved dimensions starting with dt.*).

Development

Requirements

Just tox.

Running tests and lint

• Test all supported python versions: tox
• Test all supported python versions in parallel: tox -p
• A particular python version: tox -e 38
• Current python version: tox -e py
• Lint: tox -e lint