> Unfortunately OMSA has no info on when the charge cycle is expected to > be finished, or how long it has been in its current learn/charge state: > > # omreport storage battery controller=1 > Battery 0 on Controller PERC 6/E Adapter (Slot 1) > > Controller PERC 6/E Adapter (Slot 1) > ID : 0 > Status : Non-Critical > Name : Battery 0 > State : Charging > Recharge Count : Not Applicable > Max Recharge Count : Not Applicable > Predicted Capacity Status : Ready > Learn State : Requested > Next Learn Time : 0 hours > Maximum Learn Delay : 7 days 0 hours > Learn Mode : Auto > > I could make the plugin record it, but then I would violate my principle > that the plugin should be stateless... Introducing state in the plugin > complicates things.
Hmmm, that's unfortunate that they don't track a duration or start time. :( And no, I fully agree - plugins should be stateless. Keeping track of state is an ugly, error-prone business. Benny -- "Hairy ape nads." -- Colleen, playing Neverwinter Nights ------------------------------------------------------------------------------ Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev _______________________________________________ Nagios-users mailing list Nagios-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null