Skip to main content
Use the Axiom integration to ingest structured events, query logs and traces with APL, query OpenTelemetry metrics with MPL, manage observability resources, and start automations from monitor state changes.

Connect Axiom

Create an API token in Axiom and connect it from your Automate.ax project. Advanced tokens must grant every capability used by your automation. Query and ingestion actions need dataset and query access; resource actions need matching datasets, monitors, notifiers, saved queries, or dashboards permissions. Monitor triggers need read and write access to monitors and notifiers.
automations/investigate-axiom-alerts.automation.ts
axiomAccount declares a named static project binding when an automation uses more than one Axiom account. Every action and trigger also accepts an optional account binding.

Query and ingest endpoints

APL, MPL, metrics discovery, and ingest actions accept an optional edgeUrl. It defaults to the US East 1 (AWS) edge at https://us-east-1.aws.edge.axiom.co; set it to the edge that stores the target dataset. Automate.ax accepts only HTTPS *.edge.axiom.co origins and never follows redirects. Query windows default to the 30 minutes before execution. Metrics discovery accepts fixed RFC3339 timestamps because Axiom’s discovery endpoints require them.

Monitor triggers

Automate.ax creates one custom webhook notifier, attaches it without replacing the monitor’s existing notifier IDs, authenticates deliveries with a managed secret header, and emits an ordinary root event. When no deployment needs the source, Automate.ax detaches and deletes only its managed notifier. Axiom API errors include the HTTP status and provider details. Automate.ax retries 429 request-rate limits and 430 ingest or query limits using Axiom’s reset timing when available.

Exports

  • axiom contains the packaged Axiom actions and triggers.
  • axiomAccount("name") selects a named Axiom connection.

Triggers

Actions