add template driven hook

[svrnm]

This introduces a template driven hook, so instead of writing a new one every time we want to quickly test something out, a template can be provided for the mapping

[cmiller-causely]

Have you tried this with the case of notifications being processed through the mediator?

[svrnm]

Have you tried this with the case of notifications being processed through the mediator?

No, I have not, since I was under the assumption that the mediator-based notifications are limited to what the UI provides (splunk, slack, alertmanager, teams, incident.io) and I was under the assumption that the executer-based approach is best for me to do rapid testing of targets we do not support yet. Or is there a way to handle that?

I mean, eventually it would be great to have a template-driven solution like that built into the UI directly, but I don't know if there is a wider need for that.

[cmiller-causely]

The intention was to use the mediator notification processing going forward. I added logic to support Causely bot as a type in the case that we want to support any other types going forward, and also to generally allow for more flexibility. For example, if someone wants to change the formatting of the notification, CauselyBot could be used to do this.
The API should support CauselyBot as a type. However, I am not sure what code changes are needed in CauselyBot. For example, there is filtering being done in the mediator. The same filtering is supported in CauselyBot, which is fine but redundant.

[svrnm]

Ah ok, then this option is not exposed via the UI, so I would need to configure that through an UI call?

Maybe we can make it visibile in the UI, and instead of calling it "CauselyBot" it's called "Generic" and we add some docs on how people can turn that into something (e.g. via causelybot, but also other solutions that are able to transform that)

[cmiller-causely]

Right, the UI is not exposing it, but it could be used via the API. Makes sense to add a generic option in the UI, as long as we add documentation on how to setup Causely bot - and maybe some info on the fact that CauselyBot must be setup before adding this type.

[svrnm]

I can manage the docs and the changes to the bot then. So if we can get this into the UI, that would be awesome :-)

Do we have a sense of how many existing customers use it, so in how far we need to be backward compatible?

[cmiller-causely]

I think @esara said there are 2, but I believe these 2 customers do not need CauselyBot going forward. They can use the existing built in support in the mediator.

[svrnm]

ok, so the first next step would be that we make the "CauselyBot" option (with a different name) available in the UI and then provide the docs for it. cc @byemini13 @akhandsi @vnikiten01

[cmiller-causely]

@svrnm I think this should be done via the api for now. We can add the UI later.

[svrnm]

@cmiller-causely start in the docs with API or just for my specific use cases right now?

[cmiller-causely]

I think it is OK to include the API in the docs, but maybe you should discuss with Ben.