Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/percona/grafana-dashboards
PMM dashboards for database monitoring
https://github.com/percona/grafana-dashboards
grafana-dashboard hacktoberfest mongodb-monitoring mysql pmm
Last synced: 4 days ago
JSON representation
PMM dashboards for database monitoring
- Host: GitHub
- URL: https://github.com/percona/grafana-dashboards
- Owner: percona
- License: agpl-3.0
- Created: 2016-01-22T07:14:23.000Z (almost 9 years ago)
- Default Branch: main
- Last Pushed: 2024-10-24T10:53:50.000Z (about 2 months ago)
- Last Synced: 2024-10-29T17:58:57.205Z (about 2 months ago)
- Topics: grafana-dashboard, hacktoberfest, mongodb-monitoring, mysql, pmm
- Language: JavaScript
- Homepage:
- Size: 209 MB
- Stars: 2,701
- Watchers: 110
- Forks: 1,546
- Open Issues: 35
-
Metadata Files:
- Readme: README.md
- Contributing: CONTRIBUTING.md
- License: LICENSE
- Codeowners: .github/CODEOWNERS
Awesome Lists containing this project
- awesome - percona/grafana-dashboards - PMM dashboards for database monitoring (JavaScript)
- awesome-pmm - Grafana Dashboards by Percona - This is a set of Grafana dashboards for database and system monitoring using Prometheus datasource. (Dashboards / Resources)
README
## Grafana dashboards for efficient database monitoring
The list of featured dashboards:
- Advanced Data Exploration
- CPU Utilization Details
- Disk Details
- HAProxy Instance Summary
- Home Dashboard
- Memory Details
- MongoDB Cluster Summary
- MongoDB InMemory Details
- MongoDB Instance Summary
- MongoDB Instances Compare
- MongoDB Instances Overview
- MongoDB MMAPv1 Details
- MongoDB ReplSet Summary
- MongoDB WiredTiger Details
- MySQL Amazon Aurora Details
- MySQL Command Handler Counters Compare
- MySQL Group Replication Summary
- MySQL InnoDB Compression Details
- MySQL InnoDB Details
- MySQL Instance Summary
- MySQL Instances Compare
- MySQL Instances Overview
- MySQL MyISAM Aria Details
- MySQL MyRocks Details
- MySQL Performance Schema Details
- MySQL Query Response Time Details
- MySQL Replication Summary
- MySQL Table Details
- MySQL TokuDB Details
- MySQL User Details
- MySQL Wait Event Analyses Details
- NUMA Details
- Network Details
- Node Summary
- Node Temperature Details
- Nodes Compare
- Nodes Overview
- PXC Galera Cluster Summary
- PXC Galera Node Summary
- PXC Galera Nodes Compare
- PostgreSQL Instance Summary
- PostgreSQL Instances Compare
- PostgreSQL Instances Overview
- Processes Details
- Prometheus Exporter Status
- Prometheus Exporters Overview
- ProxySQL Instance Summary
- VictoriaMetrics
- VictoriaMetrics Agents OverviewThese dashboards are part of [Percona Monitoring and Management](https://www.percona.com/doc/percona-monitoring-and-management/2.x/index.html).
See a live demonstration at .
## Reusing dashboards outside of PMM
Dashboards can be converted to be used on a dedicated prometheus instance.
Example:
- misc/convert-dash-from-PMM.py dashboards/Disk_Details.json
## AWS Setup page
Plase see the relevant [README.md](./setup-page/README.md).
## Contributing
We welcome contributions to this repository! Detailed information in [CONTRIBUTING.md](CONTRIBUTING.md)
## Submitting Bug Reports
If you find a bug in Percona Grafana Dashboards or one of the related projects, you can submit a bug report to that project's [JIRA](https://jira.percona.com) issue tracker.
Your first step should be [to search](https://jira.percona.com/issues/?jql=project%20%3D%20PMM%20AND%20component%20%3D%20%22Grafana%20Dashboards%22) the existing set of open tickets for a similar report. If you find that someone else has already reported your problem, then you can upvote that report to increase its visibility.
If there is no existing report, submit a report following these steps:
1. [Sign in to Percona JIRA.](https://jira.percona.com/login.jsp) You will need to create an account if you do not have one.
2. [Go to the Create Issue screen and select the relevant project.](https://jira.percona.com/secure/CreateIssueDetails!init.jspa?pid=11600&issuetype=1&priority=3&components=11307)
3. Fill in the fields of Summary, Description, Steps To Reproduce, and Affects Version to the best you can. If the bug corresponds to a crash, attach the stack trace from the logs.An excellent resource is [Elika Etemad's article on filing good bug reports.](http://fantasai.inkedblade.net/style/talks/filing-good-bugs/).
As a general rule of thumb, please try to create bug reports that are:
- _Reproducible._ Include steps to reproduce the problem.
- _Specific._ Include as much detail as possible: which version, what environment, etc.
- _Unique._ Do not duplicate existing tickets.
- _Scoped to a Single Bug._ One bug per report.