The administration documentation contains all the information needed to administer a working InfluxDB installation.
This document covers setting up and managing authentication and authorization in InfluxDB.
Authentication: Authorization: Set up Authentication User Types and Privileges Authenticate Requests User Management Commands HTTP Errors HTTP Errors Note: Authentication and authorization should not be relied upon to prevent access and protect data from malicious actors. If additional security or compliance features are desired, InfluxDB should be run behind a third-party service. If InfluxDB is being deployed on a publicly accessible endpoint, we strongly recommend authentication be enabled.
Using InfluxDB OSS backup and restore utilities for online, Enterprise-compatible use and portability between InfluxDB Enterprise and InfluxDB OSS servers.
The InfluxDB OSS configuration file contains configuration settings specific to a local node.
Content Configuration overview Environment variables InfluxDB environment variables (INFLUXDB_*) GOMAXPROCS environment variable Using the configuration file Configuration file settings Global settings Metastore settings [meta] Data settings [data] Query management settings [coordinator] Retention policy settings [retention] Shard precreation settings [shard-precreation] Monitoring settings [monitor] HTTP endpoint settings [http] Subscription settings [subscriber] Graphite settings [[graphite]] CollectD settings [[collectd]] OpenTSB settings [[opentsdb]] UDP settings [[udp]] Continuous queries settings [continuous_queries] Transport Layer Security (TLS) settings [tls] Configuration overview InfluxDB is configured using the configuration file (influxdb.
Enable HTTPS and Transport Security Layer (TLS) secure communication between clients and your InfluxDB servers.
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 that runs the RPC service for backup and 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.
On this page
SHOW STATS SHOW DIAGNOSTICS Internal monitoring Useful performance metrics commands InfluxDB /metrics HTTP endpoint InfluxDB can display statistical and diagnostic information about each node. This information can be very useful for troubleshooting and performance monitoring.
SHOW STATS To see node statistics, execute the command SHOW STATS. For details on this command, see SHOW STATS in the InfluxQL specification.
The statistics returned by SHOW STATS are stored in memory only, and are reset to zero when the node is restarted.
Logging locations Redirecting HTTP request logging Structured logging Tracing Logging locations InfluxDB writes log output, by default, to stderr. Depending on your use case, this log information can be written to another location.
Running InfluxDB directly When you run InfluxDB directly, using influxd, all logs are written to stderr. You can also redirect the log output, as you would any output to stderr, like in this example:
influxd 2>$HOME/my_log_file Launched as a service sysvinit If InfluxDB was installed using a prebuilt package, and then launched as a service, stderr is redirected to /var/log/influxdb/influxd.
InfluxDB uses subscriptions to copy all written data to a local or remote endpoint. This article walks through how InfluxDB subscriptions work, how to configure them, and how to manage them.
Some customers may choose to install InfluxDB with public internet access, however doing so can inadvertently expose your data and invite unwelcome attacks on your database. Check out the sections below for how protect the data in your InfluxDB instance.
Enabling authentication Password protect your InfluxDB instance to keep any unauthorized individuals from accessing your data.
Resources: Set up Authentication
Managing users and permissions Restrict access by creating individual users and assigning them relevant read and/or write permissions.
1.x API compatibility and stability One of the more important aspects of the 1.0 release is that this marks the stabilization of our API and storage format. Over the course of the last three years we’ve iterated aggressively, often breaking the API in the process. With the release of 1.0 and for the entire 1.x line of releases we’re committing to the following:
No breaking HTTP API changes When it comes to the HTTP API, if a command works in 1.
Upgrading InfluxDB 1.3 / 1.4 (no TSI Preview) to 1.6.x (TSI enabled) Upgrading InfluxDB 1.3 - 1.4 (TSI Preview enabled) to 1.6.x (TSI enabled) Upgrading InfluxDB 1.0 - 1.4 to 1.6.x Upgrading InfluxDB Enterprise clusters Upgrading InfluxDB 1.3 / 1.4 (no TSI Preview) to 1.6.x (TSI enabled) Starting with the InfluxDB 1.6 release, enabling Time Series Index (TSI) is recommended for all customers. To learn more about TSI, see: