We're using ASP.NET Web API and Azure Service Bus and adding logging to our disparate services and systems. We need to track a correlation ID to the headers of each set of bus messages as well as logs related to a single business workflow/sequence together together. I'm just trying to nail down what this should be called. So basically it ties together the logs of a single business process hitting multiple servers. The originator of the specifications used "EventID". In past projects I've seen "RequestId", "SessionId", "ContextId", and I suppose we could also use "WorkflowId", "ActivityId", "CorrelationId", etc.
More specifically, since this would otherwise be a completely subjective call, is there any known and published industry standard that calls out a convention for what to call this thing?
My question comes from ignorance about ESB convention and thought perhaps there is a conventional header name used for this purpose.