Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] OTel duration in L1 cache and duration creating POP tokens are badly computed #5036

Closed
bgavrilMS opened this issue Dec 31, 2024 · 1 comment · Fixed by #5035
Closed

Comments

@bgavrilMS
Copy link
Member

Library version used

4.64.0

.NET version

all

Scenario

ConfidentialClient - web site (AcquireTokenByAuthCode), ConfidentialClient - web api (AcquireTokenOnBehalfOf), ConfidentialClient - service to service (AcquireTokenForClient)

Is this a new or an existing app?

None

Issue description and reproduction steps

Measure duration is L1 cache or duration creating POP tokens. The values are wrong by a factor of 100 (e.g. should be 60000 microseconds, but MSAL only reports 600)

Relevant code snippets

No response

Expected behavior

No response

Identity provider

Microsoft Entra ID (Work and School accounts and Personal Microsoft accounts)

Regression

no

Solution and workarounds

No response

@bgavrilMS bgavrilMS added untriaged Do not delete. Needed for Automation needs attention Delete label after triage bug P2 confidential-client and removed untriaged Do not delete. Needed for Automation needs attention Delete label after triage labels Dec 31, 2024
@bgavrilMS bgavrilMS added this to the 4.67.0 milestone Dec 31, 2024
@bgavrilMS
Copy link
Member Author

CC @neha-bhargava for impact on telemetry

@bgavrilMS bgavrilMS linked a pull request Dec 31, 2024 that will close this issue
1 task
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant