You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm forwarding opsgenie snooze action to our internal alertmanager. My flow looks like
user receives alert
press snooze action and sets time
oec got request for snooze and launches my script
my script creates request to alertmanager and got silence_id or error
I want to send that silence_id to opsgenie activity logs or an error if it happens.
Looks like there are way how to send an error to opsgenie but no way how to send success.
the only doubt is discardScriptResponse that set to true for that request. i've found no way how to change this to false
alternatives i considered
i can use notes to send success. But most of my users uses slack as notification channel and forwards all evens to it. So i will have two notifications for this one action.
One for alert being snoozed and one it was silenced.
Also i can use always exit code 1 and message. But that looks ugly and creates unnecessary complications
The text was updated successfully, but these errors were encountered:
freeseacher
changed the title
Send logs for success oec action
Send logs of success oec action to alert activity log
Jan 6, 2022
I'm forwarding opsgenie snooze action to our internal alertmanager. My flow looks like
I want to send that silence_id to
opsgenie activity logs
or an error if it happens.Looks like there are way how to send an error to opsgenie but no way how to send success.
the only doubt is
discardScriptResponse
that set totrue
for that request. i've found no way how to change this tofalse
i can use notes to send success. But most of my users uses slack as notification channel and forwards all evens to it. So i will have two notifications for this one action.
One for alert being snoozed and one it was silenced.
Also i can use always exit code 1 and message. But that looks ugly and creates unnecessary complications
The text was updated successfully, but these errors were encountered: