Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Declarative log level #2314

Open
rzetelskik opened this issue Jan 10, 2025 · 1 comment
Open

Declarative log level #2314

rzetelskik opened this issue Jan 10, 2025 · 1 comment
Labels
good-first-issue Issue that is good as an onboarding task for newcomers kind/feature Categorizes issue or PR as related to a new feature. lifecycle/from-migration Indicates that this issue is a copy of a corresponding issue mentioned in the description. priority/backlog Higher priority than priority/awaiting-more-evidence. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@rzetelskik
Copy link
Member

What should the feature do?

Loglevel of particular components should be configurable through ScyllaOperatorConfig.

What is the use case behind this feature?

Allows for finer granularity and is a step towards having a centralised config.

Anything else we need to know?

For backwards compatibility, the flag provided to the binary should take precedence.

Duplicate of #836.

/lifecycle frozen
/priority important-soon
@rzetelskik rzetelskik added the kind/feature Categorizes issue or PR as related to a new feature. label Jan 10, 2025
@scylla-operator-bot scylla-operator-bot bot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Jan 10, 2025
@rzetelskik rzetelskik mentioned this issue Jan 10, 2025
Merged
@mflendrich mflendrich added triage/accepted Indicates an issue or PR is ready to be actively worked on. priority/backlog Higher priority than priority/awaiting-more-evidence. lifecycle/from-migration Indicates that this issue is a copy of a corresponding issue mentioned in the description. and removed priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. labels Feb 11, 2025
@mflendrich mflendrich marked this as a duplicate of #2449 Feb 11, 2025
@mflendrich mflendrich added the good-first-issue Issue that is good as an onboarding task for newcomers label Feb 11, 2025
@mflendrich mflendrich marked this as a duplicate of #2374 Feb 11, 2025
@mflendrich mflendrich changed the title Make loglevel configurable in ScyllaOperatorConfig Declarative log level Feb 11, 2025
@mflendrich
Copy link
Collaborator

Merged issues for scylla cluster loglevel & operator machinery loglevel into one.

From the user perspective, having a consistent loglevel experience justifies handling this holistically. Maybe the loglevel setting can/should be hierarchical - to be decided when implementing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
good-first-issue Issue that is good as an onboarding task for newcomers kind/feature Categorizes issue or PR as related to a new feature. lifecycle/from-migration Indicates that this issue is a copy of a corresponding issue mentioned in the description. priority/backlog Higher priority than priority/awaiting-more-evidence. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mflendrich @rzetelskik