High cost, short retention
To control the bill, teams drop retention to 7 or 3 days and exclude noisy sources. Then the log an engineer needs is gone from search.
Move the two sliders. The saving shown is after paying for CtrlB.
Datadog list prices, annual plan, 30 days of retention, about 1 KB per log. With CtrlB, Datadog still ingests every log and indexes 5%. CtrlB Pro is $0.20 per GB with 30 days of retention included.
Datadog charges $0.10 per GB to ingest logs and $2.50 per million log events to keep them searchable for 30 days. So the bill grows with every log you index, and teams cut the logs they need later.
To control the bill, teams drop retention to 7 or 3 days and exclude noisy sources. Then the log an engineer needs is gone from search.
Archived logs have to be indexed again before you can search them, up to 1 billion events per job, and you pay to scan and index them.
Lower storage costs come with trade-offs. Monitoring isn't included with Flex Logs, search compute is billed separately, and archived S3 logs can't be searched.
CtrlB reads your Datadog data two ways: from the archive Datadog already writes to your S3, and live from the Datadog Agent. Each works on its own. Use either one, or both. Datadog keeps running your alerts and dashboards either way.
Datadog already writes every log it receives to your S3 . Paste the bucket into CtrlB and grant read-only access. Months of logs become searchable in milliseconds, with no rehydration.
Add CtrlB as a second destination in datadog.yaml and restart the Agent. Logs, traces and metrics now reach CtrlB as well as Datadog, through Agent dual shipping .
Datadog only needs indexed data for monitors, dashboards and recent debugging. Once the rest is searchable in CtrlB, turn indexing down with settings you already have. The archive covers your logs. Live data also covers traces and metrics.
In 30 minutes, we'll review your Datadog deployment, identify what's driving your bill, and show how much of it CtrlB can take off.
CtrlB searches the archive where Datadog already writes it. Nothing is copied to another vendor to make it searchable.
A read-only IAM role. CtrlB can't write to, change or delete your archive.
Access lives in your AWS account. Remove the role and access ends.
Use CtrlB as a managed service, or deploy it in your own cloud account or VPC.
CloudTrail, WAF, VPC flow and DNS logs stay searchable while the incident is still open.
No. Datadog keeps your monitors, dashboards, APM and on-call. It indexes fewer logs, and CtrlB answers the searches across everything Datadog archives to your S3.
A read-only IAM role on the S3 bucket your Datadog Log Archive writes to. CtrlB cannot change or delete anything in that bucket, and you can revoke the role at any time.
Yes. Monitors keep running on the logs you keep indexed, and Datadog builds log-based metrics from every log it ingests, indexed or not.
Datadog uploads archive files to your bucket every few minutes, and CtrlB searches them as they land. The last few minutes stay in Datadog, where live alerting happens.
Yes. CloudTrail, WAF, VPC flow, DNS and audit logs that Datadog archives are searchable in CtrlB, so an investigation can look back without a rehydration job.
The Free plan covers up to 150 GB a month with 14 days of retention. Pro is $0.20 per GB with 30 days of retention included. Enterprise pricing is based on your volume and retention.
Book 30 minutes with an engineer. Bring your archive bucket, and leave with every log searchable and a plan to cut what Datadog indexes.