A clear and concise description of what the bug is.

Expected results

can find superset.log file

Actual results

cannot find it

Screenshots

This is my config.py file 10

How to reproduce the bug

  1. Go to 'superset/config.py'
  2. See configuration of log console

Environment

  • superset version: 0.34.0rc1
  • python version: 3.6
  • node.js version: 10.16.0
  • npm version: 6.9.0

Checklist

Make sure these boxes are checked before submitting your issue - thank you!

  • [ ] I have checked the superset logs for python stacktraces and included it here as text if there are any.
  • [ ] I have reproduced the issue with at least the latest released version of superset.
  • [x] I have checked the issue tracker for the same issue and I haven't found one similar.

Additional context

I am running superset in Docker enviornment.

Comment From: issue-label-bot[bot]

Issue-Label Bot is automatically applying the label #question to this issue, with a confidence of 0.72. Please mark this comment with :thumbsup: or :thumbsdown: to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

Comment From: kuckjwi0928

You must modify the settings.

# config.py
ENABLE_TIME_ROTATE = True

If you make the above corrections and restart as above You can check the path ~/superset/superset.log

Comment From: zhaoyongjie

for default settings

cat $SUPERSET_HOME/superset.log

Comment From: syazshafei

Alright thanks

Comment From: n15902179169

Is there no log type in the generated log file？how can i know the type in log files?

Comment From: JoanSebasMartinez

I have the same issue with the log, this is my config.py:

ENABLE_TIME_ROTATE = True TIME_ROTATE_LOG_LEVEL = logging.INFO FILENAME = os.path.join(DATA_DIR, "superset.log") ROLLOVER = "midnight" INTERVAL = 1 BACKUP_COUNT = 30

After restarting superset it doesn't generate the superset.log file

Comment From: Moosheimer

@JoanSebasMartinez Same for me.

Comment From: rusackas

@dosu

Comment From: dosubot[bot]

The superset.log file should be created at the path set by FILENAME in your config (usually os.path.join(DATA_DIR, "superset.log")). If you're running in Docker, make sure your custom config (like superset_config.py) is placed at /app/docker/pythonpath_dev/superset_config_docker.py—otherwise, your settings may not be picked up and the log file won't be created as expected. Also, check that the DATA_DIR directory exists and is writable inside the container; if not, the log file won't be created and you might only see errors in the container's stdout/stderr logs.

If ENABLE_TIME_ROTATE is True, Superset uses a TimedRotatingFileHandler to write logs to the file you specified. If the log file still isn't appearing, double-check the config file location, directory permissions, and look for any errors in the container logs during startup for clues about logging setup issues.

For log type: the default log format includes the log level (INFO, ERROR, etc.), so you should see the type in each log entry if the file is being written.

More details on logging config and Docker placement are here:
- Logging config reference
- Docker config placement
- How logging is set up in code

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other  Join Discord Share on X