dosubot[bot] commented on issue #34748:
URL: https://github.com/apache/superset/issues/34748#issuecomment-3201276973

   <!-- Answer -->
   Superset logs are sent to stdout/stderr by default when running in 
containers (like Docker). You can view these logs using `docker logs 
<container_name>`. No log files are created inside the container unless you 
explicitly enable file-based logging in your Superset config.
   
   If you want Superset to write logs to a file (for example, for easier 
searching or archiving), you can add these settings to your 
`superset_config.py` or `config.py`:
   
   ```python
   LOG_LEVEL = logging.DEBUG
   ENABLE_TIME_ROTATE = True
   TIME_ROTATE_LOG_LEVEL = logging.DEBUG
   FILENAME = os.path.join(DATA_DIR, "superset.log")
   ROLLOVER = "midnight"
   INTERVAL = 1
   BACKUP_COUNT = 30
   ```
   
   By default, the log file will be at `~/.superset/superset.log` unless you 
set the `SUPERSET_HOME` environment variable to change the data directory. In 
Docker, unless you mount a volume for logs, you’ll still want to use `docker 
logs` for troubleshooting. The Action Log UI only shows user actions and audit 
events, not backend errors—backend errors and warnings are found in the 
container logs or the log file if you configure one ([config.py 
reference](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/config.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/485c3ebe-fe84-44d0-b739-690b73cfd1ba?feedback_type=great_response)
 | 
[Irrelevant](https://app.dosu.dev/response-feedback/485c3ebe-fe84-44d0-b739-690b73cfd1ba?feedback_type=irrelevant_answer)
 | 
[Incorrect](https://app.dosu.dev/response-feedback/485c3ebe-fe84-44d0-b739-690b73cfd1ba?feedback_type=incorrect_sources)
 | 
[Verbose](https://app.dosu.dev/response-feedback/485c3ebe-fe84-44d0-b739-690b73cfd1ba?feedback_type=too_verbose)
 | 
[Hallucination](https://app.dosu.dev/response-feedback/485c3ebe-fe84-44d0-b739-690b73cfd1ba?feedback_type=hallucination)
 | [Report 
🐛](https://app.dosu.dev/response-feedback/485c3ebe-fe84-44d0-b739-690b73cfd1ba?feedback_type=bug_report)
 | 
[Other](https://app.dosu.dev/response-feedback/485c3ebe-fe84-44d0-b739-690b73cfd1ba?feedback_type=other)</sup>&nbsp;&nbsp;[![Chat
 with 
Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=githu
 b)&nbsp;[![Join 
Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share
 on 
X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/issues/34748)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org
For additional commands, e-mail: notifications-h...@superset.apache.org

Reply via email to