Documentation

View task run history and logs

When an InfluxDB task runs, a run record is created in the task’s history. Logs associated with each run provide relevant log messages, timestamps, and the exit status of the run attempt.

Use the InfluxDB user interface (UI), the influx command line interface (CLI), or the InfluxDB /api/v2 API to view task run histories and associated logs.

InfluxDB doesn’t guarantee that a task will run at the scheduled time. During busy periods, tasks are added to the run queue and processed in order of submission. The scheduled start time and actual start time can be viewed in the logs under scheduledFor and startedAt.

Task execution time doesn’t affect the time range queried. Tasks will query over the set time range as if executed on schedule regardless of delay.

View a task’s run history in the InfluxDB UI

  1. In the navigation menu on the left, select Tasks.

  2. Hover over the task you want to run and click the icon.

  3. Select View Task Runs.

View task run logs

To view logs associated with a run, click View Logs next to the run in the task’s run history.

View a task’s run history with the influx CLI

Use the influx task run list command to view a task’s run history.

# List all tasks to find the ID of the task to run
influx task list

# Use the task ID to view the run history of a task
influx task run list --task-id=0000000000000000

Detailed run logs are not currently available in the influx CLI.

To retry failed task runs, see how to run tasks.

View logs for a task with the InfluxDB API

Use the /api/v2/tasks/TASK_ID/logs InfluxDB API endpoint to view the log events for a task and exclude additional task metadata.

GET http://localhost:8086/api/v2/tasks/TASK_ID/logs

View a task’s run history with the InfluxDB API

Use the /tasks/TASK_ID/runs InfluxDB API endpoint to view a task’s run history.

GET http://localhost:8086/api/v2/tasks/{taskID}/runs

View task run logs with the InfluxDB API

To view logs associated with a run, use the /api/v2/tasks/TASK_ID/runs/RUN_ID/logs InfluxDB API endpoint.

GET http://localhost:8086/api/v2/tasks/TASK_ID/runs/RUN_ID/logs

To retry failed task runs, see how to run tasks.


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

InfluxDB Cloud powered by TSM