-
-
Notifications
You must be signed in to change notification settings - Fork 5.7k
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
Add PProf to admin pages and to gitea manager
#22742
Conversation
The PProf endpoint is too difficult for many users to use - this PR will attempt to create a nicer UI to help in the collection PProf data from Gitea. Signed-off-by: Andrew Thornton <art27@cantab.net>
Codecov Report
📣 This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more @@ Coverage Diff @@
## main #22742 +/- ##
=======================================
Coverage ? 47.21%
=======================================
Files ? 1113
Lines ? 149657
Branches ? 0
=======================================
Hits ? 70658
Misses ? 70617
Partials ? 8382
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
{{.locale.Tr "admin.monitor.stacktrace.download_stacktrace"}} | ||
</div> | ||
{{template "base/delete_modal_actions" .}} | ||
<div class="hide" id="stacktrace-to-download"> |
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.
Why not just:
- User click the download button
- Download from a HTTP URL directly
?
Then no need that complex dialog nor the JS code
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. Then they get a different stacktrace.
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.
I mean , could there be no stacktrace on the UI? Just some links to help to collect problems.
The complex UI doesn't help users. As an end user, they should just download and report the stacktrace file.
The end users could do nothing even if they see the stacktrace on the UI.....
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.
FYI, when I was using GitLab, they have an all-in-one tool. It collects everything into a file, and what I need to do is just using the tool and sending the generated file to them, then they can help to resolve problems.
Making the diagnosis system too complex doesn't benefit end users IMO.
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.
I mean , could there be no stacktrace on the UI? Just some links to help to collect problems.
I'm going to add a direct download stacktrace profile below to get the stacktraces without seeing them.
The complex UI doesn't help users. As an end user, they should just download and report the stacktrace file.
The pretty stacktrace helps me and SEVERAL bugs have been solved using it. It has helped me a large number of times already.
The end users could do nothing even if they see the stacktrace on the UI.....
Not every user is incapable and whilst the purpose of this UI is to help us to help users we should enable users and developers to help themselves. A pretty UI can be helpful for us to solve issues in a way that the opaque stacktrace format is not.
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.
I mean , could there be no stacktrace on the UI? Just some links to help to collect problems.
I'm going to add a direct download stacktrace profile below to get the stacktraces without seeing them.
If it means more complex, then it's not necessary IMO. My initial idea is about keeping the system simple but complete and useful.
While I do not think keeping the downloaded stacktrace file exactly the same as the UI list is meaningful -- everytime you refresh the page, you get a different stacktrace ..... Even if they are different, they are all helpful for resolving problem equally, and maybe sometimes the UI shown list is not helpful but the downloaded is helpful in case the downloaded one catches the problem, everything is possible.
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.
Fundamentally it's really important to be able to download the stacktrace that you have seen. Given these are dynamic it's possible that you may actually only see the issue on the stacktrace that you have and if you try get another the issue will be gone.
We need the download.
FYI, when I was using GitLab, they have an all-in-one tool. It collects everything into a file, and what I need to do is just using the tool and sending the generated file to them, then they can help to resolve problems.
Making the diagnosis system too complex doesn't benefit end users IMO.
If I knew what we generally needed I would do that - but in general we don't need cpu-profiles etc.
We do need a way of reading the logs and I will get to that but ... let's get general routes in and then we can have pared back routes to get the common things. Right now we have no easy way of getting pprof profiles from users and that fundamentally limits our ability to use them for diagnostics. This PR makes that a hell of a lot easier.
Signed-off-by: Andrew Thornton <art27@cantab.net>
Signed-off-by: Andrew Thornton <art27@cantab.net>
Signed-off-by: Andrew Thornton <art27@cantab.net>
Signed-off-by: Andrew Thornton <art27@cantab.net>
gitea manager
Signed-off-by: Andrew Thornton <art27@cantab.net>
Signed-off-by: Andrew Thornton <art27@cantab.net>
Signed-off-by: Andrew Thornton <art27@cantab.net>
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.
Hmm, I hope it is by design that the vast majority of generated reports is absolutely unreadable?
Perhaps we should add a "warning" at the top of the section stating something like Many of the generated files won't be understandable for you. Don't worry, the only thing that matters is that WE understand it.
(Hopefully you find a better wording 😅)
Signed-off-by: Andrew Thornton <art27@cantab.net>
Signed-off-by: Andrew Thornton <art27@cantab.net>
Signed-off-by: Andrew Thornton <art27@cantab.net>
Signed-off-by: Andrew Thornton <art27@cantab.net>
Signed-off-by: Andrew Thornton <art27@cantab.net>
Signed-off-by: Andrew Thornton <art27@cantab.net>
Signed-off-by: Andrew Thornton <art27@cantab.net>
Signed-off-by: Andrew Thornton <art27@cantab.net>
Any UI screenshots? |
I think this has been replaced by #24636 ? |
Maybe additional |
The PProf endpoint is too difficult for many users to use - this PR will attempt to create a nicer UI to help in the collection PProf data from Gitea. It also adds pprof endpoints to the gitea manager command.
Signed-off-by: Andrew Thornton art27@cantab.net