Honeycomb integration. Triage Honeycomb triggers and query your datasets to find the cause.
Praxen Inc. triages every Honeycomb trigger as it fires, queries your datasets to find the cause, and turns your saved queries and boards into checks.
Get started for freeWhat Praxen Inc. does with Honeycomb.
Triggers triaged on arrival
Every Honeycomb trigger 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.
Your queries become checks
Every saved query and board becomes a check: agents run it on a cadence and flag what doesn't look like normal for the service behind it.
Queried mid-investigation
Agents query your datasets while they work an issue: high-cardinality questions, answered and cited in the thread.
First-class in the graph
Honeycomb joins the context graph as a source, so a regression in a dataset lands next to the deploy and the resources behind it.
How to set up Honeycomb
- Choose an environment under Honeycomb Team Settings → API Keys and create its API key.
- Select the US or EU region in Praxen Inc. and enter the key. Connect each environment separately.
- Review alert delivery after connection: Praxen Inc. creates a webhook recipient named praxen and subscribes triggers to it.
Permissions and access
The product guide recommends a read key for investigation queries, but the integration also creates a recipient and updates triggers. The exact provider key capabilities for those provisioning operations are not enumerated in the checked connection form; verify them on Honeycomb rather than treating alert setup as a read-only operation.
Discovery, refresh and the connected view
Agents query datasets, inspect traces and check triggers. Recurring reconciliation keeps the praxen recipient on triggers. Terraform-managed triggers should include that recipient to avoid drift. Unlike Axiom, investigations use Honeycomb dataset queries and request traces rather than APL over event logs.
Disconnect and revoke access
Disconnect Honeycomb in Praxen Inc. and revoke the environment key. Disconnect removes the recipient from triggers; remove it from Terraform configuration at the same time.
Honeycomb tools.
The calls Praxen Inc. can make to Honeycomb when it looks into an issue.
Honeycomb -
honeycombApiCall any Honeycomb REST endpoint that lacks a dedicated tool -
honeycombRunQueryRun a query against a Honeycomb dataset -
honeycombDatasetsRead Honeycomb datasets and their columns -
honeycombTriggersRead or create Honeycomb triggers (alerts) -
honeycombBoardsRead or create Honeycomb boards (dashboards) -
honeycombSLOsRead or create Honeycomb Service Level Objectives (SLOs) -
honeycombMarkersList or create markers in a Honeycomb dataset
Common questions.
How do I connect Honeycomb to Praxen Inc.?
Choose an environment under Honeycomb Team Settings → API Keys and create its API key. Select the US or EU region in Praxen Inc. and enter the key. Connect each environment separately. Review alert delivery after connection: Praxen Inc. creates a webhook recipient named praxen and subscribes triggers to it.
What can Praxen Inc. read from Honeycomb?
Agents query datasets, inspect traces and check triggers. Recurring reconciliation keeps the praxen recipient on triggers. Terraform-managed triggers should include that recipient to avoid drift. Unlike Axiom, investigations use Honeycomb dataset queries and request traces rather than APL over event logs.