Documentation

Analyze logs with Chronograf

Chronograf gives you the ability to view, search, filter, visualize, and analyze log information from a variety of sources. This helps to recognize and diagnose patterns, then quickly dive into logged events that lead up to events.

Set up logging

Logs data is a first class citizen in InfluxDB and is populated using available log-related Telegraf input plugins:

View logs in Chronograf

Chronograf has a dedicated log viewer accessed by clicking the Log Viewer button in the left navigation.

Log viewer in the left nav

The log viewer provides a detailed histogram showing the time-based distribution of log entries color-coded by log severity. It also includes a live stream of logs that can be searched, filtered, and paused to analyze specific time ranges. Logs are pulled from the syslog measurement. Other log inputs and alternate log measurement options will be available in future updates.

Chronograf log viewer

Search and filter logs

Search for logs using keywords or regular expressions. They can also be filtered by clicking values in the log table such as severity or facility. Any tag values included with the log entry can be used as a filter.

You can also use search operators to filter your results. For example, if you want to find results with a severity of critical that don’t mention RSS, you can enter: severity == crit and -RSS.

Searching and filtering logs

Note: The log search field is case-sensitive.

To remove filters, click the × next to the tag key by which you no longer want to filter.

Select specific times

In the log viewer, you can select time ranges from which to view logs. By default, logs are streamed and displayed relative to “now,” but it is possible to view logs from a past window of time. timeframe selection allows you to go to to a specific event and see logs for a time window both preceding and following that event. The default window is one minute, meaning the graph shows logs from thirty seconds before and the target time. Click the dropdown menu change the window.

Selecting time ranges

Configure the log viewer

The log viewer can be customized to fit your specific needs. Open the log viewer configuration options by clicking the gear button in the top right corner of the log viewer. Once done, click Save to apply the changes.

Log viewer configuration options

Severity colors

Every log severity is assigned a color which is used in the display of log entries. To customize colors, select a color from the available color dropdown.

Table columns

Columns in the log viewer are auto-populated with all fields and tags associated with your log data. Each column can be reordered, renamed, and hidden or shown.

Severity format

“Severity Format” specifies how the severity of log entries is displayed in your log table. Below are the options and how they appear in the log table:

Severity FormatDisplay
DotLog severity format 'Dot'
Dot + TextLog severity format 'Dot + Text'
TextLog severity format 'Text'

Truncate or wrap log messages

By default, text in Log Viewer columns is truncated if it exceeds the column width. You can choose to wrap the text instead to display the full content of each cell.

Select the Truncate or Wrap option to determine how text appears when it exceeds the width of the cell.

To copy the complete, un-truncated log message, select the message cell and click Copy.

Show or hide the log status histogram

The Chronograf Log Viewer displays a histogram of log status.

To hide the log status histogram, click the icon in the top right corner of the histogram.

To show the log status histogram, click the icon in the top right corner of the log output.

Logs in dashboards

An incredibly powerful way to analyze log data is by creating dashboards that include log data. This is possible by using the Table visualization type to display log data in your dashboard.

Correlating logs with other metrics

This type of visualization allows you to quickly identify anomalies in other metrics and see logs associated with those anomalies.


Was this page helpful?

Thank you for your feedback!


InfluxDB OSS 2.9.0: API tokens are hashed by default

Stronger token security in InfluxDB OSS 2.9.0 — tokens are hashed on disk by default. Existing tokens are hashed on first startup and can’t be recovered afterward. Capture any plaintext tokens you still need before you upgrade.

View InfluxDB OSS 2.9.0 release notes

Hashed tokens authenticate exactly like unhashed tokens — clients and integrations keep working.

Also new in 2.9.0:

  • Configurable backup compression
  • Restore support for backups containing hashed tokens
  • Tighter Edge Data Replication queue validation
  • Flux upgrade
  • Compaction reliability improvements

Key enhancements in Explorer 1.8

Explorer 1.8 is now available with streaming data subscriptions (beta), line protocol preview, and query history & saved queries.

View Explorer 1.8 release notes

Explorer 1.8 includes new features and improvements that make it easier to ingest, explore, and manage data.

Highlights:

  • Streaming data subscriptions (beta): Stream data into Explorer from MQTT, Kafka, and AMQP sources.
  • Line protocol preview: Preview line protocol, schema, and parse errors before data is written.
  • Custom sample data: Generate custom sample datasets with line protocol and schema preview.
  • Query history and saved queries: Browse query history and save/re-run named queries.
  • Retention period management: Set, update, or clear retention periods on databases and tables.

For more details, see Explorer 1.8 release notes

InfluxDB 3.9: Performance upgrade preview

InfluxDB 3 Enterprise 3.9 includes a beta of major performance upgrades with faster single-series queries, wide-and-sparse table support, and more.

InfluxDB 3 Enterprise 3.9 includes a beta of major performance and feature updates.

Key improvements:

  • Faster single-series queries
  • Consistent resource usage
  • Wide-and-sparse table support
  • Automatic distinct value caches for reduced latency with metadata queries

Preview features are subject to breaking changes.

For more information, see:

Telegraf Enterprise now in public beta

Get early access to the Telegraf Controller and provide feedback to help shape the future of Telegraf Enterprise.

See the Blog Post

The upcoming Telegraf Enterprise offering is for organizations running Telegraf at scale and is comprised of two key components:

  • Telegraf Controller: A control plane (UI + API) that centralizes Telegraf configuration management and agent health visibility.
  • Telegraf Enterprise Support: Official support for Telegraf Controller and Telegraf plugins.

Join the Telegraf Enterprise beta to get early access to the Telegraf Controller and provide feedback to help shape the future of Telegraf Enterprise.

For more information:

Telegraf Controller v0.0.7-beta now available

Telegraf Controller v0.0.7-beta is now available with new features, improvements, bug fixes, and an important breaking change.

View the release notes
Download Telegraf Controller v0.0.7-beta

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On May 27, 2026, the latest tag for InfluxDB Docker images will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments.

If using Docker to install and run InfluxDB, the latest tag will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments. For example, if using Docker to run InfluxDB v2, replace the latest version tag with a specific version tag in your Docker pull command–for example:

docker pull influxdb:2