Administering InfluxDB

Backing up and restoring in InfluxDB OSS

Using InfluxDB OSS backup and restore utilities for online, Enterprise-compatible use and portability between InfluxDB Enterprise and InfluxDB OSS servers.

Configuring InfluxDB OSS

The InfluxDB OSS configuration file contains configuration settings specific to a local node. Content Configuration overview Environment variables 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] Configuration overview InfluxDB is configured using the configuration file (influxdb.

Enabling HTTPS with InfluxDB

Enabling HTTPS secures the communication between clients and the InfluxDB server, and, in some cases, HTTPS verifies the authenticity of the InfluxDB server to clients. If you plan on sending requests to InfluxDB over a public network, InfluxData strongly recommends that you enable HTTPS. Otherwise the data will be publicly available to any unauthenticated user. Requirements To enable HTTPS with InfluxDB, you’ll need an existing or new InfluxDB instance and a Transport Layer Security (TLS) certificate (also known as a Secured Sockets Layer (SSL) certificate).

InfluxDB ports

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.

InfluxDB server monitoring

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. The statistics returned by SHOW STATS are stored in memory only, and are reset to zero when the node is restarted.

Logging and tracing in InfluxDB

Content 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.

Managing InfluxDB security

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. If InfluxDB is being deployed on a publicly accessible endpoint, we strongly recommend authentication be enabled. Otherwise the data will be publicly available to any unauthenticated user. 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.

Stability and compatibility

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 to InfluxDB 1.5.x

Upgrading from 1.3 / 1.4 (no TSI Preview) to 1.5.x (TSI enabled) Upgrading from 1.4 (TSI Preview enabled) to 1.5.x (TSI enabled) Upgrading from 1.0-1.4 to 1.5.x (TSI enabled) Upgrading InfluxDB Enterprise clusters Upgrading from 1.3 / 1.4 (no TSI Preview) to 1.5.x (TSI enabled) Starting with the InfluxDB 1.5 release, enabling Time Series Index (TSI) is recommended for all customers. To learn more about TSI, see: Time Series Index (TSI) overview Time Series Index (TSI) details The upgrade steps below guide you in upgrading InfluxDB OSS and InfluxDB Enterprise, enabling TSI functionality.