errorcore
IO Recording

Database Queries

Database query capture is most useful when the failure is a consequence of data shape or timing rather than a database exception by itself.

database query timeline
14ms  SELECT * FROM invoices WHERE status = "overdue"
19ms  Error thrown in billing service

Prefer normalized query summaries over raw, high-cardinality SQL text when the full statement is not needed. The goal is readable incident context, not query log duplication.

Outbound HTTP

Record upstream requests so application failures can be read against the network calls that preceded them.

DNS & Net

Include lookup and low-level network events when the failure path depends on connectivity rather than application code alone.

On this page

Database Queries