Create and manage Axiom monitors and notifiers through the v2 public API.
npx skills add https://github.com/openclaw/clawhub --skill axiom-alerting
Please help me install this Agent Skill. Skill: axiom-alerting Source: https://github.com/openclaw/clawhub/tree/main/.agents/skills/axiom-alerting Command: npx skills add https://github.com/openclaw/clawhub --skill axiom-alerting
Managing Axiom alerting configuration manually through the UI or raw API calls is repetitive and error-prone, especially when wiring notifiers to monitors and validating alert behavior across deployments.
notifierIds.rangeMinutes, intervalMinutes, and N-of-M trigger fields.Run the setup script, then ask the agent to list existing notifiers and create a threshold monitor for error logs wired to an email notifier in the prod deployment.
High-intent search queries and answers about installing and using this skill.
Write a JSON payload with name, type, query, threshold, and notifierIds, then run the monitor-create script with your deployment name and the JSON file. The script POSTs the body to /v2/monitors using credentials from ~/.axiom.toml.
Create the notifier first with notifier-create, then include its ID in the monitor's notifierIds array when creating or updating the monitor. The monitor payload references notifiers only by ID.
The API supports Threshold, MatchEvent, and AnomalyDetection monitor types. Threshold monitors use operators like Above or BelowOrEqual, while anomaly monitors use AboveOrBelow with a columnName field.
Common causes are thresholds set too strict, a query window that misses data, or N-of-M trigger settings requiring more positive runs. Inspect firing behavior with monitor-history over a known active period, then lower the threshold or widen rangeMinutes.
The payload shape is likely invalid. Use exactly one channel inside properties, and for email notifiers use the emails field rather than recipients. Validate against a known-good example before retrying.
You need an Axiom API token, organization ID, and deployment URL stored in ~/.axiom.toml under a [deployments.<name>] section. The scripts read these values and send them as Bearer token and X-Axiom-Org-Id headers.
vm0-aiIngest logs, metrics, and events into Axiom via REST API.
OpenLaborMonitor server uptime and performance metrics to detect incidents.
WayneBanksyDeploy secure AWS infrastructure with Terraform modules for VPCs, IAM, and monitoring.
cockroachdbConvert React class components to functional components with hooks.