IT OPS

Certificate Expiry Alerts Driven by Axiom Probe Logs

Triggers when a scheduled cert-probe pipeline ships expiry data into Axiom, queries which certificates breach the threshold.

CategoryIT Ops
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerSchedule triggers the query run
  • ActionQuery latest days-to-expiry per endpoint in AxiomAxiom
  • LogicFilter below threshold and dedupe open incidents
  • ActionOpen or update PagerDuty incident for breachesPagerDutyPagerDuty
  • OutputPost at-risk count to Slack ops channelSlack

What it does

Instead of probing endpoints itself, this workflow reads from the certificate expiry data your monitoring already lands in Axiom. It periodically queries Axiom for the latest expiry-day values per endpoint, finds any below the alert threshold, and pages on critical breaches. This keeps a single source of truth and avoids duplicate probing logic.

When to use it

Use this when you already emit TLS expiry metrics into Axiom (from a blackbox exporter, a cron probe, or a sidecar) and want alerting to be a thin query layer on top, rather than a second system that probes endpoints independently.

How it works

  1. 1A schedule triggers the query run a few times a day.
  2. 2An Axiom action queries the most recent days-to-expiry value per endpoint.
  3. 3A logic step filters to endpoints under the configured threshold and dedupes against already-open incidents.
  4. 4Breaching endpoints open or update a PagerDuty incident with the queried expiry detail.
  5. 5A summary output posts the current at-risk count to a Slack ops channel for visibility.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect AxiomLog streams, queries, dashboards.
  2. 2
    Connect PagerDutyIncidents, on-call, escalations.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  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.