Only the superset_worker container needs this headless browser to browse to the target chart or dashboard.

If you are running a non-dev docker image, e.g., a stable release like apache/superset:2.0.1, that image does not include a headless browser.

Note: All the components required (Firefox headless browser, Redis, Postgres db, celery worker and celery beat) are present in the dev docker image if you are following Installing Superset Locally.Īll you need to do is add the required config variables described in this guide (See Detailed Config). If you choose Chrome, you must also change the value of WEBDRIVER_TYPE to 'chrome' in your superset_config.py. Only Firefox and Chrome are currently supported.

You must install a headless browser, for taking screenshots of the charts and dashboards.

To disable dry-run mode and start receiving email/Slack notifications, set ALERT_REPORTS_NOTIFICATION_DRY_RUN to False in superset config. Screenshots will be taken but no messages actually sent as long as ALERT_REPORTS_NOTIFICATION_DRY_RUN = True, its default value in config.py.

At least one of those must be configured, depending on what you want to use:.

beat_schedule in Celer圜onfig must contain schedule for reports.scheduler.

'ALERT_REPORTS' feature flag must be turned to True.Requirements Commons In your superset_config.py or superset_config_docker.py To turn them on, you need to do some setup, described here. Alerts are sent when a SQL condition is reachedĪlerts and reports are disabled by default.Users can configure automated alerts and reports to send dashboards or charts to an email recipient or Slack channel.

Slack firefox