All Projects → percona → qan-api

percona / qan-api

Licence: AGPL-3.0 license
Query Analytics API for PMM 1.x

Programming Languages

go
31211 projects - #10 most used programming language
perl
6916 projects

Labels

Projects that are alternatives of or similar to qan-api

qan-app
Query Analytics Web App for PMM
Stars: ✭ 12 (-25%)
Mutual labels:  pmm, pmm1
mysqld exporter
Exporter for MySQL server metrics
Stars: ✭ 54 (+237.5%)
Mutual labels:  pmm
awesome-pmm
A curated list of awesome Percona Monitoring and Management (PMM) free and opensource software, libraries and resources.
Stars: ✭ 26 (+62.5%)
Mutual labels:  pmm
Grafana Dashboards
PMM dashboards for database monitoring
Stars: ✭ 2,084 (+12925%)
Mutual labels:  pmm
pmm-agent
pmm-agent for PMM 2.x.
Stars: ✭ 33 (+106.25%)
Mutual labels:  pmm

Percona Query Analytics API

Travis CI Build Status GoDoc Report Card CLA assistant

Percona Query Analytics (QAN) API is part of Percona Monitoring and Management (PMM). See the PMM docs for more information.

##Building

In the empty dir run:

export GOPATH=$(pwd)
git clone http://github.com/percona/qan-api ./src/github.com/percona/qan-api
go build -o ./revel ./src/github.com/percona/qan-api/vendor/github.com/revel/cmd/revel
ln -s $(pwd)/src/github.com/percona/qan-api/vendor/github.com/revel src/github.com/revel
./revel build github.com/percona/qan-api <destination dir> prod

Submitting Bug Reports

If you find a bug in Percona QAN API 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.
Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].