-
Notifications
You must be signed in to change notification settings - Fork 553
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
verbose_logging_timeout_sec_max #15798
Conversation
Added option to v1/loggers to provide the log levels in addition to the names of the loggers. Use v1/loggers?include-levels=true Signed-off-by: Michael Boquard <michael@redpanda.com> Signed-off-by: Oren Leiman <oren.leiman@redpanda.com>
ducktape was retried in https://buildkite.com/redpanda/redpanda/builds/43112#018c8628-5a3e-4b3c-8840-b1dffe1713f0 |
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.
looks fantastic, just a couple of notes
CI Failures: |
Added message to set_log_level response that reports previous level of the logger. Signed-off-by: Michael Boquard <michael@redpanda.com> Signed-off-by: Oren Leiman <oren.leiman@redpanda.com>
Signed-off-by: Michael Boquard <michael@redpanda.com> Signed-off-by: Oren Leiman <oren.leiman@redpanda.com>
f5f888f
to
df50d3b
Compare
force push contents:
|
/ci-repeat 5 |
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.
couple more questions but looks great!
Max duration for TRACE or DEBUG level logging. If null (default) we impose no limit. Signed-off-by: Oren Leiman <oren.leiman@redpanda.com>
Allows setting an expiration that exceeds `verbose_logging_timeout_max`. Signed-off-by: Oren Leiman <oren.leiman@redpanda.com>
- Adds get_log_level - Improve set_log_level - Allows setting expiration=0 - Adds force query parameter Signed-off-by: Oren Leiman <oren.leiman@redpanda.com>
df50d3b
to
3816a0f
Compare
force push for better |
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.
lgtm
This allows us to keep the default level for each logger around in the level reset map and distinguish between loggers with expiring settings and those without when the log reset timer fires. Signed-off-by: Oren Leiman <oren.leiman@redpanda.com>
- Clamps timeouts to node config - inclusive of 0-valued setting (no timeout) - Respects force query param to override configured max - Log the timeout (after clamping) at INFO level Signed-off-by: Oren Leiman <oren.leiman@redpanda.com>
Signed-off-by: Oren Leiman <oren.leiman@redpanda.com>
3816a0f
to
4d4c975
Compare
force push condition |
/backport v23.3.x |
/backport v23.2.x |
/backport v23.1.x |
Oops! Something went wrong. |
Failed to create a backport PR to v23.2.x branch. I tried:
|
Failed to create a backport PR to v23.1.x branch. I tried:
|
This PR introduces
verbose_logging_timeout_sec_max
, which, if set, causes expiration times included in set_log_level requests to be clamped before timeouts are calculated.Includes an assortment of minor improvements to the logic around setting log levels and managing timeouts around those settings.
Fixes https://github.com/redpanda-data/core-internal/issues/938
Fixes https://github.com/redpanda-data/core-internal/issues/931
Fixes https://github.com/redpanda-data/core-internal/issues/930
Backports Required
Release Notes
Improvements
verbose_logging_timeout_max
node config, to prevent setting TRACE and DEBUG log level indefinitely