Welcome to the SigNoz Dashboards repository! This repository hosts a collection of pre-built SigNoz dashboard templates in JSON format, designed to monitor popular services like MySQL, MongoDB, APM, JVM, and more. These dashboards allow you to quickly set up visualizations for your application's metrics and performance.
- Overview
- Available Dashboards
- Request New Dashboard Template
- Adding New Dashboards
- Dashboard Naming Convention
- Contributing
- License
SigNoz is an open-source observability platform that helps you monitor and analyze the performance of your services in real-time. This repository contains ready-to-use dashboard templates in JSON format that can be imported into SigNoz to visualize key metrics and performance indicators for various services.
Each dashboard is built for specific services and data sources like OpenTelemetry (OTLP) and Prometheus. Users can import and modify these dashboards or create new ones based on their needs.
Below is a list of available dashboard templates in this repository:
- Hostmetrics Dashboard: Monitors general host metrics, including CPU, memory, and disk usage.
- Kubernetes Infra Dashboard: Visualizes metrics related to Kubernetes infrastructure.
- Key Operations Dashboard: Tracks key operations within an application, focusing on performance and reliability.
- Apache Web Server Dashboard: Monitors Apache web server metrics like request rates and active connections.
- APM Dashboard: Visualizes application performance metrics, including latency, throughput, and error rates.
- Docker Container Metrics Dashboard: Tracks metrics related to Docker containers, such as CPU and memory usage.
- CouchDB Dashboard: Monitors CouchDB-specific metrics, such as document read/write rates.
- ECS Infrastructure Metrics Dashboard: Visualizes metrics for Amazon ECS infrastructure.
- Flask Monitoring Dashboard: Monitors performance metrics for Flask applications.
- HAProxy Dashboard: Monitors HAProxy metrics such as request rates and active sessions.
- Jenkins Dashboard: Tracks Jenkins metrics, including job success rates and queue times.
- JMX Dashboard: Monitors Java Management Extensions (JMX) metrics.
- JVM Dashboard: Tracks JVM metrics, including heap usage, garbage collection, and thread counts.
- Memcached Dashboard: Visualizes Memcached-specific metrics, such as cache hit/miss rates.
- MongoDB Dashboard: Monitors MongoDB operations, memory usage, and performance metrics.
- MySQL Dashboard: Tracks MySQL metrics, including queries per second and connection errors.
- Nginx Dashboard: Monitors Nginx web server metrics, including request rates and active connections.
- Nomad Dashboard: Visualizes metrics for HashiCorp Nomad.
- PostgreSQL Dashboard: Monitors PostgreSQL performance metrics.
- RabbitMQ Dashboard: Tracks RabbitMQ metrics like queue sizes and message throughput.
- Temporal.io Dashboard: Monitors Temporal.io workflow metrics.
- LLM Observability Dashboard: Visualizes metrics for monitoring large language models.
- SigNoz Ingestion Analysis: Visualizes the volume the metrics, traces and logs ingested into SigNoz. Useful for cost optimization.
- KEDA Dashboard: Monitors metrics for KEDA, a Kubernetes-based event-driven autoscaling component.
More services will be added in the future!
Before requesting a new dashboard, please check if a similar request has already been made by searching through the open issues here: Existing Dashboard Requests.
If no similar request exists, you can create a new issue using the following link: Request a New Dashboard.
Please make sure to provide the necessary details when submitting your request to ensure that it can be addressed appropriately.
To add a new dashboard template for any service, follow the contribution guidelines in the Contributing Guide. In brief:
- Create a dashboard JSON file following the Dashboard Naming Convention.
- Add a README file explaining the dashboard, the metrics ingested, and the configurations needed.
- Include screenshots of the dashboard in the
assets/directory. - Submit a pull request for review.
Dashboard JSON files should follow this naming convention:
name-of-dashboard-source-version.json
- name-of-dashboard: The name of the service being monitored (e.g.,
mysql-dashboard). - source: Data source, such as
otlporprometheus. - version: Start with
v1for the initial version and increment with future versions (e.g.,v2,v3).
Example: mysql-dashboard-otlp-v1.json
We welcome contributions! If you want to contribute new dashboard templates or enhance existing ones, please refer to our Contributing Guide for details on how to get started. Be sure to follow the naming conventions and guidelines outlined in the guide.
Your contributions will help the SigNoz community grow and make monitoring easier for everyone.
This repository is licensed under the Apache 2.0 License. By contributing to this repository, you agree that your contributions will also be licensed under the same.
