New Relic Integration
Parent: MongoDB Monitoring and Observability · Published reference · snapshot 2026-10-23 · skill mongodb-cohort-e4e31a146993
↓ Facts as markdownall context files
Source-anchored research for New Relic Integration. Run status: COMPLETED.
These notes link each claim to its source. Some citations identify archived research reports that are no longer hosted on this site. A published reference means the content is available; it does not certify independent review or accuracy.Read the editorial policy and follow the sources before relying on a claim.
How it works
- For an SRV URI or multiple hosts, disable mongodb_direct_connect; direct connections are invalid in those configurations. New Relic also instructs users to disable it when loadBalanced=true. (low confidence) (verified as of 2026-10-23) [source]
Comparisons and alternatives
- An alternative collection architecture can combine the OpenTelemetry MongoDB receiver with an OTLP exporter targeting New Relic. This is a synthesis of the receiver's documented MongoDB metric collection and New Relic's native OTLP support, rather than a documented feature-equivalence guarantee for New Relic's MongoDB integration. (medium confidence) [source]
Facts and statements
- MongoDB's plugin-based New Relic integration lost support on June 16, 2021. MongoDB explicitly discourages new signups, and its product manager advised affected users to transition to New Relic's remote-agent integration. (high confidence) [source]
- New Relic announced its replacement MongoDB integration as generally available on August 4, 2023 and described it as Prometheus-based. Its current guide identifies instance, database, and collection entities. (medium confidence) [source]
- The current MongoDB integration requires mongodb_cluster_name and mongodb_uri. It exposes an exporter scrape endpoint and provides a scrape_timeout setting. (low confidence) (verified as of 2026-10-23) [source]
- collection_filters and index_filters constrain collection and index coverage; empty filters cover all databases/collections or indexes. Separate switches enable database, collection, index, replica-set, top-admin, and diagnostic metrics. (low confidence) (verified as of 2026-10-23) [source]
- Atlas documents selecting New Relic in the OpenTelemetry Metrics integration, supplying a New Relic API key, and choosing aggregation temporality. Its behavior section specifically states that the integration forwards Atlas Stream Processing metrics without processing them; this page alone does not establish export of all database-cluster metrics. (low confidence) (verified as of 2026-10-14) [source]
- The Atlas OTel endpoint integration requires Project Owner access, connects only to public IP addresses, and enforces TLS with certificates from a public certificate authority. A collector must allow inbound traffic from the relevant Atlas outbound addresses. (low confidence) (verified as of 2026-10-14) [source]
- New Relic's native OTLP ingestion requires an api-key header containing an account license key and TLS. It recommends OTLP/HTTP protobuf and delta temporality for suitable metric instruments while accepting cumulative metrics. (low confidence) (verified as of 2026-10-23) [source]
- The OpenTelemetry MongoDB receiver collects statistics through dbStats and serverStatus and recommends a clusterMonitor user. Its cached October 22, 2026 documentation marks metrics beta and logs development, so deployments should pin and validate their collector version. (low confidence) (verified as of 2026-10-22) [source]
- A December 6, 2021 issue reported that the legacy nri-mongodb integration could not use a private Atlas endpoint's SRV connection. This is historical evidence; the newer guide explicitly discusses SRV URIs, so the old issue does not establish a current general inability to monitor Atlas privately. (medium confidence) [source]
- A firsthand April 27, 2022 incident account describes a MongoDB high-CPU alert delivered through New Relic and PagerDuty. The author then used MongoDB operation inspection and explain output to identify a collection scan and add an index; the account illustrates that an infrastructure alert can initiate database-level diagnosis. (low confidence) [source]
Children
- MongoDB metric filtering in New Relic (frontier)
- MongoDB SRV connection troubleshooting (frontier)
- Atlas Stream Processing OTel export to New Relic (frontier)
- MongoDB application-agent instrumentation (frontier)
Frontier under this node: Atlas Stream Processing OTel export to New Relic, MongoDB SRV connection troubleshooting, MongoDB application-agent instrumentation, MongoDB metric filtering in New Relic