StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. DevOps
  3. Performance Monitoring
  4. Performance Monitoring
  5. New Relic vs StatsD

New Relic vs StatsD

OverviewDecisionsComparisonAlternatives

Overview

New Relic
New Relic
Stacks22.7K
Followers8.7K
Votes1.9K
StatsD
StatsD
Stacks373
Followers293
Votes31

New Relic vs StatsD: What are the differences?

Introduction

New Relic and StatsD are both performance monitoring tools that are commonly used in the field of software development. While they serve a similar purpose, there are key differences between the two.

  1. Integration capabilities: New Relic offers a wide range of integrations with various programming languages, frameworks, and cloud platforms. It has built-in support for collecting data from different parts of an application stack, giving developers a comprehensive view of their system's performance. On the other hand, StatsD is a simple, lightweight tool that focuses primarily on collecting and aggregating data from custom application metrics.

  2. Data visualization: New Relic provides a rich user interface with interactive charts and graphs to visualize performance data. It offers various pre-built dashboards and reporting features that make it easier to analyze and interpret metrics. In contrast, StatsD relies on external integrations or custom implementations for data visualization. It typically pushes the collected metrics to other tools or services for further analysis and visualization.

  3. Granularity of metrics: New Relic provides detailed and granular metrics out of the box. It captures and reports data in real-time, allowing developers to monitor application performance at a fine level of detail. StatsD, on the other hand, is designed to capture high-level aggregated metrics. It focuses on tracking and reporting average values, counts, or rates over a period of time.

  4. Alerting and notification: New Relic offers powerful alerting capabilities that allow users to set up customized alerts based on various conditions, thresholds, and patterns. It supports multiple notification channels, including email, SMS, and integrations with popular communication tools like Slack. StatsD, however, does not have built-in alerting functionality. It primarily focuses on data collection and relies on external tools or services for alerting and notification.

  5. Real-time versus batch processing: New Relic operates in real-time, continuously collecting and reporting performance data as it happens. This allows developers to closely monitor their applications and respond quickly to any performance issues. On the other hand, StatsD follows a batch processing approach, where it collects metrics over a period of time and then sends them in aggregated batches. This can result in a delay in receiving the data and responding to any performance anomalies.

  6. Agent-based versus agentless: New Relic typically requires an agent to be installed and configured within the application's environment. The agent collects and sends performance data to the New Relic platform for analysis. In contrast, StatsD is agentless and relies on client libraries or plugins to collect and send metrics. This agentless approach makes it easier to integrate and use StatsD with different applications or systems.

In summary, New Relic offers comprehensive integration capabilities, rich data visualization, detailed metrics, powerful alerting, real-time monitoring, and requires an agent for data collection. On the other hand, StatsD focuses on simplicity, customizable metrics aggregation, external data visualization, batch processing, and does not require an agent for data collection.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs
CLI (Node.js)
or
Manual

Advice on New Relic, StatsD

Medeti
Medeti

Jun 27, 2020

Needs adviceonAmazon EKSAmazon EKSKubernetesKubernetesAWS Elastic Load Balancing (ELB)AWS Elastic Load Balancing (ELB)

We are looking for a centralised monitoring solution for our application deployed on Amazon EKS. We would like to monitor using metrics from Kubernetes, AWS services (NeptuneDB, AWS Elastic Load Balancing (ELB), Amazon EBS, Amazon S3, etc) and application microservice's custom metrics.

We are expected to use around 80 microservices (not replicas). I think a total of 200-250 microservices will be there in the system with 10-12 slave nodes.

We tried Prometheus but it looks like maintenance is a big issue. We need to manage scaling, maintaining the storage, and dealing with multiple exporters and Grafana. I felt this itself needs few dedicated resources (at least 2-3 people) to manage. Not sure if I am thinking in the correct direction. Please confirm.

You mentioned Datadog and Sysdig charges per host. Does it charge per slave node?

1.51M views1.51M
Comments
Benoit
Benoit

Principal Engineer at Sqreen

Sep 17, 2019

Decided

I chose Datadog APM because the much better APM insights it provides (flamegraph, percentiles by default).

The drawbacks of this decision are we had to move our production monitoring to TimescaleDB + Telegraf instead of NR Insight

NewRelic is definitely easier when starting out. Agent is only a lib and doesn't require a daemon

457k views457k
Comments
Attila
Attila

Founder at artkonekt

Mar 24, 2020

Decided

I haven't heard much about Datadog until about a year ago. Ironically, the NewRelic sales person who I had a series of trainings with was trash talking about Datadog a lot. That drew my attention to Datadog and I gave it a try at another client project where we needed log handling, dashboards and alerting.

In 2019, Datadog was already offering log management and from that perspective, it was ahead of NewRelic. Other than that, from my perspective, the two tools are offering a very-very similar set of tools. Therefore I wouldn't say there's a significant difference between the two, the decision is likely a matter of taste. The pricing is also very similar.

The reasons why we chose Datadog over NewRelic were:

  • The presence of log handling feature (since then, logging is GA at NewRelic as well since falls 2019).
  • The setup was easier even though I already had experience with NewRelic, including participation in NewRelic trainings.
  • The UI of Datadog is more compact and my experience is smoother.
  • The NewRelic UI is very fragmented and New Relic One is just increasing this experience for me.
  • The log feature of Datadog is very well designed, I find very useful the tagging logs with services. The log filtering is also very awesome.

Bottom line is that both tools are great and it makes sense to discover both and making the decision based on your use case. In our case, Datadog was the clear winner due to its UI, ease of setup and the awesome logging and alerting features.

471k views471k
Comments

Detailed Comparison

New Relic
New Relic
StatsD
StatsD

The world’s best software and DevOps teams rely on New Relic to move faster, make better decisions and create best-in-class digital experiences. If you run software, you need to run New Relic. More than 50% of the Fortune 100 do too.

It is a network daemon that runs on the Node.js platform and listens for statistics, like counters and timers, sent over UDP or TCP and sends aggregates to one or more pluggable backend services (e.g., Graphite).

Performance Data Retention;Real-User Response Time, Throughput, & Breakdown by Layer;App Response Time, Throughput, & Breakdown by Component;App Availability Monitoring, Alerting, and Notification;Automatic Application Topology Mapping;Server Resource and Availability Monitoring;Error Detection, Alerting, & Analysis;JVM Performance Analyzer;Database Call Response Time & Throughput;Performance Data API Access;Code Level Diagnostics, Transaction Tracing, & Stack Trace Details;Slow SQL and SQL Performance Details;Real-User Breakdown by Web Page, Browser, & Geography;Track Individual Key Transactions;Mobile Features- Alerting, Summary Data, Overview Page, Topo Map, HTTP Requests, HTTP Error Summary, HTTP Error Detail, Versions, Carriers, Devices, Geo Map
Network daemon; Runs on the Node.js platform; Sends aggregates to one or more pluggable backend services
Statistics
Stacks
22.7K
Stacks
373
Followers
8.7K
Followers
293
Votes
1.9K
Votes
31
Pros & Cons
Pros
  • 414
    Easy setup
  • 344
    Really powerful
  • 245
    Awesome visualization
  • 194
    Ease of use
  • 151
    Great ui
Cons
  • 20
    Pricing model doesn't suit microservices
  • 10
    UI isn't great
  • 7
    Visualizations aren't very helpful
  • 7
    Expensive
  • 5
    Hard to understand why things in your app are breaking
Pros
  • 9
    Open source
  • 7
    Single responsibility
  • 5
    Efficient wire format
  • 3
    Loads of integrations
  • 3
    Handles aggregation
Cons
  • 1
    No authentication; cannot be used over Internet
Integrations
AppHarbor
AppHarbor
Cloudability
Cloudability
HP Cloud Compute
HP Cloud Compute
cloudControl
cloudControl
Papertrail
Papertrail
Loggly
Loggly
Ducksboard
Ducksboard
Blitz
Blitz
Pivotal Tracker
Pivotal Tracker
Red Hat OpenShift
Red Hat OpenShift
Node.js
Node.js
Docker
Docker
Graphite
Graphite

What are some alternatives to New Relic, StatsD?

Datadog

Datadog

Datadog is the leading service for cloud-scale monitoring. It is used by IT, operations, and development teams who build and operate applications that run on dynamic or hybrid cloud infrastructure. Start monitoring in minutes with Datadog!

Grafana

Grafana

Grafana is a general purpose dashboard and graph composer. It's focused on providing rich ways to visualize time series metrics, mainly though graphs but supports other ways to visualize data through a pluggable panel architecture. It currently has rich support for for Graphite, InfluxDB and OpenTSDB. But supports other data sources via plugins.

Kibana

Kibana

Kibana is an open source (Apache Licensed), browser based analytics and search dashboard for Elasticsearch. Kibana is a snap to setup and start using. Kibana strives to be easy to get started with, while also being flexible and powerful, just like Elasticsearch.

Prometheus

Prometheus

Prometheus is a systems and service monitoring system. It collects metrics from configured targets at given intervals, evaluates rule expressions, displays the results, and can trigger alerts if some condition is observed to be true.

Raygun

Raygun

Raygun gives you a window into how users are really experiencing your software applications. Detect, diagnose and resolve issues that are affecting end users with greater speed and accuracy.

Nagios

Nagios

Nagios is a host/service/network monitoring program written in C and released under the GNU General Public License.

AppSignal

AppSignal

AppSignal gives you and your team alerts and detailed metrics about your Ruby, Node.js or Elixir application. Sensible pricing, no aggressive sales & support by developers.

Netdata

Netdata

Netdata collects metrics per second & presents them in low-latency dashboards. It's designed to run on all of your physical & virtual servers, cloud deployments, Kubernetes clusters & edge/IoT devices, to monitor systems, containers & apps

AppDynamics

AppDynamics

AppDynamics develops application performance management (APM) solutions that deliver problem resolution for highly distributed applications through transaction flow monitoring and deep diagnostics.

Zabbix

Zabbix

Zabbix is a mature and effortless enterprise-class open source monitoring solution for network monitoring and application monitoring of millions of metrics.

Related Comparisons

GitHub
Bitbucket

Bitbucket vs GitHub vs GitLab

GitHub
Bitbucket

AWS CodeCommit vs Bitbucket vs GitHub

Kubernetes
Rancher

Docker Swarm vs Kubernetes vs Rancher

gulp
Grunt

Grunt vs Webpack vs gulp

Graphite
Kibana

Grafana vs Graphite vs Kibana