search

alerta / alerta-contrib

Contributed integrations, plugins and custom webhooks
http://alerta.io
MIT License
119 stars 170 forks source link

Adding acking to OpsGenie #343

Closed lorddaren closed 3 years ago

lorddaren commented 3 years ago

There is currently a bug that this also addresses, which is that any status outside of ack, assign or closed would still cause the alert to be closed.

This now allows for capturing ack'ing of alerts from Alerta -> OpsGenie along with keeping the current capability of closing.

In addition there is the ability to not send along alerts that are Informational or Warning within Alerta. This can be used to not send alerts to OpsGenie but allow them to still show up on the dashboard.

satterly commented 3 years ago

👍

seasurfpete commented 3 years ago

@satterly I have been making some changes to the opsgenie integration for use at work. I've added the ability to do the following: Work behind a proxy - grab proxy address from http_proxy or app.config Translate alert severity of critical, major etc via dict to opsgenie severity's of P1, P2 etc and pass to opsgenie Ability to snooze alerts in opsgenie from shelving in alerta and set snooze time to timeout duation Ability to 'unsnooze' as alert in opsgenie - bit of a hack as its not an API call but can be done via ack/unack. ability to unack an alert in opsgenie via unack in alerta

I was trying to work out how I could get the previous alert state when change_state is called so i could add some logic here, any thoughts?

Is this something you are interested in having pushed up? If so I'll create a Pull Req. Ta