Get notified when your data crosses critical thresholds.
Triggers let you receive notifications when your Honeycomb data crosses thresholds that you define. They help you detect issues, monitor system health, and respond quickly to anomalies before they impact users.
You can configure triggers on any graph generated by a Honeycomb query, giving you flexibility to reduce false positives caused by known errors.
Triggers let you define conditions on your data and automatically notify you when those conditions are met.
Each Trigger monitors data over a set duration and runs at a defined frequency.
For example, a trigger with a duration of 5 minutes and a frequency of 2 minutes will check the last 5 minutes of data every 2 minutes.
When a trigger fires, it alerts you via the configured method(s). Supported methods include:
Notifications include a direct link to the triggering graph, so you can see current status and quickly jump into investigation.
Tags help you stay organized as your Team creates more Triggers. Use them to group related Triggers by project, team, service, or any other category that fits your workflow.
Tags make it easier to filter and find the Triggers you need, especially in shared or busy environments. Because they’re flexible and customizable, you can organize Triggers in the way that works best for you.
By default, users have two triggers available across all environments. Upgrade to a Pro or Enterprise plan to increase your number of available Triggers.
Teams use Triggers for a variety of monitoring purposes:
| Use Case | Description |
|---|---|
| Lambda cost spikes | Detect sudden increases in usage or billing. Track the cost of Lambda queries and alert when they exceed a defined “normal” range. |
| Database connection limits | Prevent service interruptions. Determine your database connection limit, and alert when database connection counts approach or exceed that saturation threshold. |
| Kubernetes component status | Monitor Kubernetes components. For example, monitor pod startup failures or delays that indicate deployment or infrastructure issues. |
| High login activity | Identify unusual spikes in login attempts, helping identify security threats such as credential stuffing or brute-force attacks. Determine what qualifies as a high number of login attempts in your environment and alert when activity exceeds that threshold. |
| Internal operations check | Confirm that critical operations, like CronJobs, ran successfully. Alert if the operation is missing or failed. |
Create a trigger, define recipients, and activate a trigger using the Honeycomb UI.
Explore examples of trigger notifications, which you can use as inspiration for defining and configuring your own triggers.
