external/pg_stat_monitor
1
0
Fork 0
mirror of https://github.com/percona/pg_stat_monitor.git synced 2026-02-04 14:06:20 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge branch 'master' into PG-215-Doc-User-guide-updates-master

Browse Source
This commit is contained in:
Anastasia Alexandrova
2021-11-05 14:46:39 +02:00
committed by GitHub
parent d9c281a408 22ebe35cb1
commit f186a28a2d
32 changed files with 1904 additions and 653 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
docs/USER_GUIDE.md
View File

@@ -30,6 +30,7 @@ The following are the key features of pg_stat_monitor:
* [Integration with Percona Monitoring and Management (PMM) tool](#integration-with-pmm),
* [Histograms](#histogram) - visual representation of query performance.
### Time buckets
Instead of supplying one set of ever-increasing counts, `pg_stat_monitor` computes stats for a configured number of time intervals; time buckets. This allows for much better data accuracy, especially in the case of high-resolution or unreliable networks.
@@ -38,8 +39,10 @@ Instead of supplying one set of ever-increasing counts, `pg_stat_monitor` comput
`pg_stat_monitor` collects the information about what tables were accessed by a statement. This allows you to identify all queries which access a given table easily.
### Query and client information
`pg_stat_monitor` provides additional metrics for detailed analysis of query performance from various perspectives, including client connection details like user name, application name, IP address to name a few relevant columns.
With this information, `pg_stat_monitor` enables users to track a query to the originating application. More details about the application or query may be incorporated in the SQL query in a [Google’s Sqlcommenter](https://google.github.io/sqlcommenter/) format.
@@ -47,6 +50,7 @@ With this information, `pg_stat_monitor` enables users to track a query to the o
Understanding query execution time stats helps you identify what affects query performance and take measures to optimize it. `pg_stat_monitor` collects the total, min, max and average (mean) time it took to execute a particular query and provides this data in separate columns. See the [Query timing information](#usage-examples-query-timing-information) example for the sample output.
### Query execution plan information
Every query has a plan that was constructed for its executing. Collecting the query plan information as well as monitoring query plan timing helps you understand how you can modify the query to optimize its execution. It also helps make communication about the query clearer when discussing query performance with other DBAs and application developers.
@@ -180,6 +184,7 @@ The following table shows setup options for each configuration parameter and whe
#### Parameters description:
##### pg_stat_monitor.pgsm_max
Values: