All integrationsMonitoring
Honeycomb
Send events and deploy markers to Honeycomb, run queries, and manage triggers.
- actions
- 20
- triggers
- 5
Triggers
Start a workflow when something happens in Honeycomb.
- New markerRuns when a marker is added in Honeycomb, such as a deploy. Markers already there when the workflow is turned on don't start it.
- New datasetRuns when a dataset appears in your environment, such as when a new service starts sending events.
- Dataset stopped receiving eventsRuns when a dataset has received no events for a while, such as a service that stopped sending telemetry. Datasets already quiet when the workflow is turned on don't start it until they come back and go quiet again.
- Trigger firedRuns when a Honeycomb trigger crosses its threshold, such as too many errors, and again each time it fires after recovering.
- Burn alert firedRuns when an SLO burn alert fires because the SLO's error budget is running down, and again each time it fires after recovering. Needs Honeycomb Pro or Enterprise.
Actions
Steps a workflow can run in Honeycomb.
- Send eventSend one event to a dataset, such as a job that finished with its duration. A new dataset name creates the dataset.
- Send eventsSend a list of events to a dataset in one go, such as rows from an earlier step. Fails, naming each event, if Honeycomb refuses any.
- Create markerMark a moment on Honeycomb's graphs, such as a deploy or an incident, so changes in the data can be traced to it.
- List markersList a dataset's markers, newest first.
- Update markerChange a marker's message, type, link or times, such as adding the end of a deploy. Fields left blank keep what the marker has.
- Delete markerDelete a marker from a dataset.
- List datasetsList the datasets in your environment, with when each last received an event.
- Get datasetGet one dataset: its description, how many fields it has and when it last received an event.
- List fieldsList the fields in a dataset's events, with each one's type and when an event last carried it.
- Run queryCount or calculate over a dataset's events, such as the 99th percentile of duration_ms by service in the last hour, and get the results. Needs Honeycomb Enterprise.
- List triggersList the Honeycomb triggers (alerts) on a dataset, and whether each is firing.
- Get triggerGet one Honeycomb trigger: its query, threshold, schedule, who it notifies and whether it is firing.
- Create triggerCreate a Honeycomb trigger that checks a calculation on a schedule and alerts when it crosses a threshold, such as more than 100 server errors in 15 minutes.
- Update triggerChange a Honeycomb trigger's name, threshold, schedule or who it notifies, or turn it off or on. Fields left blank stay as they are.
- Delete triggerDelete a Honeycomb trigger, so it no longer checks or alerts.
- List SLOsList the service level objectives (SLOs) on a dataset. Needs Honeycomb Pro or Enterprise.
- Get SLOGet one SLO, optionally with its status, error budget left and compliance (Honeycomb Enterprise).
- List burn alertsList an SLO's burn alerts, which warn when its error budget runs down, and whether each is firing.
- List boardsList the boards in your environment, with a link to each.
- List recipientsList where Honeycomb can send alerts: email addresses, Slack channels, PagerDuty and webhooks. Secrets are hidden.
No actions match that.
Automate Honeycomb with Lodol.
Connect Honeycomb, then hand Lodol the job in Slack, Claude or ChatGPT.
We’re letting people in a few at a time.