New Relic Pioneered APM. The Telemetry Namespace It Built Is Centrally Indexed.
by Nick Clark | Published March 28, 2026
New Relic pioneered application performance monitoring and evolved into a comprehensive observability platform with the New Relic Telemetry Data Platform (NRDB), NRQL query language, and usage-based pricing that ingests all telemetry types into a single data store. The unified telemetry approach is powerful. But the namespace that indexes this telemetry — entity relationships, attribute hierarchies, and service maps — is centrally indexed in New Relic's cloud infrastructure. The gap is between centralized telemetry indexing and namespace governance that adapts locally to the infrastructure being observed.
New Relic's telemetry platform and NRQL query language provide genuine analytical power over operational data. The entity synthesis framework and AI-driven insights are practical tools. The gap described here is about where the telemetry namespace lives and who governs it.
Centralized indexing of distributed telemetry
Agents and integrations running across distributed infrastructure collect telemetry and send it to New Relic's centralized data platform. The platform indexes all incoming data, synthesizes entity relationships, and makes the data queryable through NRQL. The telemetry originates in distributed infrastructure. Its namespace is centralized.
This means the namespace authority over your own infrastructure's telemetry lives in New Relic's cloud. How entities relate, what attributes define them, and how the namespace organizes your operational data is determined by New Relic's entity synthesis rules and indexing logic.
Entity synthesis without governance participation
New Relic's entity synthesis framework automatically creates entities from incoming telemetry and establishes relationships between them. This is useful for auto-discovering infrastructure topology. But the synthesis rules are New Relic's rules. The customer's infrastructure teams do not participate in governing how their entities are synthesized, how relationships are established, or how the namespace evolves.
Custom entities and relationships can be defined through NerdGraph API. But these definitions are stored in New Relic's platform. The governance of the telemetry namespace is New Relic's, not the infrastructure team's.
What scope-governed indexing provides
A scope-governed index would let infrastructure teams govern their own telemetry namespace through locally held anchor nodes. Entity synthesis would be a governed process where new entities are proposed, validated through scoped consensus, and committed with lineage. The namespace would adapt structurally as the monitored infrastructure evolves, governed by the teams responsible for each segment.
New Relic's telemetry ingestion and analytical capabilities would continue to provide value. The governed index would ensure that the namespace organizing that telemetry is structurally owned by the infrastructure teams, not centrally indexed by the monitoring platform.
The remaining gap
New Relic built a unified telemetry platform for comprehensive observability. The remaining gap is in namespace authority: whether the index organizing telemetry data can be governed by the infrastructure teams producing it rather than centrally by the observability platform consuming it.
