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

Add log-level setting on Camel K operator #3053

Closed
christophd opened this issue Mar 1, 2022 · 3 comments
Closed

Add log-level setting on Camel K operator #3053

christophd opened this issue Mar 1, 2022 · 3 comments
Assignees
@phantomjinx
Labels
area/operator good first issue Does not require full understanding of the codebase kind/feature New feature or request

Comments

@christophd
Copy link
Contributor

Give users the opportunity to control the Camel K operator log verbosity via log level settings.

The setting should be added as kamel CLI option on the install command (e.g. --log-level | -v) and on the operator deployment (e.g. log-level) so users can adjust the log level on an already installed operator.

The logger framework supports V levels from 0-10. The log level setting on the operator should be logger framework agnostic so we might also consider to add abstractions like debug, info, error and translate those to logger framework specifics.
@squakez squakez added area/operator kind/feature New feature or request good first issue Does not require full understanding of the codebase labels Mar 1, 2022
@phantomjinx
Copy link
Contributor

Going to work on this.

phantomjinx added a commit to phantomjinx/camel-k that referenced this issue Mar 15, 2022
@phantomjinx
(apache#3053): Adds ability to modify the level of the operator logs
6437a9d 
* Exposes a switch --log-level (-v) at the CLI level allowing the operator
  to have its level of logging changed (info, debug, 0 ... 10)

* The switch translates to an env variable LOG_LEVEL which is included in
  the operator deployment. It is this env var that determines the internal
  level of the log.

* install.go
 * The CLI switch for setting the log-level

* operator.go
 * The setting of the log-level based on the env variable

* Adds debug logging for building the integration kits and integrations

* Wraps errors when building integration kits to identify more precisely
  where the error is occurring and the reason
phantomjinx added a commit to phantomjinx/camel-k that referenced this issue Apr 11, 2022
@phantomjinx
(apache#3053): Adds ability to modify the level of the operator logs
d2d24f7 
* Exposes a switch --log-level (-v) at the CLI level allowing the operator
  to have its level of logging changed (info, debug, 0 ... 10)

* The switch translates to an env variable LOG_LEVEL which is included in
  the operator deployment. It is this env var that determines the internal
  level of the log.

* install.go
 * The CLI switch for setting the log-level

* operator.go
 * The setting of the log-level based on the env variable

* Adds debug logging for building the integration kits and integrations

* Wraps errors when building integration kits to identify more precisely
  where the error is occurring and the reason
phantomjinx added a commit to phantomjinx/camel-k that referenced this issue Apr 11, 2022
@phantomjinx
(apache#3053): Adds ability to modify the level of the operator logs
c51ae1d 
* Exposes a switch --log-level (-v) at the CLI level allowing the operator
  to have its level of logging changed (info, debug, 0 ... 10)

* The switch translates to an env variable LOG_LEVEL which is included in
  the operator deployment. It is this env var that determines the internal
  level of the log.

* install.go
 * The CLI switch for setting the log-level

* operator.go
 * The setting of the log-level based on the env variable

* Adds debug logging for building the integration kits and integrations

* Wraps errors when building integration kits to identify more precisely
  where the error is occurring and the reason
phantomjinx added a commit to phantomjinx/camel-k that referenced this issue Apr 28, 2022
@phantomjinx
(apache#3053): Adds ability to modify the level of the operator logs
b0ddc92 
* Exposes a switch --log-level (-v) at the CLI level allowing the operator
  to have its level of logging changed (info, debug, 0 ... 10)

* The switch translates to an env variable LOG_LEVEL which is included in
  the operator deployment. It is this env var that determines the internal
  level of the log.

* install.go
 * The CLI switch for setting the log-level

* operator.go
 * The setting of the log-level based on the env variable

* Adds debug logging for building the integration kits and integrations

* Wraps errors when building integration kits to identify more precisely
  where the error is occurring and the reason
@phantomjinx
Copy link
Contributor

Fixed by #3245.

phantomjinx added a commit to phantomjinx/camel-k that referenced this issue Apr 29, 2022
@phantomjinx
(apache#3053): Adds ability to modify the level of the operator logs
8adc02c 
* Exposes a switch --log-level (-v) at the CLI level allowing the operator
  to have its level of logging changed (info, debug, 0 ... 10)

* The switch translates to an env variable LOG_LEVEL which is included in
  the operator deployment. It is this env var that determines the internal
  level of the log.

* install.go
 * The CLI switch for setting the log-level

* operator.go
 * The setting of the log-level based on the env variable

* Adds debug logging for building the integration kits and integrations

* Wraps errors when building integration kits to identify more precisely
  where the error is occurring and the reason
squakez pushed a commit that referenced this issue May 3, 2022
@phantomjinx @squakez
(#3053): Adds ability to modify the level of the operator logs
f7fdf35 
* Exposes a switch --log-level (-v) at the CLI level allowing the operator
  to have its level of logging changed (info, debug, 0 ... 10)

* The switch translates to an env variable LOG_LEVEL which is included in
  the operator deployment. It is this env var that determines the internal
  level of the log.

* install.go
 * The CLI switch for setting the log-level

* operator.go
 * The setting of the log-level based on the env variable

* Adds debug logging for building the integration kits and integrations

* Wraps errors when building integration kits to identify more precisely
  where the error is occurring and the reason
@phantomjinx
Copy link
Contributor

Fixed by #3245.

Please close.

@squakez squakez closed this as completed May 6, 2022
oscerd pushed a commit that referenced this issue May 16, 2022
@phantomjinx @oscerd
(#3053): Adds ability to modify the level of the operator logs
2204a74 
* Exposes a switch --log-level (-v) at the CLI level allowing the operator
  to have its level of logging changed (info, debug, 0 ... 10)

* The switch translates to an env variable LOG_LEVEL which is included in
  the operator deployment. It is this env var that determines the internal
  level of the log.

* install.go
 * The CLI switch for setting the log-level

* operator.go
 * The setting of the log-level based on the env variable

* Adds debug logging for building the integration kits and integrations

* Wraps errors when building integration kits to identify more precisely
  where the error is occurring and the reason
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@phantomjinx phantomjinx

Labels
area/operator good first issue Does not require full understanding of the codebase kind/feature New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@christophd @phantomjinx @squakez