Opened at 2010-01-17T17:04:12Z
Last modified at 2014-09-11T22:19:58Z
#912 new enhancement
Build In Fault-Monitoring and Reporting — at Version 3
Reported by: | bewst | Owned by: | nobody |
---|---|---|---|
Priority: | major | Milestone: | undecided |
Component: | code-nodeadmin | Version: | 1.5.0 |
Keywords: | error | Cc: | |
Launchpad Bug: |
Description (last modified by warner)
When configuring a node there should be a place to enter an email address that will be notified when something goes wrong with that node. Otherwise, errors will be missed. Other notification methods, such as IRC, optional. You may want to have nodes check on one-another in case of system crashes.
Change History (3)
comment:1 Changed at 2010-01-17T18:33:59Z by davidsarah
- Keywords error added
comment:2 Changed at 2012-01-15T15:28:59Z by zooko
comment:3 Changed at 2014-09-11T22:19:58Z by warner
- Component changed from unknown to code-nodeadmin
- Description modified (diff)
Note: See
TracTickets for help on using
tickets.
See #529 for a request that when a node detects that it is failing, it clearly indicates that fact to a watching process such as a load-balancer or a monitoring system like nagios, ganglia, or zenoss. That might suffice to close this ticket, because that monitoring system could then alert the operator.
Least Authority Enterprises is working on related behavior and will update these tickets as appropriate.