Observability
Monitor Axiom with MrCron
MrCron mirrors Axiom dataset counts and 24h event ingestion every 5 minutes so you can watch log volume on the same dashboard as errors, deploys, and payments.
How MrCron monitors Axiom
- Dataset count on your Axiom organization.
- Events ingested for the last 24 hours across all datasets.
- Auth-failure detection with an amber Rotate key CTA when the API token stops working.
- Alert rules that fire on ingestion volume spikes via any notification channel.
What you will see
Datasets total, events ingested (24h) on your project card.
Auth flow: API Key. Credentials are stored encrypted at rest with AES-256-GCM and never returned to your browser.
Start monitoring Axiom
Sign in, create a project, and connect Axiom in under a minute. First check ships in the free tier.
Frequently asked questions
- What Axiom credentials does MrCron need?
- An Axiom personal token with read scope. MrCron stores it encrypted at rest and only decrypts it inside the sync worker.
- Does MrCron query log content?
- No. MrCron reads dataset metadata (name, ingest count) only. Log content stays in Axiom; MrCron deep-links to the Axiom UI for search.
- Can I alert on a log-ingest drop?
- Yes. Create an alert rule on the axiom_events_24h metric with a threshold below your baseline. A silent drop is a common signal that a client stopped shipping logs.