Idea: add "trigger type" to webhook

Feedback
1

I’ve looked through the options for sieve and sieve_data, but don’t see anything pertaining to what triggered the monitor. Would you consider adding the ability to send the trigger type to a webhook? The way I see it, there are at least 3 different ways a notification can be triggered: from a scheduled trigger, manually, or from a retry after an error. There could be more, and you could possibly split off the retry as a separate value, so it might be something like "trigger": "scheduled" and "isRetry": true. Either way, it would be helpful to be able to have this information in the webhook.

For example, one might want to filter out manual triggers that happen during a certain time, or may want to log if a particular monitor is needing to retry.

Thanks!
Micah

2

the module that triggers actions doesn’t know how the change was detected - it only knows that a change was detected and that it needs to trigger the actions.

if you need the log, api is a better way to get the data.