IT OPS

Axiom Sampling-Rule Change Proposed as a GitLab MR

After confirming a noisy service is driving an Axiom cost spike, it drafts a sampling-rule change for that service and opens a GitLab merge request so an engineer can review…

CategoryIT Ops
Enginesim
Difficultyadvanced
Triggerwebhook
Steps5
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerConfirmed noisy-service webhookHTTP webhook
  • LogicDerive target sampling rate to hit budget
  • ActionPatch sampling config in GitLab repoGitLabGitLab
  • ActionOpen GitLab merge request with savings mathGitLabGitLab
  • OutputPost MR link to Slack for approvalSlack

What it does

Turns a diagnosis into a reviewable code change. Given a confirmed noisy service, it computes a sensible sampling rate to cut that service's ingestion, edits the observability config in your repo, and opens a GitLab merge request with the before/after volume math in the description. Nothing changes in production until a human approves the MR.

When to use it

Use it when you want the cost fix to go through real review and version control rather than a console click. The MR leaves an auditable trail of who approved cutting which service's log fidelity.

How it works

  1. 1A webhook delivers the confirmed noisy-service payload (name, byte share, cost).
  2. 2A logic step derives a target sampling rate that brings the service under budget.
  3. 3Read and patch the sampling config file in the GitLab repo.
  4. 4Open a GitLab merge request with the rule diff and projected savings.
  5. 5Post the MR link to Slack so the on-call reviewer can approve it.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect GitLabRepos, MRs, pipelines, registry.
  2. 2
    Connect SlackChannels, DMs, threads, mentions.
  3. 3
    Connect HTTP webhookTrigger any URL on agent actions.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.