DarthVader
Reputation: 55032
How is HttpContext TraceIdentifier generated in .NET Core?
How is HttpContext TraceIdentifier (aka Correlation-Id) generated?
I request a page through controller which gives me the following TraceId:
0HLEACIU86PT6:0000000D
The page fires an ajax call which has the following TraceId:
0HLEACIU86PT7:00000005
As you can see, they are very similar. Is it based on time?
Why didn't I get the same TraceIdentifier?
How can I ensure the same TraceIdentifier?
Upvotes: 34
Views: 26585
Answers (2)
davidfowl
Reputation: 38784
Kestrel generates the request ID as {ConnectionId}:{Request number}. The connection id is the base32 encoded version of a long using the alphabet 1-9, and A - V. The request count is the number of requests over that connection. The nth request over a specific connection is {ConnectionId}:{n}
Upvotes: 58
Related Questions
- Difference between HttpContext.TraceIdentifier and Activity.Current.Id
- Does .NET Core HttpClient have the concept of interceptors?
- How does HttpContext.Current.User.Identity.Name know which usernames exist?
- How does HttpContext property work in ASP.NET Core?
- Why is traceid sent in automatic 400 responses in ASP.NET Core 2.2
- HttpContext.TraceIdentifier is always same (and a Guid)
- HttpContext Header
- How to implement HttpContext in .net core 2.0?
- How do you use 'HttpContext' class?
- How HttpContext works in .NET