New Relic NRQL LIMIT/OFFSET Pagination Across NRQL, UI Dashboard, and Agent SDKs

Integration Boundary: NRQL vs UI Dashboard vs Agent SDK

Goal: determine whether LIMIT and OFFSET behave consistently when applied in NRQL queries, UI dashboards, and data ingestion through agent SDKs.

Constraints: NRQL enforces a 10,000‑row cap per query; OFFSET may generate non‑deterministic ordering if no SORT clause is specified. UI dashboards mimic NRQL limits, but embedded widgets in third‑party interfaces sometimes report different row counts when agent sampling rates or SDK versions change. Documentation does not clarify whether pagination state is preserved after agent restarts or configuration changes.

Unresolved behavior: Is pagination state and ordering deterministic across all components when OFFSET is used without an explicit SORT clause?

• Does the UI dashboard reset OFFSET after an agent restart?
• Is pagination state preserved when switching between NRQL API and UI query builder?
• Should a deterministic SORT clause be required for reliable pagination across data types?