Documentation

Configure Chronograf

Configure Chronograf by passing command line options when starting the Chronograf service. Or set custom default configuration options in the filesystem so they don’t have to be passed in when starting Chronograf.

Start the Chronograf service

Use one of the following commands to start Chronograf:

  • If you installed Chronograf using an official Debian or RPM package and are running a distro with systemd. For example, Ubuntu 15 or later.

    systemctl start chronograf
    
  • If you installed Chronograf using an official Debian or RPM package:

    service chronograf start
    
  • If you built Chronograf from source:

    $GOPATH/bin/chronograf
    

Set custom default Chronograf configuration options

Custom default Chronograf configuration settings can be defined in /etc/default/chronograf. This file consists of key-value pairs. See keys (environment variables) for Chronograf configuration options, and set values for the keys you want to configure.

HOST=0.0.0.0
PORT=8888
TLS_CERTIFICATE=/path/to/cert.pem
TOKEN_SECRET=MySup3rS3cretT0k3n
LOG_LEVEL=info

Note: /etc/default/chronograf is only created when installing the .deb or .rpm` package.

Set up security, organizations, and users

To set up security for Chronograf, configure:

After you configure OAuth 2.0 authentication, you can set up multiple organizations, roles, and users. For details, check out the following topics:


Was this page helpful?

Thank you for your feedback!


Introducing InfluxDB Clustered

A highly available InfluxDB 3.0 cluster on your own infrastructure.

InfluxDB Clustered is a highly available InfluxDB 3.0 cluster built for high write and query workloads on your own infrastructure.

InfluxDB Clustered is currently in limited availability and is only available to a limited group of InfluxData customers. If interested in being part of the limited access group, please contact the InfluxData Sales team.

Learn more
Contact InfluxData Sales

The future of Flux

Flux is going into maintenance mode. You can continue using it as you currently are without any changes to your code.

Flux is going into maintenance mode and will not be supported in InfluxDB 3.0. This was a decision based on the broad demand for SQL and the continued growth and adoption of InfluxQL. We are continuing to support Flux for users in 1.x and 2.x so you can continue using it with no changes to your code. If you are interested in transitioning to InfluxDB 3.0 and want to future-proof your code, we suggest using InfluxQL.

For information about the future of Flux, see the following: