stallonederek / clusterfuzz

Automatically exported from code.google.com/p/clusterfuzz
0 stars 0 forks source link

Better monitoring for various errors #4

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
There are quite a few errors that are not easy to notice without watching 
ClusterFuzz very closely. Some examples:

- Exceptions
- Problems with job definitions
- Fuzzer errors
- Build archiving issues

We should implement a better way to monitor all of these. Probably some sort of 
dashboard that requires admin access as well as automated notifications for 
certain issues.

I'm setting this as low priority for now since I'm not sure when I'll be able 
to get around to it, but it does seem worthwhile.

Original issue reported on code.google.com by mbarbe...@chromium.org on 14 Oct 2014 at 5:11