Documentation

InfluxDB ports

This page documents an earlier version of InfluxDB. InfluxDB v2 is the latest stable version.

Enabled ports

8086

The default port that runs the InfluxDB HTTP service. Configure this port in the configuration file.

Resources API Reference

8088

The default port used by the RPC service for RPC calls made by the CLI for backup and restore operations (influxdb backup and influxd restore). Configure this port in the configuration file.

Resources Backup and Restore

Disabled ports

2003

The default port that runs the Graphite service. Enable and configure this port in the configuration file.

Resources Graphite README

4242

The default port that runs the OpenTSDB service. Enable and configure this port in the configuration file.

Resources OpenTSDB README

8089

The default port that runs the UDP service. Enable and configure this port in the configuration file.

Resources UDP README

25826

The default port that runs the Collectd service. Enable and configure this port in the configuration file.

Resources Collectd README


Was this page helpful?

Thank you for your feedback!


Introducing InfluxDB Clustered

A highly available InfluxDB 3.0 cluster on your own infrastructure.

InfluxDB Clustered is a highly available InfluxDB 3.0 cluster built for high write and query workloads on your own infrastructure.

InfluxDB Clustered is currently in limited availability and is only available to a limited group of InfluxData customers. If interested in being part of the limited access group, please contact the InfluxData Sales team.

Learn more
Contact InfluxData Sales

The future of Flux

Flux is going into maintenance mode. You can continue using it as you currently are without any changes to your code.

Flux is going into maintenance mode and will not be supported in InfluxDB 3.0. This was a decision based on the broad demand for SQL and the continued growth and adoption of InfluxQL. We are continuing to support Flux for users in 1.x and 2.x so you can continue using it with no changes to your code. If you are interested in transitioning to InfluxDB 3.0 and want to future-proof your code, we suggest using InfluxQL.

For information about the future of Flux, see the following: