Execution tracing

[einari]

We want to be able to trace execution paths - not as logging, but more concrete and useful. Every request that gets sent to the runtime (Commands, Queries) should be associated with a correlation ID automatically.

Every trace should include the GIT commit SHA of the source it represents. This way we would be able to navigate back to the code.

The things we want to record are typically something like:

• Command received (The command itself as metadata + the identifier of it)
• Authorization performed (Metadata could be the identity and claims)
• Validation performed (Metadata would be the AAI of the validation rules)
• Business rules performed (Metadata would be the AAI of the business rules)
• Event Source (Metadata would be AAI of the Event Source)
• Event(s) applied (Metadata would include the event itself + the AAI of it)
• Mediator
• Event Processors
• Bounded Contexts sent to

[einari]

Interesting thing here is to use something like Append Blobs in Azure for this - we should have a relative time from entry into a process that we add. This time can then be sorted out when we pull the blob out as a single entity in memory.