GitHub user dosubot[bot] added a comment to the discussion: Alerts & reports 
nothing triggered

<!-- Answer -->
You can check Celery worker and beat logs depending on how Superset is deployed:

- **Docker**: Use `docker logs <container-name>` for your worker and beat 
containers. All logs (INFO, WARNING, ERROR) are sent to stdout/stderr by 
default. This is the standard way to view logs in containerized setups.  
- **Kubernetes**: Use `kubectl logs <pod-name>` for the relevant worker or beat 
pod. If you need more detail, set the `SUPERSET_LOG_LEVEL` environment variable 
to `debug` in your deployment config to increase verbosity 
[[source]](https://github.com/apache/superset/discussions/33006).
- **Manual/Local**: If you start Celery with a command like `celery 
--app=superset.tasks.celery_app:app worker ...`, logs will appear in the 
terminal/session where you started the process 
[[source]](https://github.com/apache/superset/discussions/31988).

If you want file-based logging, you can enable it in your Superset config with 
`ENABLE_TIME_ROTATE = True` and set `FILENAME` to your desired log path, but 
this is not the default for Celery processes 
[[source]](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/config.py).

Typical log messages to look for: scheduling/running reports, connection 
errors, screenshot failures, and notification delivery status. These logs are 
key for troubleshooting why alerts/reports aren't triggering 
[[source]](https://github.com/apache/superset/discussions/28454).


<!-- 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/b27ab95d-f284-415e-85ea-1398183e4039?feedback_type=great_response)
 | 
[Irrelevant](https://app.dosu.dev/response-feedback/b27ab95d-f284-415e-85ea-1398183e4039?feedback_type=irrelevant_answer)
 | 
[Incorrect](https://app.dosu.dev/response-feedback/b27ab95d-f284-415e-85ea-1398183e4039?feedback_type=incorrect_sources)
 | 
[Verbose](https://app.dosu.dev/response-feedback/b27ab95d-f284-415e-85ea-1398183e4039?feedback_type=too_verbose)
 | 
[Hallucination](https://app.dosu.dev/response-feedback/b27ab95d-f284-415e-85ea-1398183e4039?feedback_type=hallucination)
 | [Report 
🐛](https://app.dosu.dev/response-feedback/b27ab95d-f284-415e-85ea-1398183e4039?feedback_type=bug_report)
 | 
[Other](https://app.dosu.dev/response-feedback/b27ab95d-f284-415e-85ea-1398183e4039?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=github)&
 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/discussions/35138)

GitHub link: 
https://github.com/apache/superset/discussions/35138#discussioncomment-14400304

----
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]

Reply via email to