Skip to content
Branch: master
Clone or download
Latest commit 00c1489 Mar 16, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
build
pmm PMM-3479 Error message for different versions. (#196) Feb 12, 2019
scripts
tests/fakeapi PMM-2704: Stop travis PostgreSQL and fix tests. Jul 31, 2018
vendor
.gitignore PMM-1443 Hide user credentials in error message (#172) Oct 2, 2018
.travis.yml PMM-2715: Update dep. Oct 2, 2018
CHANGELOG.md Remove changelog Jul 25, 2017
CONTRIBUTING.md Update CONTRIBUTING.md Feb 22, 2018
Gopkg.lock PMM-3479 Error message for different versions. (#196) Feb 12, 2019
Gopkg.toml
LICENSE Rename percona-metrics to percona-prom-pm. Update build script to mak… Mar 31, 2016
Makefile
README.md Update README.md Mar 15, 2019
VERSION PMM-3464 update version to 1.17.1 (#194) Jan 22, 2019
docker-compose.yml
pmm-admin.go
pmm-admin_test.go PMM-3464 update version to 1.17.1 (#194) Jan 22, 2019

README.md

Percona Monitoring and Management (PMM) Client

Build Status Go Report Card CLA assistant

See the PMM docs for more information.

Submitting Bug Reports

If you find a bug in Percona PMM Client 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:

  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.
You can’t perform that action at this time.