AI AGENTS
Datadog Noisy-Log Sampling Proposal to GitLab MR
Monthly, an agent clusters Datadog log patterns, identifies the highest-volume low-severity sources.
How it runs
The automated pipeline, trigger to output.
- TriggerMonthly schedule starts the review
- ActionPull 30 days of indexed log analytics from DatadogDatadog
- LogicRank clusters, filter to low-value sources
- LogicSplit into exclusion vs sampling buckets
- ActionOpen GitLab MR with filters and projected reductionGitLab
- OutputNotify platform channel in SlackSlack
What it does
This agent targets Datadog log management costs. It clusters indexed log events by source and message pattern, finds the high-volume low-severity streams driving your indexing spend, and opens a GitLab merge request adding exclusion filters and sampling rates to your logging pipeline config, with a projected reduction in indexed events per month.
When to use it
Use it when Datadog indexed-log costs are the problem and your config lives in GitLab. Best for teams that want monthly, audited tuning of log exclusion filters rather than clicking through the Datadog UI.
How it works
- 1A monthly schedule starts the run.
- 2The agent pulls the last 30 days of indexed log analytics from Datadog grouped by service and pattern.
- 3It ranks clusters by indexed volume and filters to low-severity, low-value sources.
- 4A logic step splits candidates into full-exclusion versus partial-sampling buckets based on whether any signal value remains.
- 5It drafts exclusion filters and sampling percentages and estimates the monthly indexed-event reduction.
- 6It opens a GitLab merge request editing the logging pipeline config with the rules and savings summary, then notifies the platform channel in Slack.
Set it up
What you configure once, before turning it on.
- 1Connect DatadogMetrics, traces, log search.
- 2Connect GitLabRepos, MRs, pipelines, registry.
- 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.