InfluxDB Enterprise guides and tutorials
This guide describes how to enable HTTPS for InfluxDB Enterprise. Setting up HTTPS secures the communication between clients and the InfluxDB Enterprise server, and, in some cases, HTTPS verifies the authenticity of the InfluxDB Enterprise server to clients.
If you plan on sending requests to InfluxDB Enterprise over a network, we strongly recommend that you set up HTTPS.
Requirements To set up HTTPS with InfluxDB Enterprise, you’ll need an existing or new InfluxDB Enterprise instance and a Transport Layer Security (TLS) certificate (also known as a Secured Sockets Layer (SSL) certificate).
Controlling access to data with InfluxDB Enterprise’s fine-grained authorization In InfluxDB OSS, access control operates only at a database level. In InfluxDB Enterprise, fine-grained authorization can be used to control access at a measurement or series level.
Concepts To use fine-grained authorization (FGA), you must first enable authentication in your configuration file. Then the admin user needs to create users through the query API and grant those users explicit read and/or write privileges per database.
IMPORTANT Due to a known issue in InfluxDB, attempts to upgrade an InfluxDB OSS instance to InfluxDB Enterprise will fail. A fix is in place and will be released with InfluxDB v1.7.10. Until InfluxDB v1.7.10 is released, DO NOT attempt to migrate an InfluxDB OSS instance to InfluxDB Enterprise by following the steps in this guide.
We will update this guide to reflect the new upgrade process after the release of InfluxDB 1.
Introduction This guide describes how to manually rebalance an InfluxDB Enterprise cluster. Rebalancing a cluster involves two primary goals:
Evenly distribute shards across all data nodes in the cluster Ensure that every shard is on N number of nodes, where N is determined by the retention policy’s replication factor Rebalancing a cluster is essential for cluster health. Perform a rebalance if you add a new data node to your cluster.
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.
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.
Support and feedback
Thank you for being part of our community!
We welcome and encourage your feedback and bug reports for InfluxDB and this documentation.
To find support, the following resources are available:
InfluxDB Cloud and InfluxDB Enterprise customers can contact InfluxData Support.