AI AGENTS
Datadog Log Retention Cut Proposal Agent
On request, an agent inspects Datadog log indexes and their retention settings, identifies indexes where shorter retention or exclusion filters would cut cost with low risk.
How it runs
The automated pipeline, trigger to output.
- TriggerOperator runs retention review
- ActionPull log index configs and ingest volumeDatadog
- LogicBucket indexes by cut risk
- ActionAgent drafts retention-cut proposalOpenAI
- OutputPost proposal with rollback to SlackSlack
What it does
Reviews your Datadog log indexes, their retention periods, and ingest patterns to find places where retention is longer than needed or where noisy log streams could be excluded. The agent produces a concrete, risk-rated proposal: which indexes to shorten, which filters to add, the estimated monthly savings, and how to roll each change back.
When to use it
Reach for it when log management is your biggest Datadog line item and you need a defensible plan to bring it down without losing logs anyone actually queries. Trigger it manually before a cost-review meeting.
How it works
- 1An operator runs the workflow manually when a retention review is needed.
- 2The agent pulls Datadog log index configs, retention settings, and recent ingest volume per index.
- 3A logic step separates indexes into safe-to-cut, needs-review, and leave-alone buckets based on query activity and retention.
- 4The agent drafts per-index recommendations with estimated savings and explicit rollback steps.
- 5The proposal posts to Slack for the team to approve before anyone changes config.
Set it up
What you configure once, before turning it on.
- 1Connect DatadogMetrics, traces, log search.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More AI Agents workflows
Custom Metrics Cardinality Spike Pager
A webhook from a Datadog monitor fires when custom-metric cardinality jumps; an agent pinpoints the offending metric and tag, estimates the added cost.
Sentry-to-Confluence Runbook Updater
When a Sentry issue is resolved, the agent finds the matching Confluence runbook page and proposes an inline update with the verified fix.
Stale Doc-PR Chaser for Runbook Gaps
On a daily schedule the agent finds runbook doc PRs that were opened from resolved incidents but never reviewed, summarizes what each one fixes.
Resolved Incident to Public Troubleshooting Doc
For customer-facing errors resolved in Sentry, the agent drafts a sanitized troubleshooting entry and opens a PR to your ReadMe documentation.
On-Call Runbook Gap Closer: Resolved Sentry Issues to Doc PRs
An agent reads each newly resolved Sentry issue, compares the actual fix against your existing runbook, and opens a GitHub PR adding the missing remediation steps.
Weekly On-Call Doc-Gap Digest
Each week the agent reviews every Sentry issue resolved in the last 7 days, ranks the ones whose runbook coverage is missing or thin.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.