Axiom integration. Triage Axiom monitors and run APL queries to find the cause.
Praxen Inc. triages every Axiom monitor as it fires, runs APL queries over your logs and traces to find the cause, and turns your saved queries into checks.
Get started for freeWhat Praxen Inc. does with Axiom.
Alerts triaged on arrival
Every Axiom monitor that fires lands in Praxen Inc. as an issue, and an agent triages it the moment it does, correlated with recent changes across the graph.
APL mid-investigation
Agents run APL queries against your datasets while they work an issue, and every result is cited back to the query behind it.
Your queries become checks
Every saved query and dashboard becomes a check: agents run it on a cadence and flag results that stray from the service's normal.
First-class in the graph
Axiom joins the context graph as a source, so a spike in a dataset lands next to the deploy and the resources behind it.
How to set up Axiom
- Find the Axiom region in Organization Settings: api.axiom.co for US or api.eu1.axiom.co for EU.
- Create an API token with read access to the datasets you intend to query; paste it into Praxen Inc.
- Validate the connection and review the praxen webhook notifier added to monitors.
Permissions and access
Dataset reads support investigation queries. Alert provisioning additionally creates a custom webhook notifier and updates monitors; exact token capabilities for that setup are not listed by the checked form. Verify those provider-side capabilities when creating the token.
Discovery, refresh and the connected view
Agents run APL queries, explore dataset schemas and fields, and inspect monitor status. Recurring reconciliation attaches the notifier to monitors. Terraform-managed monitors need its ID in notifier_ids to avoid drift. This is an Axiom log/event query workflow rather than Honeycomb trace analysis.
Disconnect and revoke access
Disconnect Axiom and revoke its API token. Praxen Inc. removes the notifier from monitors; remove the notifier ID from Terraform at the same time.
Axiom tools.
The calls Praxen Inc. can make to Axiom when it looks into an issue.
Axiom -
axiomApiCall any Axiom REST endpoint that lacks a dedicated tool -
axiomQueriesRun an Axiom query (APL for logs/traces/events, MPL for metrics) -
axiomDatasetsRead Axiom datasets and their fields -
axiomDashboardsRead or create Axiom dashboards -
axiomMonitorsRead or create Axiom monitors -
axiomViewsRead or create Axiom saved views -
axiomAnnotationsList or create Axiom annotations -
axiomVirtualFieldsList or create Axiom virtual fields -
axiomListNotifiersList alert notifiers in Axiom
Axiom setup and troubleshooting
Common questions.
How do I connect Axiom to Praxen Inc.?
Find the Axiom region in Organization Settings: api.axiom.co for US or api.eu1.axiom.co for EU. Create an API token with read access to the datasets you intend to query; paste it into Praxen Inc. Validate the connection and review the praxen webhook notifier added to monitors.
What can Praxen Inc. read from Axiom?
Agents run APL queries, explore dataset schemas and fields, and inspect monitor status. Recurring reconciliation attaches the notifier to monitors. Terraform-managed monitors need its ID in notifier_ids to avoid drift. This is an Axiom log/event query workflow rather than Honeycomb trace analysis.