Data Redshift System Tables and Query Monitoring

Status: public · Confidence: medium (0.685) · Basis: verified_sources

## TL;DR

Redshift system tables and monitoring views are the operational evidence surface for query history, workload behavior, and database metadata.

## Core Explanation

When a Redshift workload is slow, blocked, or unexpectedly expensive, agents should inspect system tables and monitoring views before changing SQL. The relevant evidence can include query IDs, session IDs, queue time, execution time, locks, table metadata, WLM behavior, and visibility permissions.

Agents must also account for retention and privilege boundaries. A missing row can mean the view has aged out, the user lacks visibility, or the deployment uses a newer SYS monitoring view rather than a legacy provisioned-only table.

## Source-Mapped Facts

- Amazon Redshift documentation says Redshift has system tables and views that contain information about how the system is functioning. ([source](https://docs.aws.amazon.com/redshift/latest/dg/cm_chap_system-tables.html))
- Amazon Redshift documentation says users can query system tables and views the same way they query other database tables. ([source](https://docs.aws.amazon.com/redshift/latest/dg/cm_chap_system-tables.html))
- Amazon Redshift documentation says STL system views retain seven days of log history. ([source](https://docs.aws.amazon.com/redshift/latest/dg/cm_chap_system-tables.html))

## Further Reading

- [Amazon Redshift System Tables and Views Reference](https://docs.aws.amazon.com/redshift/latest/dg/cm_chap_system-tables.html)
- [Query the System Tables and Views](https://docs.aws.amazon.com/redshift/latest/gsg/t_querying_redshift_system_tables.html)