You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by "lyric2249 (via GitHub)" <gi...@apache.org> on 2025/01/27 17:40:36 UTC
[I] There is no error in any log, but report is not sent for both slack and email. [superset]
lyric2249 opened a new issue, #32001:
URL: https://github.com/apache/superset/issues/32001
### Bug description
We are currently using Superset latest (4.1.1), and imac. After cloning the repository via Git (https://github.com/apache/superset), we set up the Superset environment using docker-compose-image-tag.yml with Docker Compose. To investigate an issue, we modified docker-compose-image-tag.yml to add a Flower container.
After setting up the reports, we attempted to send them. Although all the report dispatches show as "success," none of the reports are being delivered. We checked all the logs, including those for worker, worker-beat, Flower, and web, and they all indicate that the dispatches were successful.
The configuration is set as follows:
- ALERT_REPORTS_NOTIFICATION_DRY_RUN = False
- "ALERT_REPORTS": True
- "ALERT_REPORT_SLACK_V2": True
SMTP is configured with Gmail, and SLACK_API_TOKEN is set as "xoxb-......". When setting up SMTP, I used an app password generated by Google. Additionally, when I tested the email example code provided in the Alert & Report section of the Superset documentation (https://superset.apache.org/docs/configuration/alerts-reports/#send-a-test-email) with my Gmail information, the email was successfully sent.
I cannot figure out why the reports are not being delivered. Could you help me understand why this issue occurs?
### Screenshots/recordings
- docker containers
- flower logs
- report execution logs
- report configuration
 
### Superset version
master / latest-dev
### Python version
3.10
### Node version
I don't know
### Browser
Safari
### Additional context
_No response_
### Checklist
- [x] I have searched Superset docs and Slack and didn't find a solution to my problem.
- [x] I have searched the GitHub issue tracker and didn't find a similar bug report.
- [x] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.
--
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-unsubscribe@superset.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [I] There is no error in any log, but report is not sent for both slack and email. [superset]
Posted by "lyric2249 (via GitHub)" <gi...@apache.org>.
lyric2249 closed issue #32001: There is no error in any log, but report is not sent for both slack and email.
URL: https://github.com/apache/superset/issues/32001
--
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-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [I] There is no error in any log, but report is not sent for both slack and email. [superset]
Posted by "lyric2249 (via GitHub)" <gi...@apache.org>.
lyric2249 commented on issue #32001:
URL: https://github.com/apache/superset/issues/32001#issuecomment-2623465030
Thank you for the notification. When I set `ALERT_REPORTS_NOTIFICATION_DRY_RUN = False` in `superset/config.py`, it appears to work correctly now. However, in `docker/pythonpath_dev/superset_config.py`, the setting was `ALERT_REPORTS_NOTIFICATION_DRY_RUN = False`, and I am not sure why it functioned under the configuration `ALERT_REPORTS_NOTIFICATION_DRY_RUN = True`. For anyone who encounters this issue in the future, please try to fix your `superset/config.py` file as well.
--
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-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [I] There is no error in any log, but report is not sent for both slack and email. [superset]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
dosubot[bot] commented on issue #32001:
URL: https://github.com/apache/superset/issues/32001#issuecomment-2616488300
<!-- Greeting -->
Hey there, @lyric2249! I'm here to help you with any bugs, questions, or contributions you have for the project. Let's tackle this together!
<!-- Answer -->
I found some similar discussions that might be relevant to your issue:
1. [Nothing triggered issue in alert report in superset](https://github.com/apache/superset/discussions/31988) - This discussion is still open and might provide insights into similar problems with alert reports not being triggered <sup>[[1]](https://github.com/apache/superset/discussions/31988)</sup>.
2. [No Slack notification method when using Report/Alert and Docker Compose](https://github.com/apache/superset/discussions/25487) - This discussion is also open and addresses issues with Slack notifications in a Docker Compose setup <sup>[[2]](https://github.com/apache/superset/discussions/25487)</sup>.
3. [Alerting mechanism of apache superset does not work at all](https://github.com/apache/superset/discussions/28126) - This is another open discussion that might have relevant information about alerting mechanisms not functioning as expected <sup>[[3]](https://github.com/apache/superset/discussions/28126)</sup>.
Regarding your issue, ensure that the `ALERT_REPORTS_NOTIFICATION_DRY_RUN` is set to `False`, which you have already done. Additionally, verify that the `SLACK_API_TOKEN` is correctly configured and not empty, as an empty token would prevent Slack notifications from being sent <sup>[[2]](https://github.com/apache/superset/discussions/25487)</sup>.
Since your SMTP configuration seems correct (as test emails are sent successfully), and the logs indicate success, it might be worth checking the network and authentication settings to ensure the worker can access the report URL. You can use `curl` to test the URL from the worker environment and adjust `WEBDRIVER_BASEURL` if necessary <sup>[[4]](https://github.com/apache/superset/blob/master/docs/docs/configuration/alerts-reports.mdx)</sup>.
If the issue persists, reviewing the Celery worker logs for any discrepancies in task execution might provide further insights <sup>[[4]](https://github.com/apache/superset/blob/master/docs/docs/configuration/alerts-reports.mdx)</sup>.
<!-- Dosu Comment Footer -->
*To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
---
<sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/d03c778f-5db5-418f-947d-09104a3b0098?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/d03c778f-5db5-418f-947d-09104a3b0098?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/d03c778f-5db5-418f-947d-09104a3b0098?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/d03c778f-5db5-418f-947d-09104a3b0098?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/d03c778f-5db5-418f-947d-09104a3b0098?feedback_type=hallucination) | [Other](https://app.dosu.dev/response-feedback/d03c778f-5db5-418f-947d-09104a3b0098?feedback_type=other)</sup>
--
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-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [I] There is no error in any log, but report is not sent for both slack and email. [superset]
Posted by "iercan (via GitHub)" <gi...@apache.org>.
iercan commented on issue #32001:
URL: https://github.com/apache/superset/issues/32001#issuecomment-2621062802
The worker logs indicate that `ALERT_REPORTS_NOTIFICATION_DRY_RUN` is enabled. Please verify your configuration.
--
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-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org