IT OPS

Endpoint Compliance Trend Logging to Axiom

Runs the shell compliance sweep on a schedule and ships every host's encryption and patch result to Axiom as structured events, building a queryable fleet-health time series.

CategoryIT Ops
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerHourly or daily schedule triggers run
  • ActionShell collects encryption + patch + build rowsShell
  • LogicNormalize rows into flat compliance events
  • ActionIngest event batch into Axiom datasetAxiom
  • OutputReturn ingested event countAxiom

What it does

This workflow treats compliance as data, not just tickets. Each scheduled sweep emits one structured event per endpoint into Axiom, recording encryption state, patch age, and OS build with a timestamp. Over time you get dashboards and alerts on fleet-wide compliance drift rather than a single point-in-time snapshot.

When to use it

Use it when you want historical trend lines and ad-hoc querying — "what percent of the fleet was encrypted last quarter?" — instead of only a remediation queue. Pairs well with the Trello sweeps, which handle the per-machine fix.

How it works

  1. 1An hourly or daily schedule triggers the run.
  2. 2A shell step collects encryption, patch age, and build for every host as JSON rows.
  3. 3A logic step normalizes each row into a flat event shape with a compliance boolean.
  4. 4An action ingests the batch of events into the Axiom dataset.
  5. 5The output returns the ingested event count so you can confirm the pipeline is feeding your dashboards.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect ShellRun sandboxed commands inside the workspace.
  2. 2
    Connect AxiomLog streams, queries, dashboards.
  3. 3
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    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.