You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes queries are scheduled to run repeatedly but they end up getting very little use, so they end up continuing to consume server resources while not providing much value. Issue #15 is one way to help alleviate this, but it might also be useful to have redash itself notice when a scheduled query is unused, sending notifications or possibly even deactivating the unused queries.
The text was updated successfully, but these errors were encountered:
I prefer this solution than to complicate the UI with the solution proposed in #15. I suspect that people will ignore the expiration setting anyway.
At EverythingMe, we had a Jenkins job that used the events table to find unused scheduled queries and unschedule them. It will be great to have this as a feature in Redash, but till then you can do something similar. Should be quite simple.
spasovski
pushed a commit
to spasovski/redash
that referenced
this issue
Feb 6, 2017
Sometimes queries are scheduled to run repeatedly but they end up getting very little use, so they end up continuing to consume server resources while not providing much value. Issue #15 is one way to help alleviate this, but it might also be useful to have redash itself notice when a scheduled query is unused, sending notifications or possibly even deactivating the unused queries.
The text was updated successfully, but these errors were encountered: