Add new opsgenie/opsgenie-incidents integration

sensu / catalog

Monitoring as code for Sensu Go. "There's a template for that!"

8 stars 4 forks source link

Add new opsgenie/opsgenie-incidents integration #96

Open calebhailey opened 2 years ago

calebhailey commented 2 years ago

TODO:

[X] Fork @nixwiz's OSS OpsGenie handler to the https://github.com/sensu org
[ ] Update the OpsGenie handler to sensu-plugin-sdk >= v0.16.x
[x] Init integration from template (see: https://github.com/sensu/catalog/blob/main/templates)
- [x] Add README.md
- [x] Add sensu-integration.yaml
- [x] Add CHANGELOG.md
[x] Add logo.png
[ ] Add sensu-resources.yaml
- [ ] opsgenie/opsgenie
- [ ] add a pipeline resource (example: pagerduty/pagerduty-incidents)
- [ ] move configured filters and mutators (if any) from handler(s) to the pipeline resource

amdprophet commented 2 years ago

The API tokens generated via the Opsgenie website do not appear to work with the nixwiz/sensu-opsgenie-handler plugin:

Error occurred with Status code: 403, Message: To perform this action, use an API key from an API integration.

amdprophet commented 2 years ago

I pushed up the WIP branch for this https://github.com/sensu/catalog/tree/jk/add/opsgenie/opsgenie-incidents. I'm waiting for the secrets work to be finished before opening a PR.

jspaleta commented 2 years ago

The API tokens generated via the Opsgenie website do not appear to work with the nixwiz/sensu-opsgenie-handler plugin:
Error occurred with Status code: 403, Message: To perform this action, use an API key from an API integration.

So I'm a little confused by this.

I just spun up an opsgenie trial and created the Sensu integration and obtained an API_KEY and it worked with the existing main branch for the forked repo. No code changes on my part.

We need to reach into there org and get the Sensu integration web tile they offer cleaned up a little but the api key did work for me.

jspaleta commented 2 years ago

Ok the PR is open: https://github.com/sensu/sensu-opsgenie-handler/pull/1

asachs01 commented 1 year ago

@portertech we've got a customer who's stuck using the old betorvs version of the handler and we'd like to get our fork published to Bonsai so that folks can use something that's being actively maintained.