Affected component
Duende.AccessTokenManagement
Version
Duende.AccessTokenManagement 4.2.0
Describe the bug
Structured logs have a mismatch of variable name used in log string and the one set by the logger
Caching access token for client: iqars-client. Expiration: {Expiration}
Log shows Expiration but code sets CacheDuration.
|
state.TagArray[2] = new("{OriginalFormat}", "Caching access token for client: {ClientName}. Expiration: {Expiration}"); |
|
state.TagArray[1] = new("ClientName", clientName.ToString()); |
|
state.TagArray[0] = new("CacheDuration", cacheDuration); |
It causes an ugly red markings in structured tools like seqlog
Steps to reproduce
- Set up structural logging with Seq (or any logger, even console should do)
- Set up Duende.AccessTokenManagement
- Use the http client
Expected behavior
Expiraition being correctly logged in both log message and structured log as property.
Additional context
No response
Affected component
Duende.AccessTokenManagement
Version
Duende.AccessTokenManagement 4.2.0
Describe the bug
Structured logs have a mismatch of variable name used in log string and the one set by the logger
Log shows
Expirationbut code setsCacheDuration.foss/access-token-management/src/AccessTokenManagement/Internal/Generated/Microsoft.Gen.Logging/Microsoft.Gen.Logging.LoggingGenerator/Logging.cs
Lines 920 to 922 in 47a6081
It causes an ugly red markings in structured tools like seqlog
Steps to reproduce
Expected behavior
Expiraition being correctly logged in both log message and structured log as property.
Additional context
No response