On 20 Sep 2002 at 16:13, Russell Scibetti wrote:
> I've been working on a plugin where I need to know the exact structure
> of the status.log file, as in what each ;-delimited value stands for.
> So I went into the code and found out, and I figured it would be a good
> reference to share with the list. It could come in very handy for
> debugging, plugin development, custom CGI's, etc. So here is a list of
> what the status.log actually means. I attached it as a text file and
> printed it out at the bottom of the email. If I have the time to write
> a Perl function that can easily grab data from a line of the status log
> (like representing the line as a hash), I'll email that to the list as well.
>
> I noticed two fields that I'm curious about. There is a
> failure_prediction_enabled setting for hosts and services. Is this
> something that was going to be created but hasn't yet and the hook for
> the status log is there, or is there any failure prediction occurring?
Failure prediction is currently not in the logic, but it is on my
long-range drawing board. Not sure when it'll first appear -
probably close to a year before something stable is ready.
>
> Also, the field that says if something is in downtime is called the
> scheduled_downtime_depth. Can this be something other than 0 or 1? How
> is downtime depth determined?
Yes, this field can have multiple value. 0 means the host/service is
not in scheduled downtime. Anything >=1 indicates how many
"overlapping" downtime entries are currently in effect for the
host/service. For instance, if the current time is 3:00pm and two
downtime entries (1:00pm-3:30pm and 2:45pm-5:00pm) where scheduled
for a host/service, the number in this field would be 2.
>
> Thanks, and here is the list of values:
>
> -Russell
>
> Host Lines:
>
> [Time of last update] HOST;
> Host Name (string);
> Status (OK/DOWN/UNREACHABLE);
> Last Check Time (long time);
> Last State Change (long time);
> Acknowledged (0/1);
> Time Up (long time);
> Time Down (long time);
> Time Unreachable (long time);
> Last Notification Time (long time);
> Current Notification Number (#);
> Notifications Enabled (0/1);
> Event Handlers Enabled (0/1);
> Checks Enabled (0/1);
> Flap Detection Enabled (0/1);
> Host is Flapping (0/1);
> Percent State Change (###.##);
> Scheduled downtime depth (# - 0/1 ???);
> Failure Prediction Enabled (0/1);
> Process Performance Data(0/1);
> Plugin Output (string)
>
> Service Lines:
>
> [Time of last update] SERVICE;
> Host Name (string);
> Service Description (string);
> Status (OK/WARNING/CRITICAL/UNKNOWN);
> Retry number (#/#);
> State Type (SOFT/HARD);
> Last check time (long time);
> Next check time (long time);
> Check type (ACTIVE/PASSIVE);
> Checks enabled (0/1);
> Accept Passive Checks (0/1);
> Event Handlers Enabled (0/1);
> Last state change (long time);
> Problem acknowledged (0/1);
> Last Hard State (OK/WARNING/CRITICAL/UNKNOWN);
> Time OK (long time);
> Time Unknown (long time);
> Time Warning (long time);
> Time Critical (long time);
> Last Notification Time (long time);
> Current Notification Number (#);
> Notifications Enabled (0/1);
> Latency (#);
> Execution Time (#);
> Flap Detection Enabled (0/1);
> Service is Flapping (0/1);
> Percent State Change (###.##);
> Scheduled Downtime Depth (# - 0/1 ???);
> Failure Prediction Enabled (0/1 ???);
> Process Performance Date (0/1);
> Obsess Over Service (0/1);
> Plugin Output (string)
>
> Program line (second line of log):
>
> [Current Time] PROGRAM;
> Program Start Time (long time);
> Nagios PID (#);
> Daemon Mode (0/1);
> Last Command Check (long time);
> Last Log Rotation (long time);
> Notifications Enabled (0/1);
> Execute Service Checks (0/1);
> Accept Passive Service Checks (0/1);
> Enable Event Handlers (0/1);
> Obsess Over Services (0/1);
> Enable Flap Detection (0/1);
> Enable Failure Prediction (0/1 ???);
> Process Performance Data (0/1)
>
> --
> Russell Scibetti
> Quadrix Solutions, Inc.
> http://www.quadrix.com
> (732) 235-2335, ext. 7038
>
>
Ethan Galstad,
Nagios Developer
---
Email: nagios@nagio
...[email truncated]...
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: nagios@nagios.org