music on atproto
plyr.fm
1---
2description: Investigate Logfire spans and traces to answer questions about application behavior
3argument-hint: [your question about what happened]
4---
5
6First read the Logfire documentation: @docs/tools/logfire.md
7
8Investigate: $ARGUMENTS
9
10Query the `records` table using SQL patterns from the docs. Key points:
11- Search by `message` for logfire.info() events, `span_name` for spans
12- Use `trace_id` to follow a full user action flow
13- Check `otel_status_message` for errors (not exception.message)
14- Filter by `start_timestamp` for time ranges
15- Extract metadata from `attributes` JSONB field