-
Notifications
You must be signed in to change notification settings - Fork 115
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
Capture CPU profiles in audit #1298
Comments
CPU profiles is the odd one out that takes a while to gather so we need to do something extra there over what the gather command handles today. We should also add the other profiles that we have now that audit isnt gathering natscli/cli/server_request_command.go Lines 230 to 235 in 09054dd
|
Good point. Would it be possible to have it opt in or some other mechanism to include other files in the audit where we could have them run a CPU profile in advance and save it to that directory? |
gather is already slow, I think its ok to make it a bit slower :) I think its useful by default to have this so we should just always grab it. Worse is forgetting and then needing it on a hard to reproduce issue |
Sounds good |
nats-io/jsm.go#639 also added a few others |
Proposed change
Please add CPU profile collection to audit when passing
--server-profiles
.Use case
CPU profile collection is often useful for diagnostics and would be worthwhile to collect when collecting the other profiles. CPU profile collection is available through
profilez
in 2.10.19+ and has been implemented innats server request profile cpu
.Contribution
No response
The text was updated successfully, but these errors were encountered: