Administering InfluxDB

Backup and restore

Backups There are two types of data to backup, the metastore and the metrics themselves. The metastore is backed up in its entirety. The metrics are backed up per-database in a separate operation from the metastore backup. Per-database backups can be full, incremental (since a RFC3339 formatted time), or for a specific shard ID. Note: Backups are not interchangeable between InfluxDB OSS and InfluxDB Enterprise. You cannot restore an OSS backup to an InfluxDB Enterprise data node, nor can you restore an InfluxDB Enterprise backup to an OSS instance.

Configuring InfluxDB

The InfluxDB 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 [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.

Differences between InfluxDB 1.4 and 1.3

This page aims to ease the transition from InfluxDB 1.3 to InfluxDB 1.4. For a comprehensive list of the differences between the versions see InfluxDB’s Changelog. Content TSI Release Prometheus Read-Write API Configuration File Byte Simplification InfluxQL Updates SHOW CARDINALITY Ranged Meta Queries Operators Functions Other TSI release Version 1.3.0 marked the first official release of InfluxDB’s new time series index (TSI) engine. Additional improvements have been made to the TSI engine for 1.

Differences between InfluxDB 1.4 and versions prior to 1.3

If you’re using version 1.3, please see Differences Between InfluxDB 1.4 and 1.3. Users looking to upgrade to InfluxDB 1.4 from versions prior to 1.3 should view the following pages in our documentation. 1.2 users: Differences Between InfluxDB 1.3 and 1.2 1.1 users: Differences Between InfluxDB 1.2 and 1.1 1.0 users: Differences Between InfluxDB 1.1 and 1.0 0.13 users: Differences Between InfluxDB 1.0 and 0.13 0.12 users: Differences Between InfluxDB 0.

HTTPS setup for InfluxDB

This guide describes how to enable HTTPS with InfluxDB. Setting up 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 network, we strongly recommend that you set up HTTPS. Requirements To set up 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).

Logging in InfluxDB

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 If you run InfluxDB directly, using influxd, all logs will be written to stderr. You may redirect this log output as you would any output to stderr like so: influxd 2>$HOME/my_log_file Launched as a service sysvinit If InfluxDB was installed using a pre-built 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. 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 their permissions Restrict access by creating individual users and assigning them relevant read and/or write permissions.

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.

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 from previous versions

This page outlines process for upgrading from: Version 0.12-1.3 to 1.4 Version 0.10 or 0.11 to 1.4 Upgrade from 0.12-1.3 to 1.4 Download InfluxDB version 1.4 Update the configuration file Migrate any customizations in the 1.4 configuration file to the 1.4 configuration file. Restart the process Check out the new features outlined in Differences between InfluxDB 1.4 and 1.3 Upgrade from 0.10 or 0.11 to 1.4 Note: 0.10 users will need to convert any remaining b1 and bz1 shards to TSM format before following the instructions below.