Merge branch 'master' into prometheus-master

README.md

@@ -1,4 +1,4 @@
-# MySQL Server Exporter [![Build Status](https://travis-ci.org/percona/mysqld_exporter.svg)][travis]
+# Percona MySQL Server Exporter [![Build Status](https://travis-ci.org/percona/mysqld_exporter.svg)][travis]
 
 [![Go Report Card](https://goreportcard.com/badge/github.com/percona/mysqld_exporter)](https://goreportcard.com/report/github.com/percona/mysqld_exporter)
 
@@ -113,3 +113,28 @@ There are some sample rules available in [example.rules](example.rules)
 [hub]: https://hub.docker.com/r/prom/mysqld-exporter/
 [travis]: https://travis-ci.org/percona/mysqld_exporter
 [quay]: https://quay.io/repository/prometheus/mysqld-exporter
+
+## Visualize
+
+There is a Grafana dashboard for MySQL available as a part of [PMM](https://www.percona.com/doc/percona-monitoring-and-management/index.html) project, you can see the demo [here](https://pmmdemo.percona.com/graph/dashboard/db/mysql-overview).
+
+## Submit Bug Report
+If you find a bug in Percona MySQL Exporter or one of the related projects, you should submit a report to that project's [JIRA](https://jira.percona.com) 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.](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=11709)
+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.
+