Documentation

Use pre-created dashboards in Chronograf

Overview

Pre-created dashboards are delivered with Chronograf depending on which Telegraf input plugins you have enabled and are available from the Host List page. These dashboards, which are built in and not editable, include cells with data visualizations for metrics that are relevant to data sources you are likely to be using.

Note that these pre-created dashboards cannot be cloned or customized. They appear only as part of the Host List view and are associated with metrics gathered from a single host. Dashboard templates are also available and deliver a solid starting point for customizing your own unique dashboards based on the Telegraf plugins enabled and operate across one or more hosts. For details, see Dashboard templates.

Requirements

The pre-created dashboards automatically appear in the Host List page to the right of hosts based on which Telegraf input plugins you have enabled. Check the list below for applications that you are interested in using and make sure that you have the required Telegraf input plugins enabled.

Use pre-created dashboards

Pre-created dashboards are delivered in Chronograf installations and are ready to be used when you have the required Telegraf input plugins enabled.

To view a pre-created dashboard:

  1. Open Chronograf in your web browser and click Host List in the navigation bar.
  2. Select an application listed under Apps. By default, the system app should be listed next to a host listing. Other apps appear depending on the Telegraf input plugins that you have enabled. The selected application appears showing pre-created cells, based on available measurements.

Create or edit dashboards

Find a list of apps (pre-created dashboards) available to use with Chronograf below. For each app, you’ll find:

  • Required Telegraf input plugins for the app
  • JSON files included in the app
  • Cell titles included in each JSON file

The JSON files for apps are included in the /usr/share/chronograf/canned directory. Find information about the configuration option --canned-path on the Chronograf configuration options page.

Enable and disable apps in your Telegraf configuration file (by default, /etc/telegraf/telegraf.conf). See Configuring Telegraf for details.

Apps (pre-created dashboards):

apache

Required Telegraf plugin: Apache input plugin

apache.json

  • “Apache Bytes/Second”
  • “Apache - Requests/Second”
  • “Apache - Total Accesses”

consul

Required Telegraf plugin: Consul input plugin

consul_http.json

  • “Consul - HTTP Request Time (ms)”

consul_election.json

  • “Consul - Leadership Election”

consul_cluster.json

  • “Consul - Number of Agents”

consul_serf_events.json

  • “Consul - Number of serf events”

docker

Required Telegraf plugin: Docker input plugin

docker.json

  • “Docker - Container CPU %”
  • “Docker - Container Memory (MB)”
  • “Docker - Containers”
  • “Docker - Images”
  • “Docker - Container State”

docker_blkio.json

  • “Docker - Container Block IO”

docker_net.json

  • “Docker - Container Network”

elasticsearch

Required Telegraf plugin: Elasticsearch input plugin

elasticsearch.json

  • “ElasticSearch - Query Throughput”
  • “ElasticSearch - Open Connections”
  • “ElasticSearch - Query Latency”
  • “ElasticSearch - Fetch Latency”
  • “ElasticSearch - Suggest Latency”
  • “ElasticSearch - Scroll Latency”
  • “ElasticSearch - Indexing Latency”
  • “ElasticSearch - JVM GC Collection Counts”
  • “ElasticSearch - JVM GC Latency”
  • “ElasticSearch - JVM Heap Usage”

haproxy

Required Telegraf plugin: HAProxy input plugin

haproxy.json

  • “HAProxy - Number of Servers”
  • “HAProxy - Sum HTTP 2xx”
  • “HAProxy - Sum HTTP 4xx”
  • “HAProxy - Sum HTTP 5xx”
  • “HAProxy - Frontend HTTP Requests/Second”
  • “HAProxy - Frontend Sessions/Second”
  • “HAProxy - Frontend Session Usage %”
  • “HAProxy - Frontend Security Denials/Second”
  • “HAProxy - Frontend Request Errors/Second”
  • “HAProxy - Frontend Bytes/Second”
  • “HAProxy - Backend Average Response Time (ms)”
  • “HAProxy - Backend Connection Errors/Second”
  • “HAProxy - Backend Queued Requests/Second”
  • “HAProxy - Backend Average Request Queue Time (ms)”
  • “HAProxy - Backend Error Responses/Second”

iis

Required Telegraf plugin: Windows Performance Counters input plugin

win_websvc.json

  • “IIS - Service”

influxdb

Required Telegraf plugin: InfluxDB input plugin

influxdb_database.json

  • “InfluxDB - Cardinality”

influxdb_httpd.json

  • “InfluxDB - Write HTTP Requests”
  • “InfluxDB - Query Requests”
  • “InfluxDB - Client Failures”

influxdb_queryExecutor.json

  • “InfluxDB - Query Performance”

influxdb_write.json

  • “InfluxDB - Write Points”
  • “InfluxDB - Write Errors”

kubernetes

kubernetes_node.json

  • “K8s - Node Millicores”
  • “K8s - Node Memory Bytes”

kubernetes_pod_container.json

  • “K8s - Pod Millicores”
  • “K8s - Pod Memory Bytes”

kubernetes_pod_network.json

  • “K8s - Pod TX Bytes/Second”
  • “K8s - Pod RX Bytes/Second "

kubernetes_system_container.json

  • “K8s - Kubelet Millicores”
  • “K8s - Kubelet Memory Bytes”

Memcached (memcached)

Required Telegraf plugin: Memcached input plugin

memcached.json

  • “Memcached - Current Connections”
  • “Memcached - Get Hits/Second”
  • “Memcached - Get Misses/Second”
  • “Memcached - Delete Hits/Second”
  • “Memcached - Delete Misses/Second”
  • “Memcached - Incr Hits/Second”
  • “Memcached - Incr Misses/Second”
  • “Memcached - Current Items”
  • “Memcached - Total Items”
  • “Memcached - Bytes Stored”
  • “Memcached - Bytes Written/Sec”
  • “Memcached - Evictions/10 Seconds”

mesos

Required Telegraf plugin: Mesos input plugin

mesos.json

  • “Mesos Active Slaves”
  • “Mesos Tasks Active”
  • “Mesos Tasks”
  • “Mesos Outstanding offers”
  • “Mesos Available/Used CPUs”
  • “Mesos Available/Used Memory”
  • “Mesos Master Uptime”

mongodb

Required Telegraf plugin: MongoDB input plugin

mongodb.json

  • “MongoDB - Read/Second”
  • “MongoDB - Writes/Second”
  • “MongoDB - Active Connections”
  • “MongoDB - Reds/Writes Waiting in Queue”
  • “MongoDB - Network Bytes/Second”

mysql

Required Telegraf plugin: MySQL input plugin

mysql.json

  • “MySQL - Reads/Second”
  • “MySQL - Writes/Second”
  • “MySQL - Connections/Second”
  • “MySQL - Connection Errors/Second”

nginx

Required Telegraf plugin: NGINX input plugin

nginx.json

  • “NGINX - Client Connections”
  • “NGINX - Client Errors”
  • “NGINX - Client Requests”
  • “NGINX - Active Client State”

nsq

Required Telegraf plugin: NSQ input plugin

nsq_channel.json

  • “NSQ - Channel Client Count”
  • “NSQ - Channel Messages Count”

nsq_server.json

  • “NSQ - Topic Count”
  • “NSQ - Server Count”

nsq_topic.json

  • “NSQ - Topic Messages”
  • “NSQ - Topic Messages on Disk”
  • “NSQ - Topic Ingress”
  • “NSQ topic egress”

phpfpm

Required Telegraf plugin: PHPfpm input plugin

phpfpm.json

  • “phpfpm - Accepted Connections”
  • “phpfpm - Processes”
  • “phpfpm - Slow Requests”
  • “phpfpm - Max Children Reached”

ping

Required Telegraf plugin: Ping input plugin

ping.json

  • “Ping - Packet Loss Percent”
  • “Ping - Response Times (ms)”

postgresql

Required Telegraf plugin: PostgreSQL input plugin

postgresql.json

  • “PostgreSQL - Rows”
  • “PostgreSQL - QPS”
  • “PostgreSQL - Buffers”
  • “PostgreSQL - Conflicts/Deadlocks”

rabbitmq

Required Telegraf plugin: RabbitMQ input plugin

rabbitmq.json

  • “RabbitMQ - Overview”
  • “RabbitMQ - Published/Delivered per second”
  • “RabbitMQ - Acked/Unacked per second”

redis

Required Telegraf plugin: Redis input plugin

redis.json

  • “Redis - Connected Clients”
  • “Redis - Blocked Clients”
  • “Redis - CPU”
  • “Redis - Memory”

riak

Required Telegraf plugin: Riak input plugin

riak.json

  • “Riak - Toal Memory Bytes”
  • “Riak - Object Byte Size”
  • “Riak - Number of Siblings/Minute”
  • “Riak - Latency (ms)”
  • “Riak - Reads and Writes/Minute”
  • “Riak - Active Connections”
  • “Riak - Read Repairs/Minute”

system

The system application includes metrics that require all of the listed plugins. If any of the following plugins aren’t enabled, the metrics associated with the plugins will not display data.

cpu

Required Telegraf plugin: CPU input plugin

cpu.json

  • “CPU Usage”

disk

disk.json

Required Telegraf plugin: Disk input plugin

  • “System - Disk used %”

diskio

Required Telegraf plugin: DiskIO input plugin

diskio.json

  • “System - Disk MB/s”

mem

Required Telegraf plugin: Mem input plugin

mem.json

  • “System - Memory Gigabytes Used”

net

Required Telegraf plugin: Net input plugin

net.json

  • “System - Network Mb/s”
  • “System - Network Error Rate”

netstat

Required Telegraf plugin: Netstat input plugin

netstat.json

  • “System - Open Sockets”
  • “System - Sockets Created/Second”

processes

Required Telegraf plugin: Processes input plugin

processes.json

  • “System - Total Processes”

procstat

Required Telegraf plugin: Procstat input plugin

procstat.json

  • “Processes - Resident Memory (MB)”
  • “Processes – CPU Usage %”

system

Required Telegraf plugin: Procstat input plugin

load.json

  • “System Load”

varnish

Required Telegraf plugin: Varnish

varnish.json

  • “Varnish - Cache Hits/Misses”

win_system

Required Telegraf plugin: Windows Performance Counters input plugin

win_cpu.json

  • “System - CPU Usage”

win_mem.json

  • “System - Available Bytes”

win_net.json

  • “System - TX Bytes/Second”
  • “RX Bytes/Second”

win_system.json

  • “System - Load”

Was this page helpful?

Thank you for your feedback!


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.

Read more

InfluxDB v3 enhancements and InfluxDB Clustered is now generally available

New capabilities, including faster query performance and management tooling advance the InfluxDB v3 product line. InfluxDB Clustered is now generally available.

InfluxDB v3 performance and features

The InfluxDB v3 product line has seen significant enhancements in query performance and has made new management tooling available. These enhancements include an operational dashboard to monitor the health of your InfluxDB cluster, single sign-on (SSO) support in InfluxDB Cloud Dedicated, and new management APIs for tokens and databases.

Learn about the new v3 enhancements


InfluxDB Clustered general availability

InfluxDB Clustered is now generally available and gives you the power of InfluxDB v3 in your self-managed stack.

Talk to us about InfluxDB Clustered