This is archived documentation for InfluxData product versions that are no longer maintained. For newer documentation, see the latest InfluxData documentation.
- What Kapacitor event handlers are supported in Chronograf?
- What applications are supported in Chronograf?
- How do I connect Chronograf to an InfluxEnterprise cluster?
- What visualization types does Chronograf support?
- What does the status column indicate on the Host List page?
- Why is my host’s status red when data is still arriving?
Known Issues
- Why is my query’s field key order inconsistent?
- Why does the query builder break after I add my template variable to a query?
What Kapacitor event handlers are supported in Chronograf?
Chronograf integrates with Kapacitor, InfluxData’s data processing platform, to send alert messages to event handlers. Chronograf supports the following event handlers:
- Alerta
- Exec
- HipChat
- HTTP/Post
- Log (available in versions 1.3.1.0+)
- OpsGenie
- PagerDuty
- Sensu
- Slack
- SMTP/Email
- Talk
- Telegram
- TCP
- VictorOps
To configure a Kapacitor event handler in Chronograf, install Kapacitor and connect it to Chronograf. The Configure Kapacitor page includes the event handler configuration options; see the Configure Kapacitor Event Handlers guide for more information.
What applications are supported in Chronograf?
Chronograf offers pre-created dashboards for several Telegraf input plugins/applications. We list those applications below and link to their Telegraf documentation:
- Apache
- Consul
- Docker
- Elastic
- etcd
- HAProxy
- IIS
- InfluxDB
- Kubernetes
- Memcached
- Mesos
- MongoDB
- MySQL
- Network
- NGINX
- NSQ
- PHPfpm
- Ping
- PostgreSQL
- Processes
- RabbitMQ
- Redis
- Riak
- System
- Varnish
- Windows Performance Counters
Enable and disable applications in your Telegraf configuration file. See the Telegraf Configuration documentation for more information.
How do I connect Chronograf to an InfluxEnterprise cluster?
The connection details form requires additional information when connecting Chronograf to an InfluxEnterprise cluster.
When you enter InfluxDB’s HTTP bind address in the Connection String input, Chronograf automatically checks if that InfluxDB instance is a data node.
If it is a data node, Chronograf automatically adds the Meta Service Connection URL input to the connection details form.
Enter the HTTP bind address of one of your cluster’s meta nodes into that input and Chronograf takes care of the rest.
Note that the example above assumes that you do not have authentication enabled. If you have authentication enabled, the form requires username and password information. For more details about monitoring an InfluxEnterprise cluster, see the Monitor an InfluxEnterprise Cluster guide.
What visualization types does Chronograf support?
Chronograf’s dashboards support six visualization types.
Line
Show time-series in a line graph.
Stacked
Show time-series arranged on top of each other.
Step-Plot
Show time-series in a staircase graph.
SingleStat
Show the time-series’ single most recent value.
If a cell’s query includes a GROUP BY tag clause, Chronograf sorts the different series lexicographically and shows the most recent field value associated with the first series.
For example, if a query groups by the name tag key and name has two tag values (chronelda and chronz), Chronograf shows the most recent field value associated with the chronelda series.
If a cell’s query includes more than one field key in the SELECT clause, Chronograf returns the most recent field value associated with the first field key in the SELECT clause.
For example, if a query’s SELECT clause is SELECT "chronogiraffe","chronelda", Chronograf shows the most recent field value associated with the chronogiraffe field key.
Line+Stat
Show time-series in a line graph and overlay the time-series’ single most recent value.
Bar
Show time-series in a bar chart. Bar graphs are available in versions 1.3.3.0+.
What does the status column indicate on the Host List page?
The status icon is a high-level measure of your host’s health. If Chronograf has not received data from a host for the past minute, the status icon is red. If Chronograf has received data from a host within the past minute, the status icon is green.
Why is my host’s status red when data is still arriving?
There are several possible explanations for an inaccurate red status icon:
The status icon depends on your host’s local time in UTC. Use the Network Time Protocol (NTP) to synchronize time between hosts; if hosts’ clocks aren’t synchronized with NTP, the status icon can be inaccurate.
The status icon turns red when Chronograf has not received data from a host for the past minute. Chronograf uses data from Telegraf to perform that calculation. By default, Telegraf sends data in ten-second intervals; you can change that interval setting in Telegraf’s configuration file. If you configure the setting to an interval that’s greater than one minute, Chronograf assumes that the host is not reporting data and changes the status icon to red.
Why is my query’s field key order inconsistent?
In versions 1.3.0-1.3.1, Chronograf doesn’t preserve the order of the items in the SELECT clause in query editor mode.
Chronograf may change the order of the items in the SELECT clause after it executes the query and populates the cell with the query results.
This issue affects the SingleStat and Line+Stat graph types.
If a cell’s query includes more than one field key in the SELECT clause, Chronograf returns the most recent stat associated with the first field key in the SELECT clause.
If you sorted the field keys in your query to rely on that behavior, it is important to note that Chronograf may change that order when it executes your query.
This is a known issue and it is fixed in versions 1.3.2.0+.
Why does the query builder break after I add my template variable to a query?
Currently, adding a template variable to a cell’s query renders the query builder unusable.
If you click on a database in the builder’s Databases column after adding a template variable to your query, Chronograf simply overwrites your existing query.
Note that this behavior does not apply to Chronograf’s pre-created template variable: :dashboardTime:.
This is a known issue and it will be fixed in a future release.