You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by "rajshivage (via GitHub)" <gi...@apache.org> on 2026/01/20 06:11:34 UTC
[D] Superset upgrade from 2 to 3 [superset]
GitHub user rajshivage created a discussion: Superset upgrade from 2 to 3
What does the below config mean in the superset_config.py?
```
# Console Log Settings
LOG_FORMAT = "%(asctime)s:%(levelname)s:%(name)s:%(message)s"
# LOG_LEVEL = DEBUG, INFO, WARNING, ERROR, CRITICAL
LOG_LEVEL = get_env_variable("LOG_LEVEL", "INFO")
```
GitHub link: https://github.com/apache/superset/discussions/37264
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] Superset upgrade from 2 to 3 [superset]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
GitHub user dosubot[bot] edited a comment on the discussion: Superset upgrade from 2 to 3
<!-- Answer -->
LOG_FORMAT sets the structure of log messages using standard Python logging syntax, so logs will include the timestamp, log level, logger name, and the message itself (for example: 2024-01-20 12:00:00:INFO:my_logger:Something happened) [reference](https://github.com/apache/superset/blob/master/superset/config.py).
LOG_LEVEL controls the minimum severity of logs that will be output (e.g., DEBUG, INFO, WARNING, ERROR, CRITICAL). Setting it via get_env_variable("LOG_LEVEL", "INFO") means Superset will use the value of the LOG_LEVEL environment variable if set, or default to "INFO" if not. This allows you to change log verbosity without editing code [reference](https://github.com/apache/superset/blob/master/docker/pythonpath_dev/superset_config.py).
Superset does not provide a built-in get_env_variable function—you or your organization must define it. A typical implementation looks like:
```python
import os
def get_env_variable(name, default):
return os.environ.get(name, default)
```
This logging configuration pattern is consistent between Superset 2 and 3, so you shouldn't encounter breaking changes related to these settings during your upgrade [reference](https://github.com/apache/superset/blob/master/superset/utils/logging_configurator.py).
<!-- Dosu Comment Footer -->
*To reply, just mention [@dosu](https://go.dosu.dev/dosubot?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=reply-with-mention&utm_term=apache%2Fsuperset).*
---
Docs are dead. Just use [Dosu](https://dosu.dev?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-tagline&utm_term=apache%2Fsuperset).
[](https://app.dosu.dev/response-feedback?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-feedback&utm_term=apache%2Fsuperset&message_id=9a27a95e-1222-45c0-b10c-4f008243e245) [](https://github.dosu.com/apache/superset?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-ask-repo&utm_term=apache%2Fsuperset) [](https://app.dosu.dev/signup?referrer=openSource&source=github-footer&utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-share-team&utm_term=apache%2Fsuperset)
GitHub link: https://github.com/apache/superset/discussions/37264#discussioncomment-15545328
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] Superset upgrade from 2 to 3 [superset]
Posted by "rajshivage (via GitHub)" <gi...@apache.org>.
GitHub user rajshivage edited a discussion: Superset upgrade from 2 to 3
@dosu What does the below config mean in the superset_config.py?
```
# Console Log Settings
LOG_FORMAT = "%(asctime)s:%(levelname)s:%(name)s:%(message)s"
# LOG_LEVEL = DEBUG, INFO, WARNING, ERROR, CRITICAL
LOG_LEVEL = get_env_variable("LOG_LEVEL", "INFO")
```
GitHub link: https://github.com/apache/superset/discussions/37264
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] Superset upgrade from 2 to 3 [superset]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
GitHub user dosubot[bot] added a comment to the discussion: Superset upgrade from 2 to 3
<!-- Answer -->
LOG_FORMAT sets the structure of log messages using standard Python logging syntax, so logs will include the timestamp, log level, logger name, and the message itself (for example: 2024-01-20 12:00:00:INFO:my_logger:Something happened) [reference](https://github.com/apache/superset/blob/master/superset/config.py).
LOG_LEVEL controls the minimum severity of logs that will be output (e.g., DEBUG, INFO, WARNING, ERROR, CRITICAL). Setting it via get_env_variable("LOG_LEVEL", "INFO") means Superset will use the value of the LOG_LEVEL environment variable if set, or default to "INFO" if not. This allows you to change log verbosity without editing code [reference](https://github.com/apache/superset/blob/master/docker/pythonpath_dev/superset_config.py).
Superset does not provide a built-in get_env_variable function—you or your organization must define it. A typical implementation looks like:
```python
import os
def get_env_variable(name, default):
return os.environ.get(name, default)
```
This logging configuration pattern is consistent between Superset 2 and 3, so you shouldn't encounter breaking changes related to these settings during your upgrade [reference](https://github.com/apache/superset/blob/master/superset/utils/logging_configurator.py).
<!-- 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/9a27a95e-1222-45c0-b10c-4f008243e245?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/9a27a95e-1222-45c0-b10c-4f008243e245?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/9a27a95e-1222-45c0-b10c-4f008243e245?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/9a27a95e-1222-45c0-b10c-4f008243e245?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/9a27a95e-1222-45c0-b10c-4f008243e245?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/9a27a95e-1222-45c0-b10c-4f008243e245?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/9a27a95e-1222-45c0-b10c-4f008243e245?feedback_type=other)</sup>
[](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=github) [](https://cursor.com/link/prompt?text=LOG_FORMAT%20sets%20the%20structure%20of%20log%20messages%20using%20standard%20Python%20logging%20syntax%2C%20so%20logs%20will%20include%20the%20timestamp%2C%20log%20level%2C%20logger%20name%2C%20and%20the%20message%20itself%20%28for%20example%3A%202024-01-20%2012%3A00%3A00%3AINFO%3Amy_logger%3ASomething%20happened%29%C2%A0%5Breference%5D%28https%3A//github.com/apache/superset/blob/master/superset/config.py%29.%0A%0ALOG_LEVEL%20controls%20the%20minimum%20severity%20of%20logs%20that%20will%20be%20output%20%28e.g.%2C%20DEBUG%2C%20INFO%2C%20WARNING%2C%20ERROR%2C%20CRITICAL%29.%20Setting%20it%20via%20get_env_variable%28%22LOG_LEVEL%22%2C%20%22INFO%22%29%20means%20Superset%20will%20use%20the%20value%20of%20the%20LOG_LEVEL%20environment%20variable%20if%20se
t%2C%20or%20default%20to%20%22INFO%22%20if%20not.%20This%20allows%20you%20to%20change%20log%20verbosity%20without%20editing%20code%C2%A0%5Breference%5D%28https%3A//github.com/apache/superset/blob/master/docker/pythonpath_dev/superset_config.py%29.%0A%0ASuperset%20does%20not%20provide%20a%20built-in%20get_env_variable%20function%E2%80%94you%20or%20your%20organization%20must%20define%20it.%20A%20typical%20implementation%20looks%20like%3A%0A%0A%60%60%60python%0Aimport%20os%0Adef%20get_env_variable%28name%2C%20default%29%3A%0A%20%20%20%20return%20os.environ.get%28name%2C%20default%29%0A%60%60%60%0A%0AThis%20logging%20configuration%20pattern%20is%20consistent%20between%20Superset%202%20and%203%2C%20so%20you%20shouldn%27t%20encounter%20breaking%20changes%20related%20to%20these%20settings%20during%20your%20upgrade%C2%A0%5Breference%5D%28https%3A//github.com/apache/superset/blob/master/superset/utils/logging_configurator.py%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/37264)
GitHub link: https://github.com/apache/superset/discussions/37264#discussioncomment-15545328
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org