Querying

Use this page when Explore, dashboards, alerts, or API queries return empty data or an ORL-2xxx diagnostic.

Symptoms

• OQL returns no rows.
• OQL returns ORL-2001, ORL-2002, or ORL-2003.
• Queries time out.
• A trace cannot be opened by ID.

Checks

Start simple:

spans | limit 20
logs | limit 20
metrics | limit 20
profiles | limit 20

Then add one predicate at a time.

Confirm the active scope bar values. Oriel injects workspace, project, environment, service, and time predicates into telemetry reads.

Common diagnostics

Code	Meaning	Fix
ORL-2001	Syntax error	Check the byte offset and simplify the query.
ORL-2002	Unknown or ambiguous field	Use a known field or check attribute type.
ORL-2003	Unknown function or wrong arity	Check the OQL aggregation table.
ORL-2004	Scan budget exceeded	Narrow scope, time range, or predicates.
ORL-2005	Timeout	Narrow the query or reduce grouping cardinality.
ORL-2007	Scope denied	Check workspace/project permissions.
ORL-2008	Trace not found	Confirm trace ID, time range, retention, and project visibility.
ORL-2010	Unknown dashboard variable	Check dashboard variable names and supplied values.

Recovery

• Use resource. or res. for resource attributes.
• Use backticks for reserved words as field names.
• Avoid high-cardinality groupings until the base filter is selective.
• Use top N by metric after binned stats to cap series.
• Check permissions with a workspace admin when scope-denied errors appear.

See OQL reference for syntax and Query budgets and rate limits for scan and timeout limits.