-
-
Notifications
You must be signed in to change notification settings - Fork 4.3k
feat(trace-eap-waterfall): Cleaning up trace context sections #90091
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: master
Are you sure you want to change the base?
Conversation
Abdkhan14
commented
Apr 22, 2025
- Only rendering contexts when we have data to populate them with.
- Disabled collapse persistence for the context sections.
key="logs" | ||
type={TraceContextSectionKeys.LOGS} | ||
<FoldSection | ||
sectionKey={TraceContextSectionKeys.LOGS as string as SectionKey} |
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.
Should we be adding these to SectionKey
? I noticed there were a few more keys in the PR that were being forced to SectionKey
const hasProfiles = tree.type === 'trace' && tree.profiled_events.size > 0; | ||
const hasLogs = logs && logs?.length > 0; | ||
const hasTags = | ||
rootEvent.data && | ||
rootEvent.data.tags.length > 0 && | ||
!(tree.type === 'empty' && hasLogs); // We don't show tags for only logs trace views |
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.
nit: might be useful to break this out into a shareable function. Looks like the same logic is being used somewhere else in this pr too