-
Notifications
You must be signed in to change notification settings - Fork 13.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The alarm and email sending functions of superset are unavailable #29541
Comments
The task to send the mail is not scheduled,No task error information is displayed in the log |
Hey @hswlxc, I'm here to assist you with any bugs, questions, or contributions you may have. Let's tackle this issue together! To resolve the issue where the alarm and email sending functions of Superset are unavailable, you need to ensure that the From the provided context, it appears that the # Enables Alerts and reports new implementation
"ALERT_REPORTS": True, This change will enable the alerts and reports functionality, which includes the alarm and email sending features [1]. |
![]() |
Since the
If all these configurations are correct and the issue persists, it might be helpful to provide more specific details about the current configuration and any additional logs or error messages that might be available. For further reference, you can check similar issues and discussions:
@rusackas, this one's a bit out of my wheelhouse, could you step in and provide your guidance? |
![]() |
Since the configuration checks are fine and no scheduled tasks are being started, let's ensure a few more things:
By following these steps, you should be able to identify and resolve the issue with the scheduled tasks not being started [1][2]. |
from superset.extensions import celery_app |
The
By following these steps, you should be able to identify and resolve the connection issue between Celery and Redis [1][2]. |
![]() ![]() |
Since the task ID is printed, indicating that the connection to Redis is fine, but the task is not visible in Flower, let's focus on a few additional checks and configurations:
By following these steps, you should be able to identify and resolve the issue with the |
![]() Through the above command, reports.scheduler has registered Celery, but still has no celery sending task @dosu |
Since the
By following these steps, you should be able to identify and resolve the issue with the |
from celery.schedules import crontab class CeleryConfig: CELERY_CONFIG = CeleryConfig ALERT_REPORTS_NOTIFICATION_DRY_RUN = False ![]() |
Given that only the
By following these steps, you should be able to identify and resolve the issue with the tasks not being executed and ensure they are correctly scheduled and executed by Celery [1][2]. |
Bug description
superset_config.py.zip
This is my profile, and according to this configuration, the email cannot be sent
How to reproduce the bug
Screenshots/recordings
No response
Superset version
4.0.1
Python version
3.9
Node version
16
Browser
Chrome
Additional context
No response
Checklist
The text was updated successfully, but these errors were encountered: