run_query
Execute Honeycomb queries to analyze and summarize observability data. Specify operations like COUNT, SUM, or P95, and group results using breakdowns. Follow specific rules to avoid errors, such as excluding the 'column' field for COUNT operations.
Instructions
Executes a Honeycomb query, returning results with statistical summaries.
CRITICAL RULE: For COUNT operations, NEVER include a "column" field in your calculation, even as null or undefined. Example: Use {"op": "COUNT"} NOT {"op": "COUNT", "column": "anything"}.
Additional Rules:
All parameters must be at the TOP LEVEL (not nested inside a 'query' property)
Field names must be exact - use 'op' (not 'operation'), 'breakdowns' (not 'group_by')
Only use the exact operation names listed in the schema (e.g., use "P95" for 95th percentile, not "PERCENTILE")
For all operations EXCEPT COUNT and CONCURRENCY, you must specify a "column" field
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| breakdowns | No | MUST use field name 'breakdowns' (not 'group_by'). Columns to group results by. | |
| calculations | Yes | ⚠️ CRITICAL RULE: For COUNT or CONCURRENCY operations, you MUST OMIT the 'column' field COMPLETELY - do not include it at all. For all other operations, the 'column' field is REQUIRED. | |
| dataset | Yes | The dataset to query. Use __all__ to query across all datasets in the environment. | |
| end_time | No | MUST use field name 'end_time' (with underscore). Absolute end timestamp in seconds. | |
| environment | Yes | The Honeycomb environment to query | |
| filter_combination | No | MUST use field name 'filter_combination' (not 'combine_filters'). How to combine filters: AND or OR. Default: AND. | |
| filters | No | MUST use field name 'filters' (an array of filter objects). Pre-calculation filters for the query. | |
| granularity | No | MUST use field name 'granularity'. Time resolution in seconds. 0 for auto. | |
| havings | No | MUST use field name 'havings'. Post-calculation filters with same column rules as calculations. | |
| limit | No | MUST use field name 'limit'. Maximum number of result rows to return. | |
| orders | No | MUST use field name 'orders' (not 'sort' or 'order_by'). Array of sort configurations. | |
| start_time | No | MUST use field name 'start_time' (with underscore). Absolute start timestamp in seconds. | |
| time_range | No | MUST use field name 'time_range' (with underscore). Relative time range in seconds from now. |