Feature: Custom destination (call a program)

[zkarj735]

In addition to adding popular services and tools as destinations, it would be useful to enable a custom distribution provided by the user.

For example, we use BMC Control-M for job scheduling and currently generate alerts to this which are patched through to our incident system. It would be useful for Manzan to be able to generate these alerts, but Control-M may not warrant its own connector.

[jonnyz32]

Hi @zkarj735 , I'm not sure how feasible it would be for us to support custom destinations from a technical standpoint due to the amount of custom code possible needed for each destination.

However, some of our destinations are more about supporting a protocol and then the message using said protocol could be customized using our format options. In your example with Control-M, how do you normally communicate with it? If it's via http, it would be as simple as specifying the http endpoint and then specifying a few custom headers and formatting your message. If it's via some other protocol, we can discuss if it's something worth adding support for :)

[zkarj735]

There is a CTMSHOUT command which we use to generate an alert. This would need just a few configuration values.

We currently have this wrapped with an alerting framework we built that uses CTMSHOUT (and a few other destinations). The Control-M alerts are patched through to our incident management system with the ability to cause an automated callout if desired.

In considering whether Manzan has a place here, the ability to send these alerts would be a mandatory requirement.

[jonnyz32]

Got it, I understand now. I believe there is a way we can do this with the camel exec component, but will need to discuss more with the team to see how we want to handle this from a security perspective.