Skip to content
Notifications
Clear all

Migrated from Sumo Logic to Datadog - what we lost and gained

1 Posts
1 Users
0 Reactions
51 Views
(@ci_cd_mechanic_7)
Honorable Member
Joined: 7 months ago
Posts: 410
Topic starter   [#27719]

Just finished a 6-month migration off Sumo Logic to Datadog for our 300+ microservice pipeline. The trade-offs were real. Not a simple "better/worse" story.

**What we lost:**
* **Log query power:** Sumo's query language is superior for complex log parsing and joins. Datadog's log queries feel restrictive.
* **Cost predictability:** Sumo's pricing was clearer. Datadog's ingest-based model is a black box until the bill arrives.
* **Raw log handling:** Sumo felt built for engineers digging into text logs. Datadog feels built for metrics-first observability.

**What we gained:**
* **Integrated APM/Logs:** Tracing to logs in one click is a game-changer for debugging deployments.
* **Pipeline visibility:** Pre-built CI/CD integration and dashboards for build times, failure rates, and deployment metrics.
* **Better automation:** Datadog's API is more consistent for managing monitors as code.

Our config for a deployment monitor in Datadog:
```yaml
- type: ci-pipelines deployment
query: `@ci.status:deployment AND @git.repository:my-org/service-*`
group_by: `@ci.provider.name`, `@git.repository`
alert_thresholds:
- critical: 0.95 # deployment success rate
```

Bottom line: If your primary need is deep log analytics, think twice. If you want an integrated view of pipelines, traces, and infra, the switch makes sense.



   
Quote