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.

Sign up for GitHub

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

Jump to bottom

Cron task reporting #285

Open

9 tasks

jimmydorry opened this issue Jun 6, 2016 · 0 comments

Assignees

Labels

back-end custom-games

Member

jimmydorry commented Jun 6, 2016

Build old reporting style into new scheduler, taking advantage of new structure.

We should also be able to report multiple incidents per mod. We currently only report the first one, which can sometimes mask issues.

Base:

Report on movements greater than the deviation (of the last 12 runs) in either direction, instead of based on percentage change
Report on value becoming 0
Report on value increasing from 0
Report on new high value
Significant events should hit the main channel. What kinds of events are significant?

Maybe Significant:

Report high player failure rates
Report when mod starts recording games with dedis
Report when no games recorded for the day
Report when schema has no new values for a week

jimmydorry added custom-games back-end labels

jimmydorry self-assigned this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment