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

Different Time range on GC activity and CPU load graphs #71

Open
tjanasiewicz opened this issue Dec 16, 2024 · 2 comments · May be fixed by #76
Open

Different Time range on GC activity and CPU load graphs #71

tjanasiewicz opened this issue Dec 16, 2024 · 2 comments · May be fixed by #76
Assignees
Labels
bug Something isn't working

Comments

@tjanasiewicz
Copy link
Collaborator

Describe the bug
Different Time range on GC activity and CPU load graphs

To Reproduce
Steps to reproduce the behavior:
Unknown

Expected behavior
The same time range should be shown on both graphs

Screenshots
If applicable, add screenshots to help explain your problem.

And example:
image

@tjanasiewicz tjanasiewicz added the bug Something isn't working label Dec 16, 2024
@tjanasiewicz tjanasiewicz self-assigned this Dec 16, 2024
@tjanasiewicz
Copy link
Collaborator Author

There is a chance that this issue is observed when the input data are invalid, but still, the range should be the same, and should consider the first and last javacores collection time.

@PiotrAniola82 any comments?

@PiotrAniola82
Copy link
Collaborator

CPU chart looks correct.
GC chart should not be displayed if there is no verboseGC data.
If there are no verbose GC logs in the input, there should be a message: "No verbosegc logs"
If there are verbose GC logs, but no collections in the javacore time limits, there should be a message "No GC activity was detected within the javacore time limits"

kkazmierczyk added a commit that referenced this issue Dec 20, 2024
Signed-off-by: Krzysztof Kaźmierczyk <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants