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

By default the log viewer struggles when there are lots of entries #12644

Open
richard-cox opened this issue Nov 21, 2024 · 0 comments
Open

By default the log viewer struggles when there are lots of entries #12644

richard-cox opened this issue Nov 21, 2024 · 0 comments
Labels
kind/bug QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this
Milestone

Comments

@richard-cox
Copy link
Member

Setup

  • Rancher version: 2.10

Describe the bug

  • The performance of the pod / node / helm log viewer struggles when there are lots of entries
  • This is made worst if there are multiple outputs a second and the default Show the last of 30 mins is used
    • For examples a pod container log that outputs a couple of times a second which results in a LOT of entries over 30 mins

Suggestion, change the default show option to 10,000 (1000?) lines instead of 30 mins

To Reproduce

  • bring up a chatty pod
  • go to pod --> view logs

Result

  • performance of component degrades

Expected Result

  • performance is snappy

Screenshots
image

Additional context

@richard-cox richard-cox added this to the v2.12.0 milestone Nov 21, 2024
@github-actions github-actions bot added the QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this label Nov 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this
Projects
None yet
Development

No branches or pull requests

1 participant