Skip to content

Latest commit

 

History

History
59 lines (46 loc) · 2.51 KB

README.md

File metadata and controls

59 lines (46 loc) · 2.51 KB

Grafana dashboards for efficient database monitoring

The list of featured dashboards:

  • Disk Performance
  • Disk Space
  • MongoDB Cluster Summary
  • MongoDB Overview
  • MongoDB ReplSet
  • MongoDB RocksDB
  • MongoDB WiredTiger
  • MongoDB MMAPv1
  • MongoDB InMemory
  • Node Overview
  • MySQL InnoDB Metrics
  • MySQL InnoDB Metrics Advanced
  • MySQL InnoDB Compression
  • MySQL MyISAM/Aria Metrics
  • MySQL Overview
  • MySQL Performance Schema
  • MySQL Query Response Time
  • MySQL Replication
  • MySQL Table Statistics
  • MySQL User Statistics
  • MySQL Command Handler Counters Compare
  • PXC/Galera Cluster Overview
  • PXC/Galera Graphs
  • VictoriaMetrics
  • ProxySQL Overview
  • Summary Dashboard
  • System Overview
  • Trends Dashboard

These dashboards are part of Percona Monitoring and Management.

See a live demonstration at https://pmmdemo.percona.com.

We welcome contributions to this repository! Detailed information in 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 issue tracker.

Your first step should be to search 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. 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.
  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..

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.