Monitoring and observability

Datadog vs New Relic

Both are offered as hosted services, so the useful comparison is each vendor’s track record, SDK and licence rather than version support. Both are proprietary services. In the last 90 days Datadog’s status feed logged 11 incidents and New Relic’s 2.

Last checked against Datadog Status, npm, deps.dev, OSV.dev, CISA KEV and New Relic Status.

Side by side

Every value links to its source. Where a row doesn’t apply to one of them, the cell says why.

Support and releases
DatadogNew Relic
Latest release

6.21.0

Node.js tracer dd-trace, Oct 14, 2026

npm

14.8.0

Node.js agent newrelic, Oct 13, 2026

npm

Releases in the last 12 months

85 releases

Node.js tracer dd-trace

npm

50 releases

Node.js agent newrelic

npm

Security
DatadogNew Relic
Advisories published in the last 12 months

1, worst rated high

For dd-trace

OSV.dev

None

For newrelic

OSV.dev

OpenSSF Scorecard

6 / 10

DataDog/dd-trace-js, Aug 24, 2026

Scorecard

6.6 / 10

newrelic/node-newrelic, Aug 24, 2026

Scorecard

Status and incidents
DatadogNew Relic
Status now

Operational

Status page

Operational

Status page

Incidents in the last 90 days

11, 1 major

Most recent: Delayed Events (Sep 30, 2026)

History

2, 1 major

Most recent: Data Irregularities for US region (Sep 25, 2026)

History

Licence and hosting
DatadogNew Relic
Licence

Proprietary service

Not open source

SDK (dd-trace): Apache-2.0 OR BSD-3-Clause.

Proprietary service

Not open source

SDK (newrelic): Apache-2.0.

How you run it

Managed by Datadog; you run its agent and tracers

Managed by New Relic; you run its agents

Adoption
DatadogNew Relic
npm downloads last week

10.2M

dd-trace

npm

1.2M

newrelic

npm

  • Advisory counts cover every version, old ones included, and a heavily used, well-audited project often has more. Check the versions you run with the dependency check.
  • Incident history is context, not a ranking: every vendor has incidents, and vendors post them at different thresholds.

Which fits your constraints

Read across for what matters to you. Each answer comes from the data above or the project’s licence and hosting options.

How Datadog and New Relic fit common constraints
DatadogNew Relic
An open-source licence

No: Proprietary service

No: Proprietary service

Someone else runs it for you

Yes: From Datadog

Yes: From New Relic

You can run it on your own servers

No: Hosted only

No: Hosted only

A public incident history

Yes: Status page with 90-day history

Yes: Status page with 90-day history

What each is good at

Datadog

Comprehensive monitoring and analytics platform

Strengths

  • All-in-one platform (metrics, logs, traces)
  • Beautiful dashboards
  • Extensive integrations (400+)
  • Powerful alerting and anomaly detection

Trade-offs

  • Vendor lock-in
  • Requires agent installation

Common uses

  • Full-stack monitoring
  • APM
  • Log management
  • Security monitoring

New Relic

Full-stack observability platform

Strengths

  • Comprehensive observability
  • Real user monitoring (RUM)
  • AI-powered insights
  • Strong APM capabilities

Trade-offs

  • Vendor lock-in
  • Complex UI for beginners
  • Data retention limitations

Common uses

  • Application performance monitoring
  • User experience monitoring
  • Infrastructure monitoring

From StackPrism’s curated notes. Pricing isn’t covered here: it changes often, so check each vendor’s pricing page.

When teams weigh these two

Both are hosted observability platforms that cover APM, infrastructure metrics, logs and real-user monitoring in one product, so teams usually compare how each instruments their stack and how it’s priced, which StackPrism doesn’t track. The table covers what can be checked: each vendor’s status history and the health of its Node.js agent.

How this comparison works

Release lines and end-of-life dates come from endoflife.date, release counts from deps.dev’s publish dates, and advisories from OSV.dev, counted once per flaw even when it’s listed under several ids, and checked against CISA’s list of vulnerabilities known to be exploited. Status and incident history come from each vendor’s public status feed; licences from each project’s licence file or the vendor’s licensing page, linked in the table.

The data refreshes every few hours and the time it was checked is shown above. There’s no pricing and no overall winner: which one fits depends on your constraints. To see how the versions you actually run hold up, check your repo.

Already using one of them?

Paste a public GitHub repo and see what’s vulnerable, end of life or deprecated in it today. Free, no sign-up.