-
Notifications
You must be signed in to change notification settings - Fork 137
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add opsgenie provider #252
Conversation
5f77722
to
ee97014
Compare
5f0336a
to
8feeefc
Compare
7ab448d
to
37de0d0
Compare
05cd5da
to
0709697
Compare
Interesting this is failing. I was debating whether I need to check-in the output of |
0709697
to
24fddbe
Compare
You need to run |
There are no changes to the API docs when running that command, the build was failing because of a diff in the CRD docs. If I run The current commit should be all that's required to make the build pass. |
24fddbe
to
0a3d67e
Compare
Signed-off-by: Alan Hollis <[email protected]>
0a3d67e
to
cbe52b5
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Thanks @Alan01252 🏅
This pull request adds opsgenie as a provider and allows extra metadata to be configured against an alert.
This is useful when you're running multiple clusters and want to distinguish where the alert has come from ( for example dev/staging/prod environments )
Opsgenie has been added as a receiver and this has been tested locally.
Opsgenie makes use of the extra metadata in order to route requests to appropriate slack channels etc.