Update a trigger by specifying the trigger ID and the same fields used when creating a new trigger.
A Honeycomb Configuration Key is required to use this API. A Configuration Key can be found in the API Keys section of the environment configuration, which can be found under Environment Settings -> API Keys -> Configuration tab. Check out our documentation to find your API Keys.
More information can be found in Manage Environments.
The dataset slug or use __all__ for endpoints that support environment-wide operations.
The unique identifier (ID) of a Trigger.
A short, human-readable name for this Trigger, which will be displayed in the UI and when the trigger fires.
1 - 120A longer description, displayed on the Trigger's detail page.
1023A list of key-value pairs to help identify the Trigger.
10[{ "key": "team", "value": "blue" }]The threshold over which the trigger will fire, specified as both an operator and a value.
The interval in seconds in which to check the results of the query’s calculation against the threshold. Cannot be more than 4 times the query's duration (i.e. duration <= frequency*4). See A Caveat on Time for more information on specifying a query's duration. minimum: 60 maximum: 86400 multipleOf: 60 default: 900
How often to fire an alert when a trigger threshold is crossed.
on_change sends a trigger notification when the result of the specified calculation crosses the threshold.
The trigger resolves only when the result of the query no longer satisfies the threshold condition.on_true keeps sending a trigger notification at current frequency when and while the threshold is met.
(This reflects the same behavior as the "Send an alert every time a threshold is met" checkbox in the Honeycomb UI.)on_change, on_true If true, the trigger will not be evaluated and alerts will not be sent.
A list of Recipients to notify when the Trigger fires. Using type+target is deprecated. First, create the Recipient via the Recipients API, and then specify the ID.
The schedule type used by the trigger. The default is frequency, where the trigger runs at the specified frequency. The window type means that the trigger will run at the specified frequency, but only in the time window specified in the evaluation_schedule field.
frequency, window A schedule that determines when the trigger is run. When the time is within the scheduled window, the trigger will be run at the specified frequency. Outside of the window, the trigger will not be run.
Additional properties needed to configure this trigger with a dynamic baseline threshold.
{
"offset_minutes": 60,
"type": "percentage"
}A query ID or an inline query that is a strict subset of a Query Specification.
The ID of a Query that meets the criteria for being used as a Trigger, per above.
Success
The unique identifier (ID) for this Trigger.
The slug of the dataset this trigger belongs to. For environment-wide triggers, this will be "all".
A short, human-readable name for this Trigger, which will be displayed in the UI and when the trigger fires.
1 - 120A longer description, displayed on the Trigger's detail page.
1023A list of key-value pairs to help identify the Trigger.
10[{ "key": "team", "value": "blue" }]The threshold over which the trigger will fire, specified as both an operator and a value.
The interval in seconds in which to check the results of the query’s calculation against the threshold. Cannot be more than 4 times the query's duration (i.e. duration <= frequency*4). See A Caveat on Time for more information on specifying a query's duration. minimum: 60 maximum: 86400 multipleOf: 60 default: 900
How often to fire an alert when a trigger threshold is crossed.
on_change sends a trigger notification when the result of the specified calculation crosses the threshold.
The trigger resolves only when the result of the query no longer satisfies the threshold condition.on_true keeps sending a trigger notification at current frequency when and while the threshold is met.
(This reflects the same behavior as the "Send an alert every time a threshold is met" checkbox in the Honeycomb UI.)on_change, on_true If true, the trigger will not be evaluated and alerts will not be sent.
If true, the trigger has crossed its specified threshold without resolving.
A list of Recipients to notify when the Trigger fires. Using type+target is deprecated. First, create the Recipient via the Recipients API, and then specify the ID.
The schedule type used by the trigger. The default is frequency, where the trigger runs at the specified frequency. The window type means that the trigger will run at the specified frequency, but only in the time window specified in the evaluation_schedule field.
frequency, window A schedule that determines when the trigger is run. When the time is within the scheduled window, the trigger will be run at the specified frequency. Outside of the window, the trigger will not be run.
Additional properties needed to configure this trigger with a dynamic baseline threshold.
{
"offset_minutes": 60,
"type": "percentage"
}A query ID or an inline query that is a strict subset of a Query Specification.
The ID of a Query that meets the criteria for being used as a Trigger, per above.