Release Announcement: Telegraf 1.8.0 and InfluxDB 1.6.3

4 minutes

A new feature-bearing release for Telegraf is now available:

The binaries for the latest open source release can be found on our downloads page.

Many thanks to the more than 60 open source community members who contributed to this effort!

Key feature highlights from the release include:

  • Added Azure Monitor (azure_monitor) plugin for sending custom metrics to Azure Monitor.
  • New VMware vSphere (vsphere) monitoring plugin to pull metrics from vCenter Clusters, Hosts, VMs, and Datastores.
  • The Kafka Output (kafka) plugin performance has been tremendously improved and now has an option to use lz4 compression.
  • Added the ability to write data in the Splunk metrics format which means you can send metrics directly to a Splunk HEC.
  • 22 new plugins and over 70 improvements and bug fixes.

New Inputs

  1. ActiveMQ (activemq)
    • This plugin gathers queues, topics & subscribers metrics using ActiveMQ Console API.
  2. Beanstalkd (beanstalkd)
    • This plugin collects server and tube stats, reported by stats and stats-tube commands respectively.
  3. File Count (filecount)
    • This plugin counts files in the directories as a specific interval that match specific criteria.
  4. File (file)
    • Leverage this plugin to parse the contents of a set of files using the selected input data format.
  5. Icinga2 (icinga2)
    • This uses the Icinga2 remote API to gather status on running services and hosts.
  6. Kibana (kibana)
    • This will query the Kibana status API to obtain its health and some other useful metrics.
  7. PgBouncer (pgbouncer)
  8. Temperature (temp)
    • Gather the temperature of your server at a regular interval.
  9. Tengine (tengine)
  10. VMware vSphere (vsphere)
    • The VMware vSphere plugin uses the vSphere API to gather metrics from multiple vCenter servers including Clusters, Hosts, VMs, and Datastores.
  11. X509 Cert (x509_cert)
    • This plugin provides information about X509 certificate such as age and expiration date.

New Processors

  1. Enum (enum)
    • Use this plugin to rewrite status codes such as red, amber and green to numeric values such as 0, 1, and 2 respectively.
  2. Parser (parser)
    • This plugin parses specified fields in a data format and creates new metrics based on its contents.
  3. Rename (rename)
    • This gives you the ability to rename measurements, fields, and tags before they are written to your outputs.
  4. Strings (strings)
    • This plugin allows you to apply common string function such as lowercase or trim to your measurement, tag or field.

New Aggregators

  1. ValueCounter (valuecounter)
    • This plugin counts the occurrence of values in fields and can be used for counting things like HTTP status codes.

New Outputs

  1. Azure Monitor (azure_monitor)
    • Use this plugin to send custom application metrics to Azure Monitor.

New Parsers

  1. CSV (csv)
    • This parser creates metrics from a document containing comma separated values.
  2. GROK (grok)
    • This has been split out from the logparser plugin into a parser that can be used with any plugin.
  3. Logfmt (logfmt)
    • This parses data in logfmt format, which is the format we use in InfluxDB.

New Serializers

  1. Splunk Metrics (splunkmetric)
    • This serializer formats and outputs the metric data in a format that can be consumed by a Splunk metrics index.

InfluxDB 1.6.3

A new maintenance release for InfluxDB is available now.

This maintenance release for InfluxDB includes the following updates:

  1. Remove TSI1 HLL sketches from heap.
  2. Fix the inherited interval for derivative and others.
    • The inherited interval from an outer query should not have caused an inner query to fail because inherited intervals are only implicitly passed to inner queries that support group by time functionality. Since an inner query with a derivative doesn’t support grouping by time and the inner query itself doesn’t specify a time, the outer query shouldn’t have invalidated the inner query.
  3. Fix the derivative and other time ranges for aggregate data.
    • The derivative function and others similar to it would preload themselves with data so that the first interval would be the start of the time range. That meant reading data outside of the time range. One change to the shard mapper made in v1.4.0 caused the shard mapper to constrict queries to the intervals given to the shard mapper. This was correct because the shard mapper can only deal with times it has mapped, but this broke the functionality of looking back into the past for the derivative and other functions that used that functionality. The query compiler has been updated with an additional attribute that records how many intervals in the past will need to be read so that the shard mapper can include extra times that it may not necessarily read from, but may be queried because of the above described functionality.

The binaries for the latest open source release can be found on our downloads page.

Related Blog Posts

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top