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

Improve relevance of email alerts by adding "acknowledge" action #1213

Open
mlandauer opened this issue May 5, 2019 · 0 comments
Open

Improve relevance of email alerts by adding "acknowledge" action #1213

mlandauer opened this issue May 5, 2019 · 0 comments

Comments

@mlandauer
Copy link
Member

The problem:

Email alerts of broken scrapers are a fantastic way to ensure that scrapers are maintainable. However, in the case of planningalerts we have a lot of scrapers and many of them (around 30 or 40) can be broken at any one time. It just isn't helpful to get an email alert one day that says have 38 broken scrapers and the next day get a message saying you have 39 broken scrapers. Is it one new broken scraper? Which one?

The fact that the subject line is roughly the same every day and the email alerts come every day means that in reality I completely ignore them. I suspect I'm not unusual in this in which case the current design of the email alerts is completely broken because it just doesn't serve its purpose.

A possible solution:
Add an "acknowledge" action next to every broken scraper in an email alert. When you acknowledge a broken scraper you're saying I've recorded that it's broken somewhere sensible and I don't want to get alerted about it (until it's fixed and then breaks again).

This would allow the user to truly see new interesting things.

Anyone can subscribe to get email alerts from any scraper so the acknowledge action needs to be a personal one. Everyone will have to do it for themselves.

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

No branches or pull requests

1 participant