Supporting Multiple Input Sources

[adodge-bcg]

Issue:
With the current implementation, to add an additional source, a conversion from the sources payload to Teams and RocketChat is required. Each additional source will require new conversions for each Chat app supported. Ie. Splunk to Teams, Splunk to Rocket, Kabana to Teams, Kabana to Rocket. Not bad now, but each time you want to add a new source or destination there needs to be a conversion added for all the existing destinations/sources.

Proposal:
A generic alert object that all incoming objects are converted into, and that can be mapped to outgoing chat platforms. Therefore, each added source only needs to implement a conversion to the generic object, and each added destination only has to map the generic.

Faults:
This could prevent or interfere with the utilization of platform-specific features. Ie. Harder to support specific buttons for links in Teams while not requiring fields that other sources may not have or use.

[alexjoybc]

I would wait a bit on implementing this until we have a need for it. The reason being that unlike splunk we don't know exactly the requirement here and we might implement something that is dead code and not in use. what do you think @adodge-bcg ?