DATA OPS
Axiom vs Datadog Cross-Source Log Volume Reconcile
Reconciles per-service log volume reported by Axiom against Datadog for the same window, flags services whose Axiom share is disproportionately high.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily reconcile schedule
- ActionQuery Axiom per-service volumeAxiom
- ActionQuery Datadog per-service volumeDatadog
- LogicJoin sources, flag ratio outliers
- ActionOpen Linear ticket per outlier serviceLinear
- OutputPost reconciled table to SlackSlack
What it does
When logs fan out to both Axiom and Datadog, a service that should be sampled or dropped in one pipeline sometimes isn't, so it costs double. This workflow pulls per-service volume from both backends for the same window, computes each service's Axiom-to-Datadog ratio, and surfaces the outliers that signal a misconfigured forwarder.
When to use it
Use it in dual-pipeline setups where Datadog is the source of truth for product telemetry and Axiom holds raw logs, and you want to catch services paying for redundant ingestion.
How it works
- 1A daily schedule kicks off the reconcile for the prior 24 hours.
- 2Query Axiom for per-service ingested volume over the window.
- 3Query Datadog for per-service log volume over the identical window.
- 4A logic step joins the two on service name and flags any service whose Axiom share exceeds the expected ratio band.
- 5For each outlier, open a Linear ticket assigned to the owning team with both volume figures.
- 6Post the reconciled table and ticket links to Slack for visibility.
Set it up
What you configure once, before turning it on.
- 1Connect AxiomLog streams, queries, dashboards.
- 2Connect DatadogMetrics, traces, log search.
- 3Connect LinearIssues, projects, cycles, triage.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Data Ops workflows
Weekly BigQuery Cost Trend Sheet and Exec Digest
Compiles week-over-week BigQuery scheduled-query cost by owner and dataset into a Google Sheet with trend columns.
Daily BigQuery Scheduled-Query Cost Attribution to Owners
Each morning, totals the prior day's on-demand bytes-billed per scheduled query, maps each query to its owner from a label, and posts a per-owner cost leaderboard to Slack.
BigQuery Per-Team Budget Breach Alert to PagerDuty
Tracks month-to-date BigQuery scheduled-query spend per team and, when a team crosses its monthly budget, pages the team's on-call in PagerDuty and snapshots the spend breakdown…
dbt source freshness watcher with severity-routed alerts
Checks Snowflake loaded-at timestamps against each dbt source's freshness SLA, then routes warnings to Slack and hard breaches to a PagerDuty incident so stale data never…
dbt orphan model detector with Linear cleanup tickets
Scans your dbt manifest for models that no other model, exposure, or BI tool consumes.
Raw Sensor Telemetry Archive to BigQuery
Captures every incoming building sensor reading via webhook, normalizes the payload into a consistent schema.
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.