InfluxDB Enterprise guides

Enable HTTPS for InfluxDB Enterprise

Enabling HTTPS encrypts the communication between clients and the InfluxDB Enterprise server, and between nodes in the cluster. When configured with a signed certificate, HTTPS can also verify the authenticity of the InfluxDB Enterprise server to connecting clients. This pages outlines how to set up HTTPS with InfluxDB Enterprise using either a signed or self-signed certificate. InfluxData strongly recommends enabling HTTPS, especially if you plan on sending requests to InfluxDB Enterprise over a network.

Fine-grained authorization in InfluxDB Enterprise

Use fine-grained authorization (FGA) in InfluxDB Enterprise to control user access at the database, measurement, and series levels. Note: InfluxDB OSS controls access at the database level only. You must have admin permissions to set up FGA. Set up fine-grained authorization Enable authentication in your InfluxDB configuration file. Create users through the InfluxDB query API. CREATEUSERusernameWITHPASSWORD'password'For more information, see User management commands. Ensure that you can access the meta node API (port 8091 by default).

Migrate InfluxDB OSS instances to InfluxDB Enterprise clusters

Migrate a running instance of InfluxDB open source (OSS) to an InfluxDB Enterprise cluster.

Rebalancing InfluxDB Enterprise clusters

Manually rebalance an InfluxDB Enterprise cluster to ensure: Shards are evenly distributed across all data nodes in the cluster Every shard is on n number of nodes, where n is the replication factor. Why rebalance? Rebalance a cluster any time you do one of the following: Expand capacity and increase write throughput by adding a data node. Increase availability and query throughput, by either: Adding data nodes and increasing the replication factor.

Replacing InfluxDB Enterprise cluster meta nodes and data nodes

Introduction Nodes in an InfluxDB Enterprise cluster may need to be replaced at some point due to hardware needs, hardware issues, or something else entirely. This guide outlines processes for replacing both meta nodes and data nodes in an InfluxDB Enterprise cluster. Concepts Meta nodes manage and monitor both the uptime of nodes in the cluster as well as distribution of shards among nodes in the cluster. They hold information about which data nodes own which shards; information on which the anti-entropy (AE) process depends.

Setup of SMTP server for InfluxDB Enterprise

InfluxDB Enterprise requires a functioning SMTP server to invite users to the console. If you’re working on Ubuntu 14.04 and are looking for an SMTP server to use for development purposes, the following steps will get you up and running with MailCatcher. Note that MailCatcher will NOT send actual emails, it merely captures email traffic from the cluster and allows you to view it in a browser. If you want to invite other users you must set up an actual email server that the InfluxDB Enterprise process can use.