We use analytics cookies.We use cookies to analyze site traffic and improve your experience.
Loading...
System Design Masterclass · Observability Monitoring
Free preview: the first 2 parts of this 7-part lesson.
Already bought the course? Sign in to read the whole lesson.
this lesson is part of
System Design Masterclass
Unlock this lesson and the 751 other paid lessons
$25 once, by PayPal
See the System Design courseread the rest of this lesson in
System Design Masterclass
Unlock this lesson and the 751 other paid lessons
$25 once, by PayPal
See the System Design coursein Observability Monitoring
This lesson is part of the full System Design Masterclass. Unlock it along with 769 other lessons for a one-time payment.
One-time payment by card or PayPal
Get Lifetime AccessOne-time payment: UPI, card or netbanking
Get Lifetime Access18 Foundation lessons are free, no payment needed. Try them now
Before Datadog, a typical monitoring stack looked like this: Prometheus for metrics, for logs, Jaeger for traces, PagerDuty for alerting, Grafana for dashboards, five different systems with five different configurations, five different query languages, and no built-in correlation between them.
Datadog's pitch was simple: what if all of that lived in one platform? Metrics, logs, traces, infrastructure monitoring, APM, RUM, synthetic monitoring, security monitoring, CI visibility, database monitoring, all in one place, all correlated, all queryable with the same interface.
The value proposition isn't any single feature, it's the integration. Click a metric spike, see related traces. Click a slow trace span, see the logs from that service at that time. Click a log error, see the infrastructure metrics for that host. This cross-signal correlation happens automatically because Datadog owns the entire pipeline.
| Product | What It Does | Competes With |
|---|---|---|
| Infrastructure | Host metrics, container metrics, monitoring | + Grafana |
| APM | Distributed tracing, service maps, profiling | Jaeger, New Relic |
| Log Management | Centralized logging with full-text search | ELK Stack, Splunk |
| RUM | Real user monitoring for web and mobile | Google Analytics, SpeedCurve |
| Synthetics | Synthetic monitoring and API testing | Checkly, Pingdom |
| Dashboards | Customizable dashboards and notebooks | |
| Monitors | Alerting with ML-based anomaly detection | PagerDuty alerting |
| Security | Cloud security posture, threat detection | Crowdstrike, Wiz |
The Datadog Agent is a lightweight process installed on every host or pod. It collects infrastructure metrics, receives traces and logs from your application, and ships everything to Datadog's cloud backend. The agent also runs integration checks, pulling metrics from databases, caches, message queues, and cloud services.
Pricing model: Datadog bills per host per month for infrastructure, per GB ingested for logs, and per span for APM. At scale, costs can be significant, many teams report spending $50-200+ per host per month when using multiple products. This is the primary criticism of Datadog.
It is easy and good
“It is really nice and good Please join the course”