Skip to content
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

Transient query execution errors sent to alert owners as alert failure notifications #20418

Closed
3 tasks done
zhaorui2022 opened this issue Jun 17, 2022 · 0 comments
Closed
3 tasks done
Labels
#bug Bug report

Comments

@zhaorui2022
Copy link
Contributor

When executing alert queries, if there is any transient errors, the error will be sent to users as alert failures. However, this could be avoided by adding retries.

How to reproduce the bug

This bug can only be reproduced when there is any transient error when executing queries.

Expected results

If the alert itself is working, users shouldn't receive a notification saying the alert fails.

Actual results

When there is a transient error, users will receive a notification with the transient error message.And also, the error message isn't helpful for alert owners to debug as it is usually internal errors.

Screenshots

N/A

Environment

(please complete the following information):

  • browser type and version: This is caused by backend and it applies to all browser types and versions.
  • superset version: superset version: latest
  • python version: python --version: any python version
  • node.js version: node -v N/A
  • any feature flags active: None

Checklist

Make sure to follow these steps before submitting your issue - thank you!

  • I have checked the superset logs for python stacktraces and included it here as text if there are any.
  • I have reproduced the issue with at least the latest released version of superset.
  • I have checked the issue tracker for the same issue and I haven't found one similar.

Additional context

Add any other context about the problem here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
#bug Bug report
Projects
None yet
Development

No branches or pull requests

1 participant