Datadog

On this page 7

Datadog is a commercial software-as-a-service observability platform that collects metrics, logs, traces and other telemetry from servers, containers, cloud services and applications, and correlates them in one shared interface for monitoring, alerting and troubleshooting. In Observability within the Cloud field, it is one of the most widely used all-in-one monitoring products, competing with open-source stacks built on Prometheus and Grafana.

Its central idea is correlation through shared tags: every data point carries labels such as host, service, environment and version, so an engineer can move from a latency spike on a dashboard to the related traces and log lines in a few clicks.

How Datadog collects and correlates telemetry

Datadog gathers data through three main paths: a local agent, direct cloud integrations and instrumentation libraries inside applications. All three send data to the hosted backend, where it is indexed, stored and made queryable.

The Datadog Agent is a lightweight process installed on hosts or deployed as a DaemonSet in Kubernetes. It collects system metrics, tails log files, runs checks for databases and middleware and forwards traces from application libraries. Cloud integrations pull metrics from provider APIs, such as AWS CloudWatch or Azure Monitor, without any agent. Tracing libraries and OpenTelemetry SDKs instrument code so that each request produces spans for distributed tracing.

The table below shows how each telemetry type enters the platform and what question it answers.

Telemetry typeCollected byQuestion it answers
MetricsAgent, cloud integrations, custom codeHow much and how fast over time
LogsAgent log tailing, forwarders, APIsWhat exactly happened in one event
TracesTracing libraries, OpenTelemetryWhere a request spent its time
ProfilesContinuous profiler in the runtimeWhich code consumes CPU or memory
Real user dataBrowser and mobile SDKsWhat end users actually experience
Synthetic resultsScripted tests from global locationsWhether key journeys work right now
Telemetry types and their collection paths

Unified service tagging with the reserved tags env, service and version ties these streams together. When tags are applied consistently, a single service page shows its request rate, error rate, latency, recent deployments and related logs; when tags are inconsistent, correlation silently breaks.

Main product areas and what they cover

Datadog is sold as a set of separately priced products on a common data platform. Organizations usually start with infrastructure monitoring and add further modules as their needs grow.

Product areaMain functionTypical users
Infrastructure monitoringHost, container and cloud metricsOperations and platform teams
APMRequest traces and service mapsBackend developers, SRE teams
Log managementIngestion, search and archivingDevelopers, security analysts
Real user monitoringFront-end performance and errorsWeb and mobile teams
Synthetic monitoringScheduled API and browser testsQuality and reliability teams
Cloud securityThreat detection and posture checksSecurity operations teams
Core product areas

On top of the data, Datadog provides dashboards, monitors and service level objectives. Monitors evaluate metric thresholds, anomalies, forecasts or log patterns and notify on-call tools. SLO tracking expresses reliability targets based on a service level indicator and shows the remaining error budget over a rolling window, typically 7, 30 or 90 days.

Datadog compared with open-source observability stacks

The main alternative to Datadog is a self-managed open-source stack, commonly Prometheus for metrics, Grafana for visualization, Loki or Elasticsearch for logs and Jaeger or Tempo for traces, often fed by OpenTelemetry. The choice is largely a trade-off between operating effort and license cost.

AspectDatadogOpen-source stack
Setup timeHours to daysDays to weeks
Operations burdenHandled by the vendorCarried by the internal team
Cost modelPer host, per GB, per spanInfrastructure and staff time
Correlation across signalsBuilt in through tagsRequires careful configuration
Data controlStored in vendor regionsStored in own environment
Vendor lock-inHigher with proprietary agentsLower with open standards
Datadog versus a self-managed stack

Datadog accepts OpenTelemetry data, which reduces lock-in at the instrumentation level, but dashboards, monitors and query syntax remain proprietary. Teams that expect to switch vendors later often instrument with OpenTelemetry from the start and send data to Datadog through the OpenTelemetry Collector.

Pricing, cost control and metric cardinality

Datadog cost is driven by usage-based billing dimensions, and uncontrolled growth in any of them is the most frequent complaint about the platform. Infrastructure is billed per monitored host, logs per ingested and indexed volume, APM per host plus indexed spans, and custom metrics per unique time series.

Metric cardinality is the critical factor for custom metrics. Each unique combination of metric name and tag values counts as a separate series, so adding a tag such as user_id or request_id can multiply one metric into hundreds of thousands of series and a matching bill.

  • Use Logging without Limits style pipelines: ingest broadly, but index only the logs needed for search and archive the rest cheaply.
  • Apply retention filters for traces so that errors and slow requests are kept while routine requests are sampled.
  • Keep high-cardinality identifiers out of metric tags and put them in logs or span attributes instead.
  • Review the usage attribution reports monthly to see which teams and services drive cost.

Common mistakes when adopting Datadog

Most problems with Datadog come from configuration and governance, not from the product itself. The table lists frequent symptoms with their causes and fixes.

SymptomCauseFix
Unexpectedly high invoiceUnbounded tags or indexed logsSet cardinality limits and exclusion filters
Logs not linked to tracesMissing trace IDs in log recordsEnable log injection in tracing libraries
Too many pages at nightStatic thresholds on noisy metricsAlert on symptoms and SLO burn rates
Dashboards nobody trustsInconsistent service and env tagsEnforce unified service tagging
Blind spots in short-lived workloadsNo agent on serverless functionsUse the serverless integration or extension
Symptoms, causes and fixes

Alert fatigue deserves special attention. Alerting on every CPU spike trains engineers to ignore notifications; alerting on user-facing golden signals such as latency, errors, traffic and saturation keeps pages rare and meaningful.

The idea in brief

Modern software runs on many machines and services at once, so when something goes wrong it is hard to see where. Datadog works like a control room with one wall of screens for all of them.

Small programs and connectors send it numbers, messages and request timings from everywhere. Datadog puts them side by side, marks them with the same labels and raises an alarm when something looks wrong. Engineers find the cause faster because every clue is already in one place, but the service is paid for by usage, so careless data collection becomes expensive.

A practical scenario

An online travel agency runs about 40 microservices on Kubernetes in a public cloud. The platform team deploys the Datadog Agent as a DaemonSet, enables APM in each service and applies the env, service and version tags in the deployment pipeline. Monitors alert when the booking service misses its 99.9% availability SLO at a fast burn rate.

One evening the booking error rate rises to 4% within ten minutes of a release. The on-call engineer opens the service page, sees that errors started with the new version, follows a failed trace to a payment adapter and reads the linked log line showing a changed API field. The team rolls back in under fifteen minutes, and the incident consumes only a small part of the monthly error budget instead of the full night it would have taken without correlated data.