Skills: Traceability of messages

[carlosscastro]

Currently there is no way of knowing the app id that originated the message in a skills scenario. The goal of this issue is to design a coherent action plan for supporting of traceability of messages. Even though most of our infrastructure is designed for host - skill pairs, ideally the design should not block longer call chains (with more than 2 bots) from being implemented in the future.

Currently we overwrite the From field with the direct neighbor, so callees do not receive message origin information. For example, if we have Skill -> VA - > Channel, the channel receives VA in the from field. That opens the door for potential debuggability issues, and knowing the originator ( and potentially call chain if we implemented longer chains in the future) could be useful for traceability, debuggability and other scenarios.

[gabog]

Hi @carlosscastro / @dandriscoll , I think this would be useful for traceability, any thoughts on where in the payload we can put this based on the current OBI spec?

Thanks

[dandriscoll]

The callerId field is used to represent VA, can't the from field be the original user? The intent was to have state switching take callerId into account and have from reflect the original user, including their user ID and channel ID so none of that logic has to change.

[carlosscastro]

@gabog @dandriscoll Organizing a call for this. The ideal outputof the call is to get enough consensus to write a detailed DCR that can translate to implementation without further unknowns.

[carlosscastro]

Also changed the title to reflect the need rather than to reflect a possible technical approach.