dosubot[bot] commented on issue #28381:
URL: https://github.com/apache/superset/issues/28381#issuecomment-2100022930
<!-- Answer -->
To address the issue with the ALERT manager not working in your 6-month-old
Superset installation, here are some targeted steps to help resolve the problem:
1. **Check the `"ALERT_REPORTS"` Feature Flag**: Make sure it's enabled in
your `superset_config.py`. This is essential for alert and report functionality.
```python
FEATURE_FLAGS = {
"ALERT_REPORTS": True
}
```
2. **Update Celery Beat Schedule**: Ensure you have a schedule for
`reports.scheduler` in your Celery configuration to enable alert and report
scheduling.
```python
beat_schedule = {
"reports.scheduler": {
"task": "reports.scheduler",
"schedule": crontab(minute="*", hour="*"),
},
"reports.prune_log": {
"task": "reports.prune_log",
"schedule": crontab(minute=0, hour=0),
},
}
```
3. **Ensure Browser Installation for Screenshots**: If not using a dev
docker image, confirm a headless browser is installed for screenshot
functionality. For Firefox, install `firefox-esr` and `geckodriver`; for
Chrome, `google-chrome-stable` and `chromedriver`.
4. **SMTP or Slack Configuration**: For notifications, ensure your SMTP
settings or `SLACK_API_TOKEN` are correctly configured.
- **Slack**:
```python
SLACK_API_TOKEN = "xoxb-your-slack-token"
```
- **Email**:
```python
SMTP_HOST = "smtp.sendgrid.net"
SMTP_PORT = 2525
SMTP_USER = "your_user"
SMTP_PASSWORD = "your_password"
SMTP_MAIL_FROM = "[email protected]"
```
5. **Review Celery Worker and Beat Logs**: For further troubleshooting,
examining the logs of your Celery worker and beat can provide additional
insights into any errors or issues.
Ensure all configurations, especially those related to Celery, the headless
browser, and notification settings, are correct. For more detailed guidance,
refer to the [Superset
documentation](https://github.com/apache/superset/blob/master/docs/docs/configuration/alerts-reports.mdx).
If after following these steps you're still facing issues, providing more
specific details about the errors or problems you're encountering, including
any error messages, would be helpful for further diagnosis.
<!-- Dosu Comment Footer -->
<details>
<summary>
#### Details
</summary>
**Sources**
- [Issue with Alerts and Reports on
3.0.x](https://github.com/apache/superset/discussions/25858)
-
[docs/docs/configuration/alerts-reports.mdx](https://github.com/apache/superset/blob/master/docs/docs/configuration/alerts-reports.mdx)
-
[RELEASING/release-notes-0-38/README.md](https://github.com/apache/superset/blob/master/RELEASING/release-notes-0-38/README.md)
-
[CHANGELOG/3.0.0.md](https://github.com/apache/superset/blob/master/CHANGELOG/3.0.0.md)
-
[superset/commands/report/exceptions.py](https://github.com/apache/superset/blob/master/superset/commands/report/exceptions.py)
-
[RELEASING/release-notes-1-0/README.md](https://github.com/apache/superset/blob/master/RELEASING/release-notes-1-0/README.md)
<br/>
**About Dosu**
This response is meant to be useful and save you time. It is **not meant to
be a precise solution**, but rather a starting point for your own research.
Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is
irrelevant.
</details>
*To continue the conversation, mention @dosu.*
--
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]
