---
title: "Verify telemetry status | Database Observability documentation"
description: "Use the Configuration page to validate that Database Observability is correctly receiving telemetry from your MySQL, PostgreSQL, and SQL Server databases."
---

> For a curated documentation index, see [llms.txt](/llms.txt). For the complete documentation index, see [llms-full.txt](/llms-full.txt).

# Verify telemetry status

Use the Configuration page in Database Observability to validate that your databases are correctly configured and sending telemetry to Grafana Cloud. The Telemetry status dashboard runs automated checks against each database instance and highlights any configuration issues that need attention.

## Before you begin

Complete setup for at least one database:

- [Set up MySQL](https://grafana.com/docs/grafana-cloud/monitor-applications/database-observability/set-up/mysql/)
- [Set up PostgreSQL](https://grafana.com/docs/grafana-cloud/monitor-applications/database-observability/set-up/postgres/)
- [Set up SQL Server](https://grafana.com/docs/grafana-cloud/monitor-applications/database-observability/set-up/sqlserver/)

## Access the Configuration page

To view the telemetry status for your database instances:

1. In Grafana Cloud, navigate to **Database Observability**.
2. Click **Configuration** in the navigation menu.
3. Select **Telemetry status**.
4. Select one or more instances from the **Instance** dropdown.

The page automatically detects the database engine type (MySQL, PostgreSQL, or SQL Server) and displays the relevant status checks for each selected instance.

## Understand status checks

Each instance displays a grid of status check tiles. Each tile represents a specific configuration requirement:

Expand table

| Status          | Meaning                                                 |
|-----------------|---------------------------------------------------------|
| Green checkmark | Check passed. The configuration is correct.             |
| Red warning     | Check failed. Action required to fix the configuration. |
| Blue “Checking” | Check in progress. Wait for the query to complete.      |

Some checks only apply to specific Grafana Alloy versions and don’t appear on instances running an incompatible version. After upgrading Alloy, the set of visible checks may change.

A badge appears next to each instance name showing the number of failed checks, for example, “2 checks require action”.

### MySQL status checks

Database Observability validates the following for MySQL instances:

Expand table

| Check                                            | What it validates                                                                                                                   | Feature impact                                                                                                                                                                                      |
|--------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Database version compatible                      | MySQL version 8.0 or later is running.                                                                                              | All features require a compatible database version.                                                                                                                                                 |
| Grafana Alloy version compatible                 | Grafana Alloy version 1.17.0 or later is collecting telemetry from the database.                                                    | All features require a compatible Alloy version.                                                                                                                                                    |
| Performance Schema enabled                       | The `performance_schema` system variable is set to `ON`.                                                                            | Queries overview, query performance, query samples, wait events, and explain plans are unavailable.                                                                                                 |
| Performance Schema populated                     | Queries are being tracked in Performance Schema tables.                                                                             | Queries overview, query performance, query samples, wait events, and explain plans are unavailable.                                                                                                 |
| Setup consumers enabled                          | The `events_statements_cpu`, `events_waits_current`, and `events_waits_history` consumers are active.                               | Query samples and wait event breakdowns are unavailable.                                                                                                                                            |
| Digest length variables set correctly            | Variables like `performance_schema_max_digest_length` are set to at least 4096 for complete query capture.                          | Query text may appear truncated. Queries with similar prefixes may be incorrectly grouped, causing metrics, samples, wait events, and explain plans to combine data from different queries.         |
| Privileges granted                               | The monitoring user has required permissions on `performance_schema` and `information_schema`.                                      | All Performance Schema and schema metadata features are unavailable.                                                                                                                                |
| Metric labels set                                | Required labels (`job`, `instance`, `server_id`, `provider_account`, `provider_region`, `provider_name`) are present and not empty. | Instance detection, query drilldowns, and per-instance data isolation fail. Data from different instances may be incorrectly combined.                                                              |
| Events statements collector configured correctly | Performance Schema metrics do not contain a `digest_text` label (`perf_schema.eventsstatements` collector uses `text_limit = 0`).   | Excessive metric cardinality may increase costs and degrade query performance in Grafana Cloud.                                                                                                     |
| Logs available and correctly labeled             | Logs are present with the same `job`, `instance`, and `server_id` labels as the metrics for the same database.                      | A relabeling mismatch between the metrics and logs pipelines (or missing logs entirely) means query samples, wait events, and other log-derived data won’t be associated with the correct instance. |

### PostgreSQL status checks

Database Observability validates the following for PostgreSQL instances:

Expand table

| Check                                     | What it validates                                                                                                                   | Feature impact                                                                                                                                                                                      |
|-------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Database version compatible               | PostgreSQL version 14 or later is running.                                                                                          | All features require a compatible database version.                                                                                                                                                 |
| Grafana Alloy version compatible          | Grafana Alloy version 1.17.0 or later is collecting telemetry from the database.                                                    | All features require a compatible Alloy version.                                                                                                                                                    |
| `pg_stat_statements` extension enabled    | The `pg_stat_statements` extension is installed and enabled.                                                                        | Queries overview, query performance, query text, explain plans, query samples, and wait events are unavailable.                                                                                     |
| `pg_stat_statements` view populated       | Queries are being tracked in the `pg_stat_statements` view for any database/user that is not excluded by configuration.             | Queries overview, query performance, query text, explain plans, query samples, and wait events are unavailable.                                                                                     |
| `compute_query_id` enabled                | The PostgreSQL `compute_query_id` setting is not `off` so `pg_stat_statements` can group statements by their query identifier.      | Without query IDs calculation, `pg_stat_statements` cannot group statements, breaking query grouping and performance metrics tracking.                                                              |
| `track_activity_query_size` set correctly | The `track_activity_query_size` parameter is set to at least 4096 for complete query capture.                                       | Query text may appear truncated. Explain plans are skipped for truncated queries, and table associations may be incomplete.                                                                         |
| Privileges granted                        | The monitoring user has required permissions on `pg_stat_statements` and `pg_stat_activity`.                                        | All `pg_stat_statements` and schema metadata features are unavailable.                                                                                                                              |
| Metric labels set                         | Required labels (`job`, `instance`, `server_id`, `provider_account`, `provider_region`, `provider_name`) are present and not empty. | Instance detection, query drilldowns, and per-instance data isolation fail. Data from different instances may be incorrectly combined.                                                              |
| Logs available and correctly labeled      | Logs are present with the same `job`, `instance`, and `server_id` labels as the metrics for the same database.                      | A relabeling mismatch between the metrics and logs pipelines (or missing logs entirely) means query samples, wait events, and other log-derived data won’t be associated with the correct instance. |

### SQL Server status checks

Database Observability validates the following for SQL Server instances:

Expand table

| Check                                | What it validates                                                                                                                                                                                                                            | Feature impact                                                                                                                                                                                                         |
|--------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Grafana Alloy version compatible     | Grafana Alloy version 1.22.0 or later is collecting telemetry from the database.                                                                                                                                                             | All features require a compatible Alloy version.                                                                                                                                                                       |
| Privileges granted                   | The monitoring login has `VIEW DEFINITION` and `VIEW DATABASE STATE` (or `VIEW DATABASE PERFORMANCE STATE`) on every accessible database, plus `VIEW SERVER STATE` (or `VIEW SERVER PERFORMANCE STATE`) on non-Azure SQL Database instances. | Schema metadata, Query Store metrics, query text, explain plans, server metrics, and query samples are unavailable.                                                                                                    |
| Query Store enabled                  | Query Store is enabled in `READ_WRITE` mode on every accessible database.                                                                                                                                                                    | Queries overview, query performance, query text, explain plans, and query samples are unavailable for databases where Query Store isn’t enabled.                                                                       |
| Query Store populated                | Queries are being tracked in `sys.query_store_runtime_stats` on at least one accessible database.                                                                                                                                            | Queries overview, query performance, query text, explain plans, and query samples are unavailable.                                                                                                                     |
| Metric labels set                    | Required labels (`job`, `instance`, `server_id`, `provider_account`, `provider_region`, `provider_name`) are present and not empty.                                                                                                          | Instance detection, query drilldowns, and per-instance data isolation fail. Data from different instances may be incorrectly combined.                                                                                 |
| Logs available and correctly labeled | Logs are present with the same `job`, `instance`, and `server_id` labels as the metrics for the same database.                                                                                                                               | A relabeling mismatch between the metrics and logs pipelines (or missing logs entirely) means query text, explain plans, query samples, wait events, and schema details won’t be associated with the correct instance. |
| Statement metrics present            | Query execution metrics (`database_observability_query_executions_total`) from Query Store are present with the same `instance` and `server_id` labels as the database.                                                                      | Query rate, latency, errors, and Top queries are unavailable.                                                                                                                                                          |

## Resolve failed checks

Click a failed status check tile to open the linked troubleshooting documentation. Each check links to specific guidance for resolving that configuration issue.

For comprehensive troubleshooting steps, refer to:

- [Troubleshoot MySQL](https://grafana.com/docs/grafana-cloud/monitor-applications/database-observability/troubleshoot/mysql/)
- [Troubleshoot PostgreSQL](https://grafana.com/docs/grafana-cloud/monitor-applications/database-observability/troubleshoot/postgres/)
- [Troubleshoot SQL Server](https://grafana.com/docs/grafana-cloud/monitor-applications/database-observability/troubleshoot/sql_server/)

## Troubleshoot the Configuration page

If instances don’t appear in the dropdown or checks remain in the “Checking” state, refer to the troubleshooting guides for your database and Alloy:

- [Troubleshoot Alloy](https://grafana.com/docs/grafana-cloud/monitor-applications/database-observability/troubleshoot/alloy/)
- [Troubleshoot MySQL](https://grafana.com/docs/grafana-cloud/monitor-applications/database-observability/troubleshoot/mysql/)
- [Troubleshoot PostgreSQL](https://grafana.com/docs/grafana-cloud/monitor-applications/database-observability/troubleshoot/postgres/)
- [Troubleshoot SQL Server](https://grafana.com/docs/grafana-cloud/monitor-applications/database-observability/troubleshoot/sql_server/)

## Next steps

- [Monitor query performance](https://grafana.com/docs/grafana-cloud/monitor-applications/database-observability/monitor/)
- [Tune Alloy collection](https://grafana.com/docs/grafana-cloud/monitor-applications/database-observability/configure/tune-alloy-collection/)
- [Monitor multiple databases](https://grafana.com/docs/grafana-cloud/monitor-applications/database-observability/configure/monitor-multiple-databases/)
