Sangarshanan opened a new issue, #22351: URL: https://github.com/apache/superset/issues/22351
A clear and concise description of what the bug is. #### How to reproduce the bug Add the following lines to superset_config.py ```python from superset.stats_logger import StatsdStatsLogger STATS_LOGGER = StatsdStatsLogger(host='localhost', port=8125, prefix='superset') ``` and the extra param to gunicorn cmd in `run-server.sh` `--statsd-host localhost:8125 ` I am also running a development server `FLASK_ENV` and `SUPERSET_ENV` set to `development` BUT when i build and run superset from scratch `Superset 0.0.0-dev` then the statd logger seems to show up locally, it however fails to show up in my docker compose ### Expected results stats_logger should start logging major events like query timings ### Actual results statsd logger does not show up. #### Screenshots If applicable, add screenshots to help explain your problem. ### Environment - browser type and version: Chrome Version 108.0.5359.94 - superset version: 1.51.2 - python version: Python 3.9.15 - node.js version: v18.11.0 - any feature flags active: FLASK_ENV, SUPERSET_ENV = development ### Checklist Make sure to follow these steps before submitting your issue - thank you! - [x] I have checked the superset logs for python stack traces and included it here as text if there are any. - [x] 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 stats_logger shows up when running locally but does not with docker-compose -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
