How do I troubleshoot a broken data pipeline in Redshift when the error logs just look like a bunch of random numbers?
Download run
Fan-out diagram
The searches the AI actually ran for this prompt.
SEED QUERY
How do I troubleshoot a broken data pipeline in Redshift when the error logs just look like a bunch of random numbers?
1 real search · 1 real-search pass
site:docs.aws.amazon.com/redshift/latest/dg Redshift troubleshooting query errors STL_ERROR STL_LOAD_ERRORS SYS_QUERY_HISTORY SYS_LOAD_ERROR_DETAIL system viewsGoogle ↗
OBSERVED
Badge and edge weight = share of passes that produced the query. Hover a query for its intent and routing format.
Query classes
Google's semantic query class for every sub-query: what kind of answer each search is after, simulated vs real.
Classifying 1 queries…
Searches and sources
ChatGPT1 real searches · gpt-6
site:docs.aws.amazon.com/redshift/latest/dg Redshift troubleshooting query errors STL_ERROR STL_LOAD_ERRORS SYS_QUERY_HISTORY SYS_LOAD_ERROR_DETAIL system views Google ↗
- STL_ERROR · docs.aws.amazon.com
- STL_LOAD_ERRORS · docs.aws.amazon.com
- STL_LOADERROR_DETAIL · docs.aws.amazon.com
- System tables and views reference · docs.aws.amazon.com
- Load error reference · docs.aws.amazon.com
- STL views for logging · docs.aws.amazon.com