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

Make root cause analysis possible also for huge traces #131

Closed
mawHBT opened this issue Apr 27, 2022 · 1 comment
Closed

Make root cause analysis possible also for huge traces #131

mawHBT opened this issue Apr 27, 2022 · 1 comment
Labels
enhancement New feature or request

Comments

@mawHBT
Copy link
Collaborator

mawHBT commented Apr 27, 2022

What feature do you want to see added?

If onlyOneCallRecording is set, no rca is possible because no calltree can be generated. You can exclude very often called methods but you have to know which ones. Therefore maybe a parameter onlyCallCountRecording would help to get information which methods are called how often.
If traces are too big and you have to set onlyOneCallRecording, maybe generating only a reduced calltree would help also.

Upstream changes

No response

@mawHBT mawHBT added the enhancement New feature or request label Apr 27, 2022
@DaGeRe
Copy link
Contributor

DaGeRe commented Feb 16, 2023

Thanks for the issue, but this is a duplicate of #81, so I'll close this.

@DaGeRe DaGeRe closed this as completed Feb 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants