dosubot[bot] commented on issue #29255:
URL: https://github.com/apache/superset/issues/29255#issuecomment-2168211450
<!-- Answer -->
It looks like you have correctly configured the Redis settings for Celery.
However, there are a few additional configurations and checks you should ensure
are in place:
1. **Enable the `ALERT_REPORTS` Feature Flag**:
Ensure that the `ALERT_REPORTS` feature flag is enabled in your
configuration:
```python
FEATURE_FLAGS = {
'ALERT_REPORTS': True,
'DASHBOARD_RBAC': True,
'ENABLE_TEMPLATE_PROCESSING': True,
}
```
2. **Set `ALERT_REPORTS_NOTIFICATION_DRY_RUN` to `False`**:
Make sure this setting is correctly set to `False` to enable actual
notifications:
```python
ALERT_REPORTS_NOTIFICATION_DRY_RUN = False
```
3. **Configure the WebDriver**:
Ensure that the WebDriver is correctly configured for taking screenshots:
```python
WEBDRIVER_TYPE = "chrome"
WEBDRIVER_OPTION_ARGS = [
"--force-device-scale-factor=2.0",
"--high-dpi-support=2.0",
"--headless",
"--disable-gpu",
"--disable-dev-shm-usage",
"--no-sandbox",
"--disable-setuid-sandbox",
"--disable-extensions",
]
WEBDRIVER_BASEURL = "http://localhost:8088";
WEBDRIVER_BASEURL_USER_FRIENDLY = "http://IP:8088";
```
4. **Set the User for Rendering Dashboards**:
Ensure that the user for rendering dashboards is set:
```python
from superset.tasks.types import ExecutorType
THUMBNAIL_SELENIUM_USER = 'admin'
ALERT_REPORTS_EXECUTE_AS = [ExecutorType.SELENIUM]
```
5. **Check Celery Workers**:
Ensure that Celery workers are running and can connect to Redis. You can
start the Celery worker with:
```sh
celery -A superset.tasks.celery_app:app worker --loglevel=info
```
6. **Check Celery Beat**:
Ensure that Celery beat is running to schedule tasks:
```sh
celery -A superset.tasks.celery_app:app beat --loglevel=info
```
7. **Verify Redis Connection**:
Ensure that Redis is running and accessible. You can test the connection
using a Redis client:
```sh
redis-cli -h localhost -p 6379 ping
```
8. **SMTP Configuration**:
Ensure that your SMTP settings are correctly configured for email
notifications:
```python
SMTP_HOST = "SMTP_HOST"
SMTP_STARTTLS = True
SMTP_SSL = True
SMTP_USER = "SMTP_USER"
SMTP_PORT = 465
SMTP_PASSWORD = "SMTP_PASSWORD"
SMTP_MAIL_FROM = "SMTP_MAIL_FROM"
SMTP_SSL_SERVER_AUTH = False
```
By ensuring these configurations and checks are in place, you should be able
to set up alerts and reports in Apache Superset 4.0.1. If the issue persists,
check the Superset logs for any errors or warnings that might provide more
insights
<sup>[[1]](https://github.com/apache/superset/blob/master/docs/docs/configuration/alerts-reports.mdx)</sup><sup>[[2]](https://github.com/apache/superset/blob/master/docker/pythonpath_dev/superset_config.py)</sup>.
<!-- Dosu Comment Footer -->
*To continue talking to [Dosu](https://dosu.dev), 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: 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
