Documentation

Create scrapable endpoints

This page documents an earlier version of InfluxDB OSS. InfluxDB 3 Core is the latest stable version.

InfluxDB scrapers can collect data from any HTTP(S)-accessible endpoint that returns data in the Prometheus data format. The links below provide information about the Prometheus data format and tools and clients that generate Prometheus-formatted metrics.

Prometheus Node Exporter

The Prometheus Node Exporter exposes a wide variety of hardware- and kernel-related metrics for *nix systems.

Monitoring linux host metrics with the Node Exporter

Prometheus exporters and integrations

Prometheus exporters and integrations export Prometheus metrics from third-party systems or services.

List of third-party exporters
Write a custom Prometheus exporter

Prometheus client libraries

Prometheus client libraries instrument applications for each of their respective languages. Application metrics are output to an HTTP(S) endpoint where they can be scraped.

Instrumenting a Go application for Prometheus
Writing Prometheus client libraries


Was this page helpful?

Thank you for your feedback!


New in InfluxDB 3.5

Key enhancements in InfluxDB 3.5 and the InfluxDB 3 Explorer 1.3.

See the Blog Post

InfluxDB 3.5 is now available for both Core and Enterprise, introducing custom plugin repository support, enhanced operational visibility with queryable CLI parameters and manual node management, stronger security controls, and general performance improvements.

InfluxDB 3 Explorer 1.3 brings powerful new capabilities including Dashboards (beta) for saving and organizing your favorite queries, and cache querying for instant access to Last Value and Distinct Value cachesβ€”making Explorer a more comprehensive workspace for time series monitoring and analysis.

For more information, check out:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On November 3, 2025, 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