-
Notifications
You must be signed in to change notification settings - Fork 475
Fix unit length search #8627
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
Fix unit length search #8627
Conversation
|
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 Summary: Fix unit length search
- Backend Parser Updates: Updated
listener.goto convert time-related keys to the correct units (Durationto ns,Lengthto ms,ActiveLengthto ms, default to ns). RenamedtraceAttributeKeytoextendedAttributeKeyfor clarity. - Unit Tests: Added new test cases in
listener_test.goto ensure correct unit conversions for time-related keys. - Frontend Graphing Component: Introduced a default time metric and updated the
getTickFormatterfunction inGraph.tsxto ensure accurate time-based data representation.
Notes:
- Ensure that all time-related searches and graph representations are consistent with the new unit conversions to avoid discrepancies.
ccschmitz
left a comment
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.
Summary
Some time related keys have different units. Fix the search to convert to the correct unit:
Open question: what is a session's duration and what is its units?
https://www.loom.com/share/f66d69ae0df544f5bb70dcf1a0b8c30a
How did you test this change?
Are there any deployment considerations?
N/A
Does this work require review from our design team?
N/A