Telegraf provides a server agent for forwarding metrics, logs, and events, and accepts data from a variety of sources through input plugins and forwards them to other destinations with output plugins .

Send data to Observe using the Telegraf HTTP output plugin and JSON data.

📘

Note

For logs and events, Observe recommends Elastic Beats , Fluent Bit , or Fluentd . But you may use an appropriate option for your environment.

Installation

If you do not currently use Telegraf, see Get started with Telegraf in the Telegraf documentation for installation details.

To install on a Kubernetes cluster, InfluxData recommends using the InfluxData Helm Charts .

Configuration

Perform the following tasks:

1. Configure the HTTP output plugin.

2. Add the following output configuration to your telegraf.conf file, where OBSERVE_CUSTOMER and OBSERVE_TOKEN are environment variables containing your Customer ID and ingest token.

   📘

   Note

   Some Observe instances may optionally use a name instead of Customer ID; if this is the case for your instance, contact your Observe data engineer to discuss implementation. A stem name will work as is, but a DNS redirect name may require client configuration.

   Text

   [[outputs.http]]
     url = "https://${OBSERVE_CUSTOMER}.collect.observeinc.com/v1/http/telegraf"
     data_format = "json"
     content_encoding = "gzip"
   
     [outputs.http.headers]
       Authorization = "Bearer ${OBSERVE_TOKEN}"
       Content-Type = "application/json"
       X-Observe-Decoder = "nested"

3. Configure input plugins.

   If needed, configure the appropriate Telegraf input plugin so Telegraf can forward data from the original sources.

   For example, to forward metrics from servers that expose a Prometheus metrics endpoint, use the Prometheus input plugin :

   [[inputs.prometheus]]
     ## An array of urls to scrape metrics from.
     urls = ["http://localhost:9100/metrics"]

   Replace 9100 with the port number for your Prometheus metrics endpoint/exporter.

Troubleshoot Telegraf configurations

To debug Telegraf inputs or outputs, see Troubleshoot Telegraf in the Telegraf documentation.