Alerts and Reports configuration in Superset 5.0.0rc2

[AviralDobhal07]

Hi all,
I’m trying to configure Alerts and Reports in Apache Superset 5.0.0rc2, but I'm encountering issues related to the Firefox driver. I’ve modified the Dockerfile to include Firefox and Geckodriver, but it still doesn’t work as expected. Interestingly, the same setup works fine in the development version of Superset 4.1.1. Could anyone guide me on the easiest and most reliable way to set up Alerts and Reports in Superset 5.0.0rc2 without much hassle?

[dosubot[bot]]

To set up Alerts and Reports in Apache Superset 5.0.0rc2 reliably, especially when facing issues with the Firefox driver, you can follow these steps:

1. Use the Dev Docker Image: The dev Docker image includes all necessary components like the Firefox headless browser. This can simplify the setup process.

2. Feature Flag: Ensure the "ALERT_REPORTS" feature flag is set to True in your superset_config.py or superset_config_docker.py.

3. Celery Configuration: Configure the beat_schedule in CeleryConfig for reports.scheduler.

4. Notification Settings: Set up either SMTP_* settings for emails or SLACK_API_TOKEN for Slack messages.

5. Disable Dry-Run Mode: Set ALERT_REPORTS_NOTIFICATION_DRY_RUN to False to ensure notifications are sent.

6. Headless Browser: If you choose to use Chrome instead of Firefox, set WEBDRIVER_TYPE to "chrome" in your configuration.

If you are using a non-dev Docker image, you can modify your docker-compose.yml to use a dev image for the worker container, which includes the headless browser, while using a stable release image for the superset_app container. This setup ensures all necessary components are available without additional configuration ^[1].

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}

[AviralDobhal07]

@dosu As far as I know, I read in the update notes that they mentioned: "30021 – The dev layer in our Dockerfile no longer includes Firefox binaries, only Chromium, to reduce bloat and Docker build time." How can we use Chromium if it's already included?

[dosubot[bot]]

To use Chromium for Alerts and Reports in Apache Superset 5.0.0rc2, you need to configure your superset_config.py or superset_config_docker.py to use the Chromium headless browser. Since Chromium is already included in the Dockerfile, set the WEBDRIVER_TYPE to "chrome" in your configuration file:

# In your superset_config.py or superset_config_docker.py
WEBDRIVER_TYPE = "chrome"

Additionally, ensure the "ALERT_REPORTS" feature flag is set to True and configure the necessary settings for email or Slack notifications. This setup will enable the use of Chromium for taking screenshots of charts and dashboards ^[1].

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}

[AviralDobhal07]

@dosu Not working

[dosubot[bot]]

To troubleshoot the issue with using Chromium for Alerts and Reports in Superset 5.0.0rc2, ensure the following steps are correctly implemented:

1. Configuration File: Double-check that WEBDRIVER_TYPE is set to "chrome" in your superset_config.py or superset_config_docker.py.

2. Feature Flag: Verify that the "ALERT_REPORTS" feature flag is set to True.

3. Celery Setup: Ensure that the beat_schedule in CeleryConfig includes a schedule for reports.scheduler.

4. Notifications: Confirm that your email (SMTP_* settings) or Slack (SLACK_API_TOKEN) configurations are correct.

5. Disable Dry-Run: Make sure ALERT_REPORTS_NOTIFICATION_DRY_RUN is set to False to receive actual notifications.

6. Chromium Installation: Since Chromium is included in the Dockerfile, there should be no need for additional installation steps. However, ensure that the Docker image you are using is up-to-date and includes the necessary Chromium binaries.

If these steps are correctly configured and the issue persists, consider checking the logs for any specific error messages that might provide more insight into the problem.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}