Percona Monitoring and Management 2.x
See the PMM 2.x docs for more information.
Submitting Bug Reports
If you find a bug in Percona Monitoring and Management or one of the related projects, you should submit a 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:
- Sign in to Percona JIRA. You will need to create an account if you do not have one.
- Go to the Create Issue screen and select the relevant project.
- 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.
APIs
See stable API definitions there, and all API definitions (including technical preview, development and testing APIs) there.
Repositories
APIs
PMM Server
- percona/pmm-managed
- percona-platform/dbaas-controller
- percona/qan-api2
- percona/pmm-update
- percona/percona-toolkit
- percona/grafana-dashboards
- percona-platform/grafana
PMM Client
- percona/pmm-agent
- percona/pmm-admin
- percona/node_exporter
- percona/mysqld_exporter
- percona/mongodb_exporter
- percona/postgres_exporter
- percona/proxysql_exporter
- percona/rds_exporter
- percona/azure_exporter
- Percona-Lab/clickhouse_exporter
Building and Packaging
- percona/pmm-server
- Percona-Lab/pmm-submodules
- Percona-Lab/jenkins-pipelines
- Percona-Lab/percona-images
