Generate critical log messages when batteries are low

[GoogleCodeExporter]

Create a class that receives all low battery events and generates a daily 
critical log message. This feature combined with critical messages notification 
by e-mail should be useful to detect a low battery problem.

Original issue reported on code.google.com by jordi.pu...@gmail.com on 22 Aug 2010 at 7:34

[GoogleCodeExporter]

Good idea. I would make a configurable NotificationCollector that apply rules 
on events to generate the notifications. This would allow for generating 
notifications on weather conditions (wind for windsurfers or storm prevention, 
freezing, UV for children suncreaming :)

Notifications could be sent as logging lines, thus we can use the existing 
LoggingHandler infrastructure and channels. Of course, the westep protocol 
should be extended to also include battery events.

Original comment by laurent....@gmail.com on 22 Aug 2010 at 7:11

[GoogleCodeExporter]

It might be a good idea to move this logic from the driver to the logger, thus 
unifying these notifications ins a single point. However I am not sure that a 
general notification tool should use the logging modules. Maybe in the future 
we need to have a wWatchdog or wNotif in a separate process.

Original comment by jordi.pu...@gmail.com on 22 Aug 2010 at 9:10

[GoogleCodeExporter]

Yes, we can add an abstraction between the NotificationCollector and
the underlying python logging system, so that we can also provide our
own notification mechanisms or route notifications to existing
monitoring infrastructures (e.g. nagios).

Regarding something like the watchdog, I see that as separate concern.
I don't think it should be related to the notification system, only by
the fact that it shoul react on absence of events. As it is something
needed in many applications, I guess we can reuse some existing stuff
(even the voyage mechanism that would allow to completely restart the
alix when no more event comes). Would we want to create an issue for
that?

Original comment by laurent....@gmail.com on 25 Aug 2010 at 8:52

[GoogleCodeExporter]

I didn't mean a operating system watchdog but a weather watchdog. I.e. some 
piece of code that can handle alarms, notifications, etc.

Original comment by jordi.pu...@gmail.com on 26 Aug 2010 at 7:16

[GoogleCodeExporter]

Ah. OK. I understood wrongly. I suspect that there exists such systems that 
fulfill our needs and that it should not be necessary to reimplement it in 
wfrog, except the collector filtering events to raise alarms, of course.

Original comment by laurent....@gmail.com on 26 Aug 2010 at 8:54

[GoogleCodeExporter]

Original comment by jordi.pu...@gmail.com on 11 Sep 2010 at 8:52

• Added labels: Milestone-Release0.9
• Removed labels: Milestone-Release0.8

[GoogleCodeExporter]

Issue 58 has been merged into this issue.

Original comment by laurent....@gmail.com on 6 Feb 2011 at 8:07