get_traces
Analyze individual trace samples in JSON format to identify bottlenecks and debug performance issues in specific slow requests. Filter by environment, service, transaction name, response time, and date range.
Instructions
Analyze individual trace samples in JSON format for detailed bottleneck identification and performance debugging. Use for investigating specific slow requests, not system-wide statistics (use get_performance_metrics for aggregate data).
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| env | No | Environment name (e.g., "production", "staging") | |
| s | No | Service name (e.g., "web", "api", "worker") | |
| transaction_name | No | Filter by specific transaction/endpoint name | |
| has_callgraph | No | Only return traces with detailed callgraph data | |
| search | No | Word-based search on transaction_name, host, and URL text tokens. This is no fulltext search. | |
| min_date | No | Minimal date for traces in YYYY-MM-DD HH:MM format (e.g., "2024-01-15 14:30"). Convert natural language like "1 hour ago" to this format. Requires max_date. | |
| max_date | No | Maximal date for traces in YYYY-MM-DD HH:MM format (e.g., "2024-01-15 16:30"). Convert natural language like "now" to this format. Requires min_date. | |
| min_response_time_ms | No | Minimum response time in milliseconds for filtering slow traces | |
| max_response_time_ms | No | Maximum response time in milliseconds for filtering traces | |
| sort_by | No | Field to sort traces by | response_time |
| sort_order | No | Sort order (DESC = slowest/newest first) | DESC |