Initialise DistributedTracingContext in AbstractActivity

[yinan-symphony]

Feature Request

DistributedTracingContext is initialised for the rest api request today, i would like to have the same traceability for the activities.

Description of Problem:

When BOT receives a message from DF, i'd like to the traceability as we do in the rest api.

Potential Solutions:

Initialise the DistributedTracingContext at the start point of the #processEvent.

... if you've considered alternatives, clearly and concisely describe those too.

[symphony-youri]

That makes sense, some points we can discuss:

• should we do that all the events in the datafeed loop and not only for the events processed for activities?
• is there a value from the event we could use to set the trace ID? or should we generate a new one randomly?

[yinan-symphony]

@symphony-youri yes, event better if we do it for all events, not only activities. well, a random value would be fine IMO (so no security concern then), just as what we have for rest requests. The idea is to ease the search by using this random value in the log file.

[symphony-youri]

Note for implementation: also check on the Agent side that if we have a trace id (or generate one) that we can correlate what happens on the agent side / bot side.

[thibauult]

+ trace (debug mode) DF events when dispatched to listeners. Also we might consider handling exceptions (see here) raised by the listener.

[thibauult]

Hi @yinan-symphony,

Pull request now opened https://github.com/finos/symphony-bdk-java/pull/489