Make log level configurable

[pavolloffay]

The log level is set as CMD argument. It would be helpful to expose it in the CRD e.g. in the observability spec

tempo-operator/apis/tempo/v1alpha1/tempostack_types.go

Line 122 in 754a9ad

type ObservabilitySpec struct {

[andreasgerstmayr]

Related PR to make it easier to change the log level for ad-hoc debug sessions using unmanaged mode: #550

[yuriolisa]

Guys, can I get this one?

[andreasgerstmayr]

Guys, can I get this one?

We have multiple components (operator, tempo, tempoQuery, tempoGateway, tempoGatewayOpa) - should we have one setting to change the log level for all components? One setting per component?

Currently you can switch the Tempo CR to Unmanaged mode, and edit the -log.level CLI argument of the deployment/statefulset you want to debug. imho this is an efficient way to debug the instance (e.g. you can also change the command of the pod, etc.), what do you think? Is an additional field in the CR required?

[yuriolisa]

@andreasgerstmayr, I believe we could keep both, the CLI parameters and add a new logLevel to the ObservabilitySpec which will work as a global loglevel as well.