-
Notifications
You must be signed in to change notification settings - Fork 845
feat: Config logging via helm #6312
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
Conversation
@@ -53,6 +53,10 @@ spec: | |||
value: '{{ .Values.security.kafka.ssl.client.endpointIdentificationAlgorithm }}' | |||
- name: SELDON_CORES_COUNT | |||
value: '{{ .Values.dataflow.cores }}' | |||
- name: SELDON_LOG_LEVEL_APP | |||
value: '{{ hasKey .Values.dataflow "logLevel" | ternary .Values.dataflow.logLevel .Values.logging.logLevel | upper }}' | |||
- name: SELDON_LOG_LEVEL_KAFKA |
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.
Was initially wondering whether we won't need a similar setup to the go one on the dataflow-engine side, but it appears that it knows how to take the same levels as syslog.
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
What this PR does / why we need it:
This PR introduces logging level configuration, exposed via helm.
Different components can set individual log levels or use a global setting in helm.
For the global setting, users should set
logging.logLevel
, possible values are: debug, info, error.If set on individual components, then the allowed levels depend on the underlying logging used for the component. Check docs for more information.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer: