We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Is your feature request related to a problem? Please describe. The Cockroach cockroach.log is too verbose and hard to make diagnosis.
cockroach.log
Describe the solution you'd like Have there be two log files:
Describe alternatives you've considered Alternative would be to have a tool to parse and decipher the verbose log file.... for example:
crdblog -events -timeframe 1w crdblog -errors -timeframe 1m crdblog -alerts -timeframe 1m crdblog -verbose -timeframe 1w
Additional context This was requested by a customer but would be useful for all.
The text was updated successfully, but these errors were encountered:
Have you looked at cockroach.stderr.log? To some degree this does this already and could be enhanced.
cockroach.stderr.log
Sorry, something went wrong.
Fixed by #57134 (and can be further exploited with a network log collector when #57170 is merged)
No branches or pull requests
Is your feature request related to a problem? Please describe.
The Cockroach
cockroach.log
is too verbose and hard to make diagnosis.Describe the solution you'd like
Have there be two log files:
Describe alternatives you've considered
Alternative would be to have a tool to parse and decipher the verbose log file.... for example:
crdblog -events -timeframe 1w
crdblog -errors -timeframe 1m
crdblog -alerts -timeframe 1m
crdblog -verbose -timeframe 1w
Additional context
This was requested by a customer but would be useful for all.
The text was updated successfully, but these errors were encountered: