Open-source web UI for visualizing monitoring data and creating alerts in the TICK stack.
Chronograf is the web-based visualization and alerting component of the TICK stack, an open-source monitoring platform from InfluxData. It provides a user interface to explore metrics collected by Telegraf, stored in InfluxDB, and processed by Kapacitor, enabling teams to create dashboards and configure alerts without deep database expertise.
DevOps engineers, SREs, and developers who use the TICK stack for infrastructure and application monitoring and need a centralized UI for data exploration and alert management.
As the official UI for the TICK stack, it offers deep integration with InfluxDB and Kapacitor, pre-built dashboards for common services, and a streamlined alert creation workflow, reducing the time to set up and maintain a monitoring system.
Open source monitoring and visualization UI for the TICK stack
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Offers an extensive library of dashboards for common Telegraf input plugins like Docker, Kubernetes, and PostgreSQL, significantly reducing initial setup time for monitoring common services.
Provides a seamless UI for creating and managing Kapacitor alerts with support for multiple destinations including Slack, PagerDuty, and email, streamlining the alert configuration workflow.
Includes capabilities to manage InfluxDB users, roles, permissions, and monitor active queries directly from the web interface, simplifying database administration tasks.
Features a Data Explorer with an InfluxQL query editor and template variables, allowing users to create personalized visualizations without deep database expertise.
The Host List feature requires running specific Telegraf plugins (CPU and system), as noted in the Known Issues section, which limits flexibility in data collection configurations.
Version 1.8 introduced a breaking change in the dashboards API where IDs are returned as strings instead of integers, potentially disrupting existing client integrations without database migrations.
Primarily designed for the TICK stack, it lacks native support for other time-series databases or query languages like Flux, making it less suitable for mixed monitoring environments.