Telegraf

Telegraf and OneAgent on the same host

1. Edit telegraf.conf, the Telegraf configuration file.
2. Uncomment the [[outputs.dynatrace]] line.
3. optional Uncomment the prefix = "telegraf." line and set the prefix to easily find the Telegraf ingested metrics. The prefix will also be visible in the Dynatrace metric key.
4. Save the file.

# # Send telegraf metrics to a Dynatrace environment
[[outputs.dynatrace]]
#   ## For usage with the Dynatrace OneAgent you can omit any configuration,
#   ## the only requirement is that the OneAgent is running on the same host.
#   ## Only setup environment url and token if you want to monitor a Host without the OneAgent present.
#   ##
#   ## Your Dynatrace environment URL.
#   ## For Dynatrace OneAgent you can leave this empty or set it to "http://127.0.0.1:14499/metrics/ingest" (default)
#   ## For Dynatrace SaaS environments the URL scheme is "https://{your-environment-id}.live.dynatrace.com/api/v2/metrics/ingest"
#   ## For Dynatrace Managed environments the URL scheme is "https://{your-domain}/e/{your-environment-id}/api/v2/metrics/ingest"
#   url = ""
#
#   ## Your Dynatrace API token.
#   ## Create an API token within your Dynatrace environment, by navigating to Settings > Integration > Dynatrace API
#   ## The API token needs data ingest scope permission. When using OneAgent, no API token is required.
#   api_token = ""
#
#   ## Optional prefix for metric names (e.g.: "telegraf.")
prefix = "telegraf."
#
#   ## Optional TLS Config
#   # tls_ca = "/etc/telegraf/ca.pem"
#   # tls_cert = "/etc/telegraf/cert.pem"
#   # tls_key = "/etc/telegraf/key.pem"
#
#   ## Optional flag for ignoring tls certificate check
#   # insecure_skip_verify = false
#
#
#   ## Connection timeout, defaults to "5s" if not set.
#   timeout = "5s"

No OneAgent on the host

If for some reason you can't install OneAgent on the Telegraf monitored host, you can configure the Dynatrace Output Plugin to push metrics directly to your Dynatrace environment through Metrics API v2.

Prerequisites

• API token with the Ingest metrics data points scope.
• Your Environment ID.

1. Edit telegraf.conf, the Telegraf configuration file.
2. Uncomment the # [[outputs.dynatrace]] line.
3. optional Uncomment the # prefix = "telegraf." line and set the prefix to easily find the Telegraf ingested metrics. The prefix will also be visible in the Dynatrace metric key.
4. Uncomment the # api_token = "" line and add your API token, for example api_token = "abcdefjhij1234567890"
5. Uncomment the # url = "" line and add your Dynatrace metric API endpoint. For example,
   • Dynatrace SaaS url = "https://{your-environment-id}.live.dynatrace.com/api/v2/metrics/ingest"
   • Dynatrace Managed https://{your-domain}/e/{your-environment-id}/api/v2/metrics/ingest
6. Save the file.

1. Go to Settings > Monitoring > Monitored technologies.
2. In the list of supported technologies, search for the Dynatrace OneAgent StatsD, Pipe, HTTP Metric API entry.
3. Select Edit.
4. Turn on Enable Extensions Execution Controller on every host.
5. 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. 5. From the navigation menu, select Hosts, and select your host. 6. Open the browse menu (...) and select Settings. 7. In the Monitored technologies table, search for the PIPE/HTTP entry. You can sort by Type and look for the Infrastructure insights type. 8. Edit the entry:

• Turn on Use host configuration.
• Turn off Enable on this host.

1. Go to Settings > Monitoring > Monitored technologies.
2. In the list of supported technologies, search for the Dynatrace OneAgent StatsD, Pipe, HTTP Metric API entry.
3. Select Edit.
4. Turn off Extension Execution Controller.
5. From the navigation menu, select Hosts, and select your host.
6. Open the browse menu (...) and select Settings.
7. 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.
8. Search for PIPE/HTTP. Select Edit and turn on Use host configuration and Enable on this host.