For proactive refresh log error to otel and change token source to IDP#4561
Conversation
|
Isn't this going to skew the cache hit ratio metrics resulting in potential customer concern for those who monitor this? Also, while there is a token refresh, the token returned to the user is not the one acquired to from the endpoint. Are we sure this is the right thing to change? |
Yes, I will be changing the token source back to cache, we should be using both token source and cache refresh reason when generating metrics. Thanks |
|
Hi @neha-bhargava - this has been opened for quite a while. Would you like the team to review again? |
…ProactiveRefreshTests.cs Co-authored-by: Peter <34331512+pmaytak@users.noreply.github.com>
Fixes #4492
Changes proposed in this request
Add telemetry for background request for proactive token refresh.
Log error to otel if the background process fails.
Added tags ApiId and IsProactiveRefresh to MsalFailure counter
Added tag CacheRefreshReason to histograms MsalTotalDuration, MsalDurationInL1CacheInUs, MsalDurationInL2Cache
Testing
Added unit tests and integration tests
Performance impact
Documentation