-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[APM] Increase Logstream height #85913
[APM] Increase Logstream height #85913
Conversation
Increasing the component height for more optimal viewing experience.
Pinging @elastic/apm-ui (Team:apm) |
@@ -135,6 +135,7 @@ function LogsTabContent({ transaction }: { transaction: Transaction }) { | |||
startTimestamp={startTimestamp - framePaddingMs} | |||
endTimestamp={endTimestamp + framePaddingMs} | |||
query={`trace.id:"${transaction.trace.id}" OR "${transaction.trace.id}"`} | |||
height={640} |
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.
Any reason for that specific size? Is it relative to other containers or does that number just work well?
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.
400 is too slim for space we typically have in this panel, and it's divisible by 8 😊 Do you think it's too tall?
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.
No it's fine. Just curious. Feel free to merge when green.
@elasticmachine merge upstream |
💚 Build SucceededMetrics [docs]Async chunks
Distributable file count
History
To update your PR or re-run it, just comment with: |
Summary
Increasing the component height from
400px
to640px
for more optimal viewing experience.Before
After
Checklist
Delete any items that are not applicable to this PR.
Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n supportDocumentation was added for features that require explanation or tutorialsUnit or functional tests were updated or added to match the most common scenariosAny UI touched in this PR is usable by keyboard only (learn more about keyboard accessibility)Any UI touched in this PR does not create any new axe failures (run axe in browser: FF, Chrome)This renders correctly on smaller devices using a responsive layout. (You can test this in your browser)This was checked for cross-browser compatibilityFor maintainers
This was checked for breaking API changes and was labeled appropriately