---
title: Telegraf Output Plugins
description: Telegraf output plugins send metrics to various destinations.
url: https://docs.influxdata.com/telegraf/v1/output-plugins/
estimated_tokens: 6625
product: Telegraf Enterprise
version: v1
publisher: InfluxData
canonical: https://docs.influxdata.com/telegraf/v1/output-plugins/
date: '2025-09-22T17:03:10+02:00'
lastmod: '2025-09-22T17:03:10+02:00'
---

Telegraf output plugins send metrics to various destinations.

### Amon

Plugin ID: `outputs.amon`  
Telegraf v0.2.1 - v1.37.0 Deprecated

This plugin writes metrics to [Amon monitoring
platform](https://www.amon.cx). It requires a `serverkey` and`amoninstance` URL which can be obtained from the[website](https://www.amon.cx/docs/monitoring/) for your account.

> [!Important]
> If point values being sent cannot be converted to a `float64`, the
> metric is skipped.

[View](/telegraf/v1/output-plugins/amon/)

### AMQP

Plugin ID: `outputs.amqp`  
Telegraf v0.1.9+

This plugin writes to an Advanced Message Queuing Protocol v0.9.1 broker.
A prominent implementation of this protocol is[RabbitMQ](https://www.rabbitmq.com).

> [!Note]
> This plugin does not bind the AMQP exchange to a queue.

For an introduction check the [AMQP concepts
page](https://www.rabbitmq.com/tutorials/amqp-concepts.html) and the[RabbitMQ getting started
guide](https://www.rabbitmq.com/getstarted.html).

[View](/telegraf/v1/output-plugins/amqp/)

### Azure Application Insights

Plugin ID: `outputs.application_insights`  
Telegraf v1.7.0+

This plugin writes metrics to the [Azure Application
Insights](https://azure.microsoft.com/en-us/services/application-insights/)service.

[View](/telegraf/v1/output-plugins/application_insights/)

### Arc

Plugin ID: `outputs.arc`  
Telegraf v1.37.0+

This plugin writes metrics to[Arc](https://github.com/basekick-labs/arc), a high-performance
time-series database, via MessagePack binary protocol messages providing
a **3-5x better performance** than the line-protocol format.

[View](/telegraf/v1/output-plugins/arc/)

### Azure Data Explorer

Plugin ID: `outputs.azure_data_explorer`  
Telegraf v1.20.0+

This plugin writes metrics to the [Azure Data
Explorer](https://docs.microsoft.com/en-us/azure/data-explorer), [Azure
Synapse Data
Explorer](https://docs.microsoft.com/en-us/azure/synapse-analytics/data-explorer/data-explorer-overview),
and [Real time analytics in
Fabric](https://learn.microsoft.com/en-us/fabric/real-time-analytics/overview)services.

Azure Data Explorer is a distributed, columnar store, purpose built for
any type of logs, metrics and time series data.

[View](/telegraf/v1/output-plugins/azure_data_explorer/)

### Azure Monitor

Plugin ID: `outputs.azure_monitor`  
Telegraf v1.8.0+

This plugin writes metrics to [Azure
Monitor](https://learn.microsoft.com/en-us/azure/azure-monitor) which has
a metric resolution of one minute. To accomodate for this in Telegraf,
the plugin will automatically aggregate metrics into one minute buckets
and send them to the service on every flush interval.

> [!Important]
> The Azure Monitor custom metrics service is currently in preview and
> might not be available in all Azure regions. Please also take the metric
> time limitations into account!

The metrics from each input plugin will be written to a separate Azure
Monitor namespace, prefixed with `Telegraf/` by default. The field name
for each metric is written as the Azure Monitor metric name. All field
values are written as a summarized set that includes: min, max, sum,
count. Tags are written as a dimension on each Azure Monitor metric.

[View](/telegraf/v1/output-plugins/azure_monitor/)

### Google BigQuery

Plugin ID: `outputs.bigquery`  
Telegraf v1.18.0+

This plugin writes metrics to the [Google Cloud
BigQuery](https://cloud.google.com/bigquery) service and requires[authentication](https://cloud.google.com/bigquery/docs/authentication)with Google Cloud using either a service account or user credentials.

> [!Important]
> Be aware that this plugin accesses APIs that are[chargeable](https://cloud.google.com/bigquery/pricing) and might incur
> costs.

[View](/telegraf/v1/output-plugins/bigquery/)

### Clarify

Plugin ID: `outputs.clarify`  
Telegraf v1.27.0+

This plugin writes metrics to [Clarify](https://clarify.io). To use this
plugin you will need to obtain a set of[credentials](https://docs.clarify.io/users/admin/integrations/credentials).

[View](/telegraf/v1/output-plugins/clarify/)

### Google Cloud PubSub

Plugin ID: `outputs.cloud_pubsub`  
Telegraf v1.10.0+

This plugin publishes metrics to a [Google Cloud
PubSub](https://cloud.google.com/pubsub) topic in one of the supported[data formats](/telegraf/v1/data_formats/output).

[View](/telegraf/v1/output-plugins/cloud_pubsub/)

### Amazon CloudWatch

Plugin ID: `outputs.cloudwatch`  
Telegraf v0.10.1+

This plugin writes metrics to the [Amazon
CloudWatch](https://aws.amazon.com/cloudwatch) service.

[View](/telegraf/v1/output-plugins/cloudwatch/)

### Amazon CloudWatch Logs

Plugin ID: `outputs.cloudwatch_logs`  
Telegraf v1.19.0+

This plugin writes log-metrics to the [Amazon
CloudWatch](https://aws.amazon.com/cloudwatch) service.

[View](/telegraf/v1/output-plugins/cloudwatch_logs/)

### CrateDB

Plugin ID: `outputs.cratedb`  
Telegraf v1.5.0+

This plugin writes metrics to [CrateDB](https://crate.io/) via its[PostgreSQL
protocol](https://crate.io/docs/crate/reference/protocols/postgres.html).

[View](/telegraf/v1/output-plugins/cratedb/)

### Datadog

Plugin ID: `outputs.datadog`  
Telegraf v0.1.6+

This plugin writes metrics to the [Datadog Metrics
API](https://docs.datadoghq.com/api/v1/metrics/#submit-metrics) and
requires an `apikey` which can be obtained on the[website](https://app.datadoghq.com/account/settings#api) for the
account.

> [!Note]
> This plugin supports the v1 API.

[View](/telegraf/v1/output-plugins/datadog/)

### Discard

Plugin ID: `outputs.discard`  
Telegraf v1.2.0+

This plugin discards all metrics written to it and is meant for testing
purposes.

[View](/telegraf/v1/output-plugins/discard/)

### Dynatrace

Plugin ID: `outputs.dynatrace`  
Telegraf v1.16.0+

This plugin writes metrics to [Dynatrace](https://www.dynatrace.com) via
the [Dynatrace Metrics API
V2](https://docs.dynatrace.com/docs/shortlink/api-metrics-v2). It may be
run alongside the Dynatrace OneAgent for automatic authentication or it
may be run standalone on a host without OneAgent by specifying a URL and
API Token.

More information on the plugin can be found in the [Dynatrace
documentation](https://docs.dynatrace.com/docs/shortlink/telegraf).

> [!Note]
> All metrics are reported as gauges, unless they are specified to be
> delta counters using the `additional_counters` or`additional_counters_patterns` config option (see below). See the[Dynatrace Metrics ingestion protocol
> documentation](https://docs.dynatrace.com/docs/shortlink/metric-ingestion-protocol)for details on the types defined there.

[View](/telegraf/v1/output-plugins/dynatrace/)

### Elasticsearch

Plugin ID: `outputs.elasticsearch`  
Telegraf v0.1.5+

This plugin writes metrics to [Elasticsearch](https://www.elastic.co) via
HTTP using the [Elastic client
library](http://olivere.github.io/elastic/). The plugin supports
Elasticsearch releases from v5.x up to v7.x.

[View](/telegraf/v1/output-plugins/elasticsearch/)

### Azure Event Hubs

Plugin ID: `outputs.event_hubs`  
Telegraf v1.21.0+

This plugin writes metrics to the [Azure Event
Hubs](https://azure.microsoft.com/en-gb/services/event-hubs/) service in
any of the supported [data formats](/telegraf/v1/data_formats/output).
Metrics are sent as batches with each message payload containing one
metric object, preferably as JSON as this eases integration with
downstream components.

Each patch is sent to a single Event Hub within a namespace. In case no
partition key is specified the batches will be automatically
load-balanced (round-robin) across all the Event Hub partitions.

[View](/telegraf/v1/output-plugins/event_hubs/)

### Executable

Plugin ID: `outputs.exec`  
Telegraf v1.12.0+

This plugin writes metrics to an external application via `stdin`. The
command will be executed on each write creating a new process. Metrics
are passed in one of the supported [data
formats](/telegraf/v1/data_formats/output).

The executable and the individual parameters must be defined as a list.
All outputs of the executable to `stderr` will be logged in the Telegraf
log.

> [!Tip]
> For better performance consider execd which runs continuously.

[View](/telegraf/v1/output-plugins/exec/)

### Executable Daemon

Plugin ID: `outputs.execd`  
Telegraf v1.15.0+

This plugin writes metrics to an external daemon program via `stdin`. The
command will be executed once and metrics will be passed to it on every
write in one of the supported [data
formats](/telegraf/v1/data_formats/output). The executable and the
individual parameters must be defined as a list.

All outputs of the executable to `stderr` will be logged in the Telegraf
log. Telegraf minimum version: Telegraf 1.15.0

[View](/telegraf/v1/output-plugins/execd/)

### File

Plugin ID: `outputs.file`  
Telegraf v0.10.3+

This plugin writes metrics to one or more local files in one of the
supported [data formats](/telegraf/v1/data_formats/output).

[View](/telegraf/v1/output-plugins/file/)

### Graphite

Plugin ID: `outputs.graphite`  
Telegraf v0.10.1+

This plugin writes metrics to[Graphite](http://graphite.readthedocs.org/en/latest/index.html) via TCP.
For details on the translation between Telegraf Metrics and Graphite
output see the [Graphite data
format](/telegraf/v1/plugins/#serializer-graphite).

[View](/telegraf/v1/output-plugins/graphite/)

### Graylog

Plugin ID: `outputs.graylog`  
Telegraf v1.0.0+

This plugin writes metrics to a [Graylog](https://graylog.org/) instance
using the [GELF data
format](https://docs.graylog.org/en/3.1/pages/gelf.html#gelf-payload-specification).

[View](/telegraf/v1/output-plugins/graylog/)

### GroundWork

Plugin ID: `outputs.groundwork`  
Telegraf v1.21.0+

This plugin writes metrics to a [GroundWork
Monitor](https://www.gwos.com/product/groundwork-monitor/) instance.

> [!Important]
> Plugin only supports GroundWork v8 or later.

[View](/telegraf/v1/output-plugins/groundwork/)

### Health

Plugin ID: `outputs.health`  
Telegraf v1.11.0+

This plugin provides a HTTP health check endpoint that can be configured
to return failure status codes based on the value of a metric.

When the plugin is healthy it will return a 200 response; when unhealthy
it will return a 503 response. The default state is healthy, one or more
checks must fail in order for the resource to enter the failed state.

[View](/telegraf/v1/output-plugins/health/)

### Heartbeat

Plugin ID: `outputs.heartbeat`  
Telegraf v1.37.0+

This plugin sends a heartbeat signal via POST to a HTTP endpoint on a
regular interval. This is useful to keep track of existing Telegraf
instances in a large deployment.

[View](/telegraf/v1/output-plugins/heartbeat/)

### HTTP

Plugin ID: `outputs.http`  
Telegraf v1.7.0+

This plugin writes metrics to a HTTP endpoint using one of the supported[data formats](/telegraf/v1/data_formats/output). For data formats
supporting batching, metrics are sent in batches by default.

[View](/telegraf/v1/output-plugins/http/)

### InfluxDB v1.x

Plugin ID: `outputs.influxdb`  
Telegraf v0.1.1+

This plugin writes metrics to a [InfluxDB
v1.x](https://docs.influxdata.com/influxdb/v1) instance via HTTP or UDP
protocol.

[View](/telegraf/v1/output-plugins/influxdb/)

### InfluxDB v2.x

Plugin ID: `outputs.influxdb_v2`  
Telegraf v1.8.0+

This plugin writes metrics to a [InfluxDB
v2.x](https://docs.influxdata.com/influxdb/v2) instance via HTTP.

[View](/telegraf/v1/output-plugins/influxdb_v2/)

### InfluxDB v3.x

Plugin ID: `outputs.influxdb_v3`  
Telegraf v1.38.0+

This plugin writes metrics to a [InfluxDB
v3.x](https://docs.influxdata.com) Core or Enterprise instance via the
HTTP API.

[View](/telegraf/v1/output-plugins/influxdb_v3/)

### Inlong

Plugin ID: `outputs.inlong`  
Telegraf v1.35.0+

This plugin publishes metrics to an [Apache
InLong](https://inlong.apache.org) instance.

[View](/telegraf/v1/output-plugins/inlong/)

### Instrumental

Plugin ID: `outputs.instrumental`  
Telegraf v0.13.1+

This plugin writes metrics to the [Instrumental Collector
API](https://instrumentalapp.com/docs/tcp-collector) and requires a
project-specific API token.

Instrumental accepts stats in a format very close to Graphite, with the
only difference being that the type of stat (gauge, increment) is the
first token, separated from the metric itself by whitespace. The`increment` type is only used if the metric comes in as a counter via the[statsd input plugin](/telegraf/v1/plugins/#input-statsd).

[View](/telegraf/v1/output-plugins/instrumental/)

### Apache IoTDB

Plugin ID: `outputs.iotdb`  
Telegraf v1.24.0+

This plugin writes metrics to an [Apache IoTDB](https://iotdb.apache.org)instance, a database for the Internet of Things, supporting session
connection and data insertion.

[View](/telegraf/v1/output-plugins/iotdb/)

### Kafka

Plugin ID: `outputs.kafka`  
Telegraf v0.1.7+

This plugin writes metrics to a [Kafka Broker](http://kafka.apache.org)acting a Kafka Producer.

[View](/telegraf/v1/output-plugins/kafka/)

### Amazon Kinesis

Plugin ID: `outputs.kinesis`  
Telegraf v0.2.5+

This plugin writes metrics to a [Amazon
Kinesis](https://aws.amazon.com/kinesis) endpoint. It will batch all
Points in one request to reduce the number of API requests.

Please consult [Amazon’s official
documentation](http://docs.aws.amazon.com/kinesis/latest/dev/key-concepts.html)for more details on the Kinesis architecture and concepts.

[View](/telegraf/v1/output-plugins/kinesis/)

### Librato

Plugin ID: `outputs.librato`  
Telegraf v0.2.0+

This plugin writes metrics to the [Librato](https://www.librato.com/)service. It requires an `api_user` and `api_token` which can be obtained
on the [website](https://metrics.librato.com/account/api_tokens) for your
account.

The `source_tag` option in the Configuration file is used to send
contextual information from Point Tags to the API. Besides from this, the
plugin currently does not send any additional associated Point Tags.

If the point value being sent cannot be converted to a `float64`, the
metric is skipped.

[View](/telegraf/v1/output-plugins/librato/)

### Logz.io

Plugin ID: `outputs.logzio`  
Telegraf v1.17.0+

This plugin writes metrics to the [Logz.io](https://logz.io) service via
HTTP.

[View](/telegraf/v1/output-plugins/logzio/)

### Grafana Loki

Plugin ID: `outputs.loki`  
Telegraf v1.18.0+

This plugin writes logs to a [Grafana Loki](https://grafana.com/loki)instance, using the metric name and tags as labels. The log line will
contain all fields in `key="value"` format easily parsable with the`logfmt` parser in Loki.

Logs within each stream are sorted by timestamp before being sent to
Loki.

[View](/telegraf/v1/output-plugins/loki/)

### Microsoft Fabric

Plugin ID: `outputs.microsoft_fabric`  
Telegraf v1.35.0+

This plugin writes metrics to [Fabric
Eventhouse](https://learn.microsoft.com/fabric/real-time-intelligence/eventhouse)and [Fabric
Eventstream](https://learn.microsoft.com/fabric/real-time-intelligence/event-streams/overview?tabs=enhancedcapabilities)artifacts of [Real-Time Intelligence in Microsoft
Fabric](https://learn.microsoft.com/fabric/real-time-intelligence/overview).

Real-Time Intelligence is a SaaS service in Microsoft Fabric that allows
you to extract insights and visualize data in motion. It offers an
end-to-end solution for event-driven scenarios, streaming data, and data
logs.

[View](/telegraf/v1/output-plugins/microsoft_fabric/)

### MongoDB

Plugin ID: `outputs.mongodb`  
Telegraf v1.21.0+

This plugin writes metrics to [MongoDB](https://www.mongodb.com)automatically creating collections as time series collections if they
don’t exist.

> [!Note]
> This plugin requires MongoDB v5 or later for time series collections.

[View](/telegraf/v1/output-plugins/mongodb/)

### MQTT Producer

Plugin ID: `outputs.mqtt`  
Telegraf v0.2.0+

This plugin writes metrics to a [MQTT broker](http://http://mqtt.org/)acting as a MQTT producer. The plugin supports the MQTT protocols `3.1.1`and `5`.

> [!Note]
> In v2.0.12+ of the mosquitto MQTT server, there is a[bug](https://github.com/eclipse/mosquitto/issues/2117) requiring the`keep_alive` value to be set non-zero in Telegraf. Otherwise, the server
> will return with `identifier rejected`. As a reference`eclipse/paho.golang` sets the `keep_alive` to 30.

[View](/telegraf/v1/output-plugins/mqtt/)

### NATS

Plugin ID: `outputs.nats`  
Telegraf v1.1.0+

This plugin writes metrics to subjects of a set of[NATS](https://nats.io) instances in one of the supported [data
formats](/telegraf/v1/data_formats/output).

[View](/telegraf/v1/output-plugins/nats/)

### Nebius Cloud Monitoring

Plugin ID: `outputs.nebius_cloud_monitoring`  
Telegraf v1.27.0+

This plugin writes metrics to the [Nebuis Cloud
Monitoring](https://nebius.com/il/services/monitoring) service.

[View](/telegraf/v1/output-plugins/nebius_cloud_monitoring/)

### New Relic

Plugin ID: `outputs.newrelic`  
Telegraf v1.15.0+

This plugins writes metrics to [New Relic Insights](https://newrelic.com)using the [Metrics
API](https://docs.newrelic.com/docs/data-ingest-apis/get-data-new-relic/metric-api/introduction-metric-api).
To use this plugin you have to obtain an [Insights API
Key](https://docs.newrelic.com/docs/apis/get-started/intro-apis/types-new-relic-api-keys#user-api-key).

[View](/telegraf/v1/output-plugins/newrelic/)

### NSQ

Plugin ID: `outputs.nsq`  
Telegraf v0.2.1+

This plugin writes metrics to the given topic of a [NSQ](https://nsq.io)instance as a producer in one of the supported [data
formats](/telegraf/v1/data_formats/output).

[View](/telegraf/v1/output-plugins/nsq/)

### OpenSearch

Plugin ID: `outputs.opensearch`  
Telegraf v1.29.0+

This plugin writes metrics to a [OpenSearch](https://opensearch.org/)instance via HTTP. It supports OpenSearch releases v1 and v2 but future
comparability with 1.x is not guaranteed and instead will focus on 2.x
support.

> [!Tip]
> Consider using the existing Elasticsearch plugin for 1.x.

[View](/telegraf/v1/output-plugins/opensearch/)

### OpenTelemetry

Plugin ID: `outputs.opentelemetry`  
Telegraf v1.20.0+

This plugin writes metrics to [OpenTelemetry](https://opentelemetry.io)servers and agents via gRPC or HTTP.

[View](/telegraf/v1/output-plugins/opentelemetry/)

### OpenTSDB

Plugin ID: `outputs.opentsdb`  
Telegraf v0.1.9+

This plugin writes metrics to an [OpenTSDB](http://opentsdb.net/)instance using either the telnet or HTTP mode. Using the HTTP API is
recommended since OpenTSDB 2.0.

[View](/telegraf/v1/output-plugins/opentsdb/)

### Parquet

Plugin ID: `outputs.parquet`  
Telegraf v1.32.0+

This plugin writes metrics to [parquet](https://parquet.apache.org)files. By default, metrics are grouped by metric name and written all to
the same file.

> [!Important]
> If a metric schema does not match the schema in the file it will be
> dropped.

To lean more about the parquet format, check out the [parquet
docs](https://parquet.apache.org/docs/) as well as a blog post on[querying
parquet](https://www.influxdata.com/blog/querying-parquet-millisecond-latency/).

[View](/telegraf/v1/output-plugins/parquet/)

### PostgreSQL

Plugin ID: `outputs.postgresql`  
Telegraf v1.24.0+

This plugin writes metrics to a [PostgreSQL](https://www.postgresql.org/)(or compatible) server managing the schema and automatically updating
missing columns.

[View](/telegraf/v1/output-plugins/postgresql/)

### Prometheus

Plugin ID: `outputs.prometheus_client`  
Telegraf v0.2.1+

This plugin starts a [Prometheus](https://prometheus.io) client and
exposes the written metrics on a `/metrics` endpoint by default. This
endpoint can then be polled by a Prometheus server.

[View](/telegraf/v1/output-plugins/prometheus_client/)

### Quix

Plugin ID: `outputs.quix`  
Telegraf v1.33.0+

This plugin writes metrics to a [Quix](https://quix.io) endpoint.

Please consult Quix’s [official documentation](https://quix.io/docs/) for
more details on the Quix platform architecture and concepts.

[View](/telegraf/v1/output-plugins/quix/)

### Redis Time Series

Plugin ID: `outputs.redistimeseries`  
Telegraf v1.0.0+

This plugin writes metrics to a [Redis
time-series](https://redis.io/timeseries) server.

[View](/telegraf/v1/output-plugins/redistimeseries/)

### Remote File

Plugin ID: `outputs.remotefile`  
Telegraf v1.32.0+

This plugin writes metrics to files in a remote location using the[rclone library](https://rclone.org). Currently the following backends
are supported:

* `local`: [Local filesystem](https://rclone.org/local/)
* `s3`: [Amazon S3 storage providers](https://rclone.org/s3/)
* `sftp`: [Secure File Transfer Protocol](https://rclone.org/sftp/)

[View](/telegraf/v1/output-plugins/remotefile/)

### Riemann

Plugin ID: `outputs.riemann`  
Telegraf v1.3.0+

This plugin writes metric to the [Riemann](http://riemann.io) serice via
TCP or UDP.

[View](/telegraf/v1/output-plugins/riemann/)

### Sensu Go

Plugin ID: `outputs.sensu`  
Telegraf v1.18.0+

This plugin writes metrics to [Sensu Go](https://sensu.io) via its HTTP
events API.

[View](/telegraf/v1/output-plugins/sensu/)

### SignalFx

Plugin ID: `outputs.signalfx`  
Telegraf v1.18.0+

This plugin writes metrics to[SignalFx](https://docs.signalfx.com/en/latest/).

[View](/telegraf/v1/output-plugins/signalfx/)

### Socket Writer

Plugin ID: `outputs.socket_writer`  
Telegraf v1.3.0+

This plugin writes metrics to a network service e.g. via UDP or TCP in
one of the supported [data formats](/telegraf/v1/data_formats/output).

[View](/telegraf/v1/output-plugins/socket_writer/)

### SQL

Plugin ID: `outputs.sql`  
Telegraf v1.19.0+

This plugin writes metrics to a supported SQL database using a simple,
hard-coded database schema. There is a table for each metric type with
the table name corresponding to the metric name. There is a column per
field and a column per tag with an optional column for the metric
timestamp.

A row is written for every metric. This means multiple metrics are never
merged into a single row, even if they have the same metric name, tags,
and timestamp.

The plugin uses Golang’s generic “database/sql” interface and third party
drivers. See the driver-specific section for a list of supported drivers
and details.

[View](/telegraf/v1/output-plugins/sql/)

### Google Cloud Monitoring

Plugin ID: `outputs.stackdriver`  
Telegraf v1.9.0+

This plugin writes metrics to a `project` in [Google Cloud
Monitoring](https://cloud.google.com/monitoring/api/v3/) (formerly called
Stackdriver).[Authentication](https://cloud.google.com/docs/authentication/getting-started)with Google Cloud is required using either a service account or user
credentials.

> [!Important]
> This plugin accesses APIs which are[chargeable](https://cloud.google.com/stackdriver/pricing#google-clouds-operations-suite-pricing)and might incur costs.

By default, Metrics are grouped by the `namespace` variable and metric
key, eg: `custom.googleapis.com/telegraf/system/load5`. However, this is
not the best practice. Setting `metric_name_format = "official"` will
produce a more easily queried format of:`metric_type_prefix/[namespace_]name_key/kind`. If the global namespace
is not set, it is omitted as well.

[View](/telegraf/v1/output-plugins/stackdriver/)

### ActiveMQ STOMP

Plugin ID: `outputs.stomp`  
Telegraf v1.24.0+

This plugin writes metrics to an [Active MQ
Broker](http://activemq.apache.org/) for [STOMP](https://stomp.github.io)but also supports [Amazon MQ](https://aws.amazon.com/amazon-mq) brokers.
Metrics can be written in one of the supported [data
formats](/telegraf/v1/data_formats/output).

[View](/telegraf/v1/output-plugins/stomp/)

### Sumo Logic

Plugin ID: `outputs.sumologic`  
Telegraf v1.16.0+

This plugin writes metrics to a [Sumo Logic HTTP
Source](https://help.sumologic.com/03Send-Data/Sources/02Sources-for-Hosted-Collectors/HTTP-Source/Upload-Metrics-to-an-HTTP-Source)using one of the following data formats:

* `graphite` for Content-Type of `application/vnd.sumologic.graphite`
* `carbon2` for Content-Type of `application/vnd.sumologic.carbon2`
* `prometheus` for Content-Type of `application/vnd.sumologic.prometheus`

[View](/telegraf/v1/output-plugins/sumologic/)

### Syslog

Plugin ID: `outputs.syslog`  
Telegraf v1.11.0+

This plugin writes metrics as syslog messages via UDP in [RFC5426
format](https://tools.ietf.org/html/rfc5426) or via TCP in [RFC6587
format](https://tools.ietf.org/html/rfc6587) or via TLS in [RFC5425
format](https://tools.ietf.org/html/rfc5425), with or without the octet
counting framing.

> [!Important]
> Syslog messages are formatted according to[RFC5424](https://tools.ietf.org/html/rfc5424) limiting the field sizes
> when sending messages according to the [syslog message
> format](https://datatracker.ietf.org/doc/html/rfc5424#section-6) section
> of the RFC. Sending messages beyond these sizes may get dropped by a
> strict receiver silently.

[View](/telegraf/v1/output-plugins/syslog/)

### Amazon Timestream

Plugin ID: `outputs.timestream`  
Telegraf v1.16.0+

This plugin writes metrics to the [Amazon
Timestream](https://aws.amazon.com/timestream) service.

[View](/telegraf/v1/output-plugins/timestream/)

### Warp10

Plugin ID: `outputs.warp10`  
Telegraf v1.14.0+

This plugin writes metrics to the [Warp 10](https://www.warp10.io)service.

[View](/telegraf/v1/output-plugins/warp10/)

### Wavefront

Plugin ID: `outputs.wavefront`  
Telegraf v1.5.0+

This plugin writes metrics to a [Wavefront](https://www.wavefront.com)instance or a Wavefront Proxy instance over HTTP or HTTPS.

[View](/telegraf/v1/output-plugins/wavefront/)

### Websocket

Plugin ID: `outputs.websocket`  
Telegraf v1.19.0+

This plugin writes metrics to a WebSocket endpoint in one of the
supported [data formats](/telegraf/v1/data_formats/output).

[View](/telegraf/v1/output-plugins/websocket/)

### Yandex Cloud Monitoring

Plugin ID: `outputs.yandex_cloud_monitoring`  
Telegraf v1.17.0+

This plugin writes metrics to the [Yandex Cloud
Monitoring](https://cloud.yandex.com/services/monitoring) service.

[View](/telegraf/v1/output-plugins/yandex_cloud_monitoring/)

### Zabbix

Plugin ID: `outputs.zabbix`  
Telegraf v1.30.0+

This plugin writes metrics to [Zabbix](https://www.zabbix.com/) via[traps](https://www.zabbix.com/documentation/current/en/manual/appendix/items/trapper).
It has been tested with versions v3.0, v4.0 and v6.0 but should work with
newer versions of Zabbix as long as the protocol doesn’t change.

[View](/telegraf/v1/output-plugins/zabbix/)