--- title: Telegraf glossary description: This section includes definitions of important terms for related to Telegraf. url: https://docs.influxdata.com/telegraf/v1/glossary/ estimated_tokens: 2188 product: Telegraf Enterprise version: v1 publisher: InfluxData canonical: https://docs.influxdata.com/telegraf/v1/glossary/ date: '2026-08-14T12:27:55-06:00' lastmod: '2026-08-14T12:27:55-06:00' --- ## agent An agent is the core part of Telegraf that gathers metrics from the declared input plugins and sends metrics to the declared output plugins, based on the plugins enabled by the given configuration. Related entries: [input plugin](/telegraf/v1/glossary/#input-plugin), [output plugin](/telegraf/v1/glossary/#output-plugin) ## aggregator plugin Aggregator plugins receive raw metrics from input plugins and create aggregate metrics from them. The aggregate metrics are then passed to the configured output plugins. Related entries: [input plugin](/telegraf/v1/glossary/#input-plugin), [output plugin](/telegraf/v1/glossary/#output-plugin), [processor plugin](/telegraf/v1/glossary/#processor-plugin) ## batch size The Telegraf agent sends metrics to output plugins in batches, not individually. The batch size controls the size of each write batch that Telegraf sends to the output plugins. Related entries: [output plugin](/telegraf/v1/glossary/#output-plugin) ## collection interval The default global interval for collecting data from each input plugin. The collection interval can be overridden by each individual input plugin’s configuration. Related entries: [input plugin](/telegraf/v1/glossary/#input-plugin) ## collection jitter Collection jitter is used to prevent every input plugin from collecting metrics simultaneously, which can have a measurable effect on the system. Each collection interval, every input plugin will sleep for a random time between zero and the collection jitter before collecting the metrics. Related entries: [collection interval](/telegraf/v1/glossary/#collection-interval), [input plugin](/telegraf/v1/glossary/#input-plugin) ## external plugin Programs built outside of Telegraf that run through the `execd` plugin. Provides flexibility to add functionality that doesn’t exist in internal Telegraf plugins. Related entries: [input plugin](/telegraf/v1/glossary/#input-plugin), [output plugin](/telegraf/v1/glossary/#output-plugin), [processor plugin](/telegraf/v1/glossary/#processor-plugin) ## flush interval The global interval for flushing data from each output plugin to its destination. This value should not be set lower than the collection interval. Related entries: [collection interval](/telegraf/v1/glossary/#collection-interval), [flush jitter](/telegraf/v1/glossary/#flush-jitter), [output plugin](/telegraf/v1/glossary/#output-plugin) ## flush jitter Flush jitter is used to prevent every output plugin from sending writes simultaneously, which can overwhelm some data sinks. Each flush interval, every output plugin will sleep for a random time between zero and the flush jitter before emitting metrics. This helps smooth out write spikes when running a large number of Telegraf instances. Related entries: [flush interval](/telegraf/v1/glossary/#flush-interval), [output plugin](/telegraf/v1/glossary/#output-plugin) ## input plugin Input plugins actively gather metrics and deliver them to the core agent, where aggregator, processor, and output plugins can operate on the metrics. In order to activate an input plugin, it needs to be enabled and configured in Telegraf’s configuration file. Related entries: [aggregator plugin](/telegraf/v1/glossary/#aggregator-plugin), [collection interval](/telegraf/v1/glossary/#collection-interval), [output plugin](/telegraf/v1/glossary/#output-plugin), [processor plugin](/telegraf/v1/glossary/#processor-plugin) ## label A key-value pair attached to a plugin instance in its configuration. Use labels with [selectors](/telegraf/v1/glossary/#selector) to enable a subset of configured plugins when starting Telegraf. See [Labels and selectors](/telegraf/v1/configuration/labels-selectors/). Related entries: [selector](/telegraf/v1/glossary/#selector) ## metric buffer The metric buffer caches individual metrics when writes are failing for an output plugin. Telegraf will attempt to flush the buffer upon a successful write to the output. The oldest metrics are dropped first when this buffer fills. Related entries: [output plugin](/telegraf/v1/glossary/#output-plugin) ## output plugin Output plugins deliver metrics to their configured destination. In order to activate an output plugin, it needs to be enabled and configured in Telegraf’s configuration file. Related entries: [aggregator plugin](/telegraf/v1/glossary/#aggregator-plugin), [flush interval](/telegraf/v1/glossary/#flush-interval), [input plugin](/telegraf/v1/glossary/#input-plugin), [processor plugin](/telegraf/v1/glossary/#processor-plugin) ## parser A parser converts raw input data, such as JSON, CSV, or Prometheus exposition format, into Telegraf metrics. Input plugins that read raw data select a parser with the `data_format` option. See [input data formats](/telegraf/v1/data_formats/input/) and [Parse incoming data](/telegraf/v1/configure_plugins/input_plugins/parse-data/). Related entries: [input plugin](/telegraf/v1/glossary/#input-plugin), [serializer](/telegraf/v1/glossary/#serializer) ## precision The precision configuration setting determines how much timestamp precision is retained in the points received from input plugins. All incoming timestamps are truncated to the given precision. Telegraf then pads the truncated timestamps with zeros to create a nanosecond timestamp. Output plugins emit timestamps in nanoseconds. Valid precisions are `ns`, `us` or `µs`, `ms`, and `s`. For example, if the precision is set to `ms`, the nanosecond epoch timestamp `1480000000123456789` would be truncated to `1480000000123` in millisecond precision and then padded with zeroes to make a new, less precise nanosecond timestamp of `1480000000123000000`. Output plugins do not alter the timestamp further. The precision setting is ignored for service input plugins. Related entries: [aggregator plugin](/telegraf/v1/glossary/#aggregator-plugin), [input plugin](/telegraf/v1/glossary/#input-plugin), [output plugin](/telegraf/v1/glossary/#output-plugin), [processor plugin](/telegraf/v1/glossary/#processor-plugin), [service input plugin](/telegraf/v1/glossary/#service-input-plugin) ## processor plugin Processor plugins transform, decorate, and/or filter metrics collected by input plugins, passing the transformed metrics to the output plugins. Related entries: [aggregator plugin](/telegraf/v1/glossary/#aggregator-plugin), [input plugin](/telegraf/v1/glossary/#input-plugin), [output plugin](/telegraf/v1/glossary/#output-plugin) ## secret store A secret store is a plugin type that keeps credentials, such as passwords and tokens, out of plain-text configuration files. Plugin options reference secrets with the `@{store_id:secret_key}` syntax, and Telegraf resolves them at runtime. See [Store secrets](/telegraf/v1/configuration/secrets/). Related entries: [input plugin](/telegraf/v1/glossary/#input-plugin), [output plugin](/telegraf/v1/glossary/#output-plugin) ## selector A key-value expression that matches plugin [labels](/telegraf/v1/glossary/#label). Pass selectors with the `--select` flag to enable only plugins with matching labels. See [Labels and selectors](/telegraf/v1/configuration/labels-selectors/). Related entries: [label](/telegraf/v1/glossary/#label) ## serializer A serializer converts Telegraf metrics into an output representation, such as InfluxDB line protocol, JSON, or Graphite. Output plugins that write generic payloads select a serializer with the `data_format` option. See [output data formats](/telegraf/v1/data_formats/output/) and [Serialize outgoing data](/telegraf/v1/configure_plugins/output_plugins/serialize-data/). Related entries: [output plugin](/telegraf/v1/glossary/#output-plugin), [parser](/telegraf/v1/glossary/#parser) ## service input plugin Service input plugins are input plugins that run in a passive collection mode while the Telegraf agent is running. They listen on a socket for known protocol inputs, or apply their own logic to ingested metrics before delivering them to the Telegraf agent. Related entries: [aggregator plugin](/telegraf/v1/glossary/#aggregator-plugin), [input plugin](/telegraf/v1/glossary/#input-plugin), [output plugin](/telegraf/v1/glossary/#output-plugin), [processor plugin](/telegraf/v1/glossary/#processor-plugin) ## tracking metric A metric whose delivery is tracked through the pipeline. Queue-based service inputs, such as Kafka and MQTT consumers, use tracking metrics to acknowledge messages back to the source only after an output writes them, so metrics aren’t lost if Telegraf stops. See [tracking metrics](/telegraf/v1/concepts/metrics/#tracking-metrics). Related entries: [service input plugin](/telegraf/v1/glossary/#service-input-plugin), [metric buffer](/telegraf/v1/glossary/#metric-buffer)