GitHub user dosubot[bot] added a comment to the discussion: Superset → PostgreSQL: recurring SSL EOF and connection reset logs
<!-- Answer --> You can change the Superset log level in your Helm chart by setting the SUPERSET_LOG_LEVEL environment variable using the extraEnv field in your values.yaml. For example: ```yaml extraEnv: SUPERSET_LOG_LEVEL: "debug" ``` This will set the log level for all Superset pods, and logs will go to stdout/stderr by default in Kubernetes deployments. This method works whether or not Celery is enabled. For more advanced logging customization, you can use the configOverrides field to append Python logging config to superset_config.py, but for most cases, setting the environment variable is sufficient. [Reference](https://github.com/apache/superset/blob/master/helm/superset/values.yaml) <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/f675d097-9db6-4acb-98f1-8f9246ce2840?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/f675d097-9db6-4acb-98f1-8f9246ce2840?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/f675d097-9db6-4acb-98f1-8f9246ce2840?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/f675d097-9db6-4acb-98f1-8f9246ce2840?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/f675d097-9db6-4acb-98f1-8f9246ce2840?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/f675d097-9db6-4acb-98f1-8f9246ce2840?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/f675d097-9db6-4acb-98f1-8f9246ce2840?feedback_type=other)</sup> [](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=github) [](https://cursor.com/link/prompt?text=You%20can%20change%20the%20Superset%20log%20level%20in%20your%20Helm%20chart%20by%20setting%20the%20SUPERSET_LOG_LEVEL%20environment%20variable%20using%20the%20extraEnv%20field%20in%20your%20values.yaml.%20For%20example%3A%0A%0A%60%60%60yaml%0AextraEnv%3A%0A%20%20SUPERSET_LOG_LEVEL%3A%20%22debug%22%0A%60%60%60%0A%0AThis%20will%20set%20the%20log%20level%20for%20all%20Superset%20pods%2C%20and%20logs%20will%20go%20to%20stdout/stderr%20by%20default%20in%20Kubernetes%20deployments.%20This%20method%20works%20whether%20or%20not%20Celery%20is%20enabled.%20For%20more%20advanced%20logging%20customization%2C%20you%20can%20use%20the%20configOverrides%20field%20to%20append%20Python%20logging%20config%20to%20superset_config.py%2C%20but%20for%20most%20cases%2C%20set ting%20the%20environment%20variable%20is%20sufficient.%20%20%0A%5BReference%5D%28https%3A//github.com/apache/superset/blob/master/helm/superset/values.yaml%29) [](https://go.dosu.dev/discord-bot) [](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/discussions/36420) GitHub link: https://github.com/apache/superset/discussions/36420#discussioncomment-15170834 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
