TraceId is not set to Correlation ID about correlationid HOT 3 CLOSED

Having a bit more of a look it seems that the RequestId in the logged scope is retrieved from the HttpContext.TraceIdentifier property, not sure where the logged TraceId value comes from.

Regardless, neither value is what was set by the CorrelationId middleware.

from correlationid.

The TraceId set in the logging scope above is coming fro the current Activity.

There are quite a lot of considerations around messing with the Activity directly and I currently feel that adjusting that should be a decision in user code. I may revisit that but right now I'm unconvinced. Activities support the concept of correlation of requests and logs and provide a richer, standards-compliant approach. I feel that CorrelationID and Activity should remain distinct. Correlation ID is a simpler library which can be used in place of or alongside Activities.

from correlationid.

Same issue here. The "TraceId" I see in my log output is unchanged despite options.UpdateTraceIdentifier = true. If you AddToLoggingScope = true it shows up in the logs. Hope this helps someone.

from correlationid.