-
Notifications
You must be signed in to change notification settings - Fork 46
Make benchmark tool record multiple attribute record separately, Fixes AB#3429544 #2815
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
base: dev
Are you sure you want to change the base?
Conversation
|
❌ Work item link check failed. Description does not contain AB#{ID}. Click here to Learn more. |
|
✅ Work item link check complete. Description contains link AB#3429544 to an Azure Boards work item. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This pull request fixes a bug in the benchmark tool where only the first occurrence of duplicate status names was being recorded. The fix introduces logic to track and enumerate each occurrence separately (e.g., "status [1]", "status [2]"), enabling proper statistical analysis of repeated status events within spans.
- Refactored the
calculateStatisticsmethod to track occurrence indices for duplicate status names - Added enumeration to display names when multiple occurrences of the same status are detected
- Updated documentation to reflect the new duplicate-tracking behavior
...n4j/src/main/com/microsoft/identity/common/java/opentelemetry/DefaultBenchmarkSpanPrinter.kt
Outdated
Show resolved
Hide resolved
...n4j/src/main/com/microsoft/identity/common/java/opentelemetry/DefaultBenchmarkSpanPrinter.kt
Outdated
Show resolved
Hide resolved
…etry/DefaultBenchmarkSpanPrinter.kt Co-authored-by: Copilot <[email protected]>
145560b to
bc46512
Compare
AB#3429544
Previously, the tool would only record the first occurence of each attributes.