> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:nagios-users- > [EMAIL PROTECTED] On Behalf Of David Latorre > Sent: Wednesday, July 12, 2006 9:30 AM > To: nagios-users@lists.sourceforge.net > Subject: [Nagios-users] Setting scheduled downtimes a posteriori > > Hi, everyone. > > We are using Nagios 1.3 and were wondering if there is a way of setting > downtimes a posteriori, I mean, once there has been an outage in a > service, telling nagios that, actually, it was a scheduled downtime. We > have tried it but it seems it has no effect when you calculate the > availability...
Definitely not through the gui. This is untested but since the reports use the log files only for their information, I would imagine that you can just insert downtime log entries at the correct time locations in the correct log file -- For a host -- [1105463596] HOST DOWNTIME ALERT: sample-hostname;STARTED; Host has entered a period of scheduled downtime [1105470770] HOST DOWNTIME ALERT: sample-hostname;STOPPED; Host has exited from a period of scheduled downtime For a service -- [1105467783] SERVICE DOWNTIME ALERT: someother-hostname;PING;STARTED; Service has entered a period of scheduled downtime [other normal log entries] [1105474963] SERVICE DOWNTIME ALERT: someother-hostname;PING;STOPPED; Service has exited from a period of scheduled downtime The numbers in [] are the timestamp for the beginning and end of the downtimes. -- Marc ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ 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
