profiler: log when profiler is stopped #1433
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This is mainly motivated by a support case where the user did profiler.Start(...) profiler.Stop() instead of profiler.Start(...) defer profiler.Stop() and wasn't getting any profiles. Explicitly logging when the profiler is stopped makes that easier to catch. Only log if startup logging is also enabled to avoid log spam.
pmbauer
approved these changes
Aug 30, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is mainly motivated by a support case where the user did
instead of
and wasn't getting any profiles. Explicitly logging when the profiler is
stopped makes that easier to catch. Only log if startup logging is also
enabled to avoid log spam.