OpsGenie alert and event related enhancements

[MattMofDoom]

Hi @nblumhardt,

This pull request adds functionality to Seq.App.OpsGenie:

• Priority can be specified in the instance config - P1 - P5 - allowing the app to raise alerts based on a specific priority
• Responders can be specified. Two formats accepted; comma-delimited team name, and comma-delimited "name=type" where type is one of team, user, escalation, or schedule). This allows the app to hook into OpsGenie team, scheduling, and escalation workflows
• Optionally specify an event property that contains an array or comma-delimited list of tags to allow OpsGenie tags to be dynamically built from the event; useful for passing through tags from apps such as https://github.com/MattMofDoom/Seq.App.EventTimeout
• Added debug logging for improved troubleshooting and traceability of alerts
• Logging of alert properties, which allows options such as sending the details of a failed OpsGenie alert via another app (example - Email+, Jira) attached to a signal watching for errors from the app or instance. Example - internet is down but an alternate alerting path exists, such as a DR email server
• convert enums to string during Json Serialization
• added OpsGenie icons to the package

Note - App name and assembly name were changed as part of build & test.

[MattMofDoom]

FYI - Test build can be installed from Nuget as Seq.App.Opsgenie2 .. the latest tested build version is 1.1.18.

[MattMofDoom]

🎉 this looks awesome, thanks @MattMofDoom!

I've added a stack of mostly-stylistic comments, to bring things in line with the rest of the codebase. LGTM otherwise :-)

Thanks @nblumhardt ... think it makes the app even more useful, and glad for an opportunity to contribute :-)

[MattMofDoom]

Hi @nblumhardt ,

Updated per your suggestions/nits and have reverted the versioning. I think the Serialize implementation in OpsGenieApiClient was what you had in mind - implemented an overload for passing either a list or an alert.

Checks are now passing :-)

Cheers,

Matt

[nblumhardt]

Merged! I'll keep an eye on CI/publishing.

Thanks @MattMofDoom - looking forward to hearing how it goes! 😎

[MattMofDoom]

Thanks @nblumhardt, I've already installed and tested - works great 😊

I no longer need to create OpsGenie rules to set priority or responders, and tags logged via Seq.App.EventTimeout are automatically added to the OpsGenie alert.

I will probably look at the idea for allowing mapping of @Level or a specified property to set Priority, and potentially allow passing through responders, as I noted in https://github.com/datalust/seq-tickets/issues/1221 ... obviously the intent being to make the alerting capabilities from this app even more powerful.

It may also be worth passing through properties such as a link to the signal and the event, if the instance is attached to a signal, but I'll have a think on that one.