Observability
ObservabilityTelemetry
List keys
Run a query
List values
ModelsExpand Collapse
TelemetryQueryResponse { run, statistics, agents, 5 more }
run: Run { id, accountId, dry, 8 more } A Workers Observability Query Object
A Workers Observability Query Object
query: Query { id, adhoc, created, 6 more }
parameters: Parameters { calculations, datasets, filterCombination, 6 more }
calculations?: Array<Calculation>Create Calculations to compute as part of the query.
Create Calculations to compute as part of the query.
filterCombination?: "and" | "or" | "AND" | "OR"Set a Flag to describe how to combine the filters on the query.
Set a Flag to describe how to combine the filters on the query.
filters?: Array<UnionMember0 { filterCombination, filters, kind } | WorkersObservabilityFilterLeaf { key, operation, type, 2 more } >Configure the Filters to apply to the query. Supports nested groups via kind: ‘group’.
Configure the Filters to apply to the query. Supports nested groups via kind: ‘group’.
WorkersObservabilityFilterLeaf { key, operation, type, 2 more } Filtering best practices: use observability_keys and observability_values to confirm available fields and values. If searching for errors, filter for $metadata.error exists.
Filtering best practices: use observability_keys and observability_values to confirm available fields and values. If searching for errors, filter for $metadata.error exists.
Filter field name. IMPORTANT: do not guess keys. Always use verified keys from previous query results or the observability_keys response. Preferred keys: $metadata.service, $metadata.origin, $metadata.trigger, $metadata.message, $metadata.error.
value?: string | number | booleanFilter comparison value. IMPORTANT: must match actual values in your logs. Verify using previous query results or the /values endpoint. Ensure value type matches the field type. String comparisons are case-sensitive unless using specific operations. Regex uses ClickHouse RE2 syntax (no lookaheads/lookbehinds); examples: ^5\d{2}$ for HTTP 5xx, \bERROR\b for word boundary.
Filter comparison value. IMPORTANT: must match actual values in your logs. Verify using previous query results or the /values endpoint. Ensure value type matches the field type. String comparisons are case-sensitive unless using specific operations. Regex uses ClickHouse RE2 syntax (no lookaheads/lookbehinds); examples: ^5\d{2}$ for HTTP 5xx, \bERROR\b for word boundary.
havings?: Array<Having>Configure the Having clauses that filter on calculations in the query result.
Configure the Having clauses that filter on calculations in the query result.
Set a limit on the number of results / records returned by the query
statistics: Statistics { bytes_read, elapsed, rows_read, abr_level } The statistics object contains information about query performance from the database, it does not include any network latency
The statistics object contains information about query performance from the database, it does not include any network latency
events?: Events { count, events, fields, series }
events?: Array<Event>
Cloudflare Containers event information enriches your logs so you can easily identify and debug issues.
"$workers"?: UnionMember0 { eventType, requestId, scriptName, 7 more } | UnionMember1 { cpuTimeMs, eventType, outcome, 11 more } Cloudflare Workers event information enriches your logs so you can easily identify and debug issues.
Cloudflare Workers event information enriches your logs so you can easily identify and debug issues.
invocations?: Record<string, Array<Invocation>>
Cloudflare Containers event information enriches your logs so you can easily identify and debug issues.
"$workers"?: UnionMember0 { eventType, requestId, scriptName, 7 more } | UnionMember1 { cpuTimeMs, eventType, outcome, 11 more } Cloudflare Workers event information enriches your logs so you can easily identify and debug issues.
Cloudflare Workers event information enriches your logs so you can easily identify and debug issues.