Postgresql opentelemtry app enhanced with newly contributed metrics (#5287)

* Postgresql opentelemtry app enhanced with newly contributed metrics

* Update postgresql-opentelemetry.md

* Update docs/integrations/databases/opentelemetry/postgresql-opentelemetry.md

* Update docs/integrations/databases/opentelemetry/postgresql-opentelemetry.md

* Apply suggestions from code review

Co-authored-by: Kim (Sumo Logic) <[email protected]>

---------

Co-authored-by: Jagadisha V <[email protected]>
Co-authored-by: Kim (Sumo Logic) <[email protected]>

Author: 3 people

docs/integrations/databases/opentelemetry/postgresql-opentelemetry.md

@@ -15,7 +15,7 @@ import TabItem from '@theme/TabItem';
 
 The Sumo Logic app for PostgreSQL includes predefined searches and dashboards that allow you to monitor logs and metrics for the database. The logs enable you to monitor database activity, user activity, incoming connections, query execution time, and errors. The metrics allow you to monitor database resource utilization and throughput performance.
 
-This app supports PostgreSQL version 9.6+.
+This app supports PostgreSQL version 13+.
 
 We use the OpenTelemetry collector for PostgreSQL metric collection and for collecting PostgreSQL logs.
 
@@ -41,7 +41,7 @@ Following are the tags that will be created as part of PostgreSQL app installati
 ### For metrics collection
 
 - This collection queries the PostgreSQL [statistics collector](https://www.postgresql.org/docs/9.6/monitoring-stats.html).
-- This receiver supports PostgreSQL version 9.6+.
+- This receiver supports PostgreSQL version 13+.
 - The monitoring user must be granted **SELECT** on the `pg_stat_database`.
 
 ### For logs collection
@@ -115,6 +115,7 @@ Below is the required input:
 - **Endpoint**. Enter the url of the server which needs to be monitored. Default endpoint is `localhost:5432`.
 - **UserName**. Enter the PostgreSQL username.
 - **Password**. Password for the user name which is being used for scrapping the PostgreSQL metrics.
+- **Collection Interval**. You can specify at what interval should the metrics be collected. Default is 5 minutes.
 
 You can add any custom fields which you want to tag along with the data ingested in Sumo. Click on the **Download YAML File** button to get the yaml file.
 
@@ -246,6 +247,7 @@ Use this dashboard to:
 - Determine the number of active databases and clusters.
 - Drill-down into database errors, failed logins and slow queries.
 - Determine if your database or queries need to be tuned based on comparing the number of slow queries.
+- Active deadlock value and tuple operations trends.
 
 <img src='https://sumologic-app-data-v2.s3.amazonaws.com/dashboards/Postgresql-OpenTelemetry/PostgreSQL-Overview.png' alt="Overview" />
 
@@ -267,8 +269,11 @@ The **PostgreSQL - Database Metrics** dashboard allows you to monitor the databa
 Use this dashboard to:
 
 - Understand the behavior and performance of your database clusters.
-- Monitor database size and disk usage.
+- Monitor the database size and disk usage.
 - Identify top 5 and least 5 frequently scanned indexes.
+- Monitor the row return and fetched ratio, block hits by database.
+- Identify the number of Locks and Deadlocks.
+- Identify the rows Update/Deleted/Inserted count trend.
 
 <img src='https://sumologic-app-data-v2.s3.amazonaws.com/dashboards/Postgresql-OpenTelemetry/PostgreSQL-Database-Metrics.png' alt="Database Metrics" />
 
@@ -281,6 +286,7 @@ Use this dashboard to view:
 - Head Only Tuple updated by schema.
 - Disk block reads and Disk usage by schema.
 - Buffer hits and rows inserted, updated and deleted by schema.
+- Live rows by schema.
 
 <img src='https://sumologic-app-data-v2.s3.amazonaws.com/dashboards/Postgresql-OpenTelemetry/PostgreSQL-Schema-Metrics.png' alt="Schema Metrics" />
 
@@ -333,6 +339,8 @@ Use this dashboard to:
 - Monitor PostgreSQL relation metrics (disk blocks, buffer hits, and hot updates) trends over time.
 - Monitor index scans and size to determine if executed queries are accessing them for a relation.
 - Track index utilization of existing indexes in a relation.
+- Monitor the PostgreSQL live and dead rows count trend.
+- Monitor the sequential scans and index scans by relation.
 
 <img src='https://sumologic-app-data-v2.s3.amazonaws.com/dashboards/Postgresql-OpenTelemetry/PostgreSQL-Relation-Metrics.png' alt="Relation Metrics" />
 
@@ -352,4 +360,5 @@ import CreateMonitors from '../../../reuse/apps/create-monitors.md';
 | `PostgreSQL - Instance Down Alert` | This alert gets triggered when the Postgres instance is down. | Count > = 1 | Count < 1 |
 | `PostgreSQL - SlowQueries Alert` | This alert gets triggered when we detect that the PostgreSQL instance is executing slow queries. | Count > 5 | Count < = 5 |
 | `Postgresql- Too Many Connections Alert` | PostgreSQL instance has too many connections. | Count > = 100 | Count < 100 |
-| `Postgresql - Too Many Locks Acquired Alert` | This alert gets triggered when we detect that there are too many locks acquired on the database. If this alert happens frequently, you may need to increase the postgres setting `max_locks_per_transaction`. | Count > = 100 | Count < 100 |
+| `PostgreSQL - Too Many Locks Acquired Alert` | This alert is triggered when there are too many locks acquired on the database. Increase the postgres setting `max_locks_per_transaction`, if this alert occurs frequently. | Count > = 100 | Count < 100 |
+| `PostgreSQL - High Rate Deadlock` | This alert is triggered when deadlocks in a Postgres instance are detected. | Count > = 1 | Count < 1 |