amreport(1M) amreport(1M)
NAME
amreport - produce statistical and event reports from availmon logfile
SYNOPSIS
/usr/etc/amreport [ -r | -e | -d | -p ] [ -l locallogfile ]
[ -f time ] [ -t time ] [ -c ]
/usr/etc/amreport [ -r | -e | -d | -p ] -s sitelogfile [ -c ]
/usr/etc/amreport { -v | -1 }
DESCRIPTION
amreport reviews saved availmon(5) report information and provides
statistical and event history reports. By default, amreport processes
the availability data on the local system, which is saved automatically,
whether or not sending availmon email reports is enabled (see
amconfig(1M)). amreport can also process received aggregate availmon
reports; that is, an appended accumulation of availmon reports from
different systems, referred to as a site logfile.
amreport can be run interactively or it can generate statistical or event
history reports that are written to standard output. Interactively, it
presents a statistical summary and allows hierarchical selection and
display of the list of events or detail on particular events. Run
interactively on a site logfile, amreport presents the same statistical
or event information, either on all systems or on individual systems. In
both cases, amreport can generate statistical, event list, event detail
or combined reports that are written to standard output.
The first synopsis is for reporting local availmon information. If any
of the -r, -e, -d or -p options are given, amreport writes the
corresponding report to standard output. Otherwise, amreport runs
interactively using curses(3X) for screen control. In either case, the
-f time or -t time options can be used to delimit the "from" and/or "to"
times for the report. By default, amreport uses /var/adm/avail/availlog.
The options for local availmon reporting include:
-r Write a statistical report to standard output
-e Write an event list report to standard output
-d Write an event detail report to standard output
-p Write a combined report to standard output, including
the statistical report followed by the event list
report
-l locallogfile Specify a local logfile. By default,
/var/adm/avail/availlog is used
-f time Specify the "from", or start, time for the report.
time is specified in the same format as the touch(1) -t
argument
Page 1
amreport(1M) amreport(1M)
-t time Specify the "to", or stop, time for the report. time
is specified in the same format as the touch(1) -t
argument
-c Exclude the current uptime from the reports (since the
last boot)
The second synopsis is for reporting from site logfiles. As with local
reporting, if any of the -r, -e, -d or -p options are given, amreport
writes the corresponding report to standard output. Otherwise, amreport
runs interactively using curses(3X) for screen control. The -s option
must be used to specify the sitelogfile. Time specification is not
supported on site logfiles.
The options for site logfile reporting include:
-r Write a statistical report to standard output
-e Write an event list report to standard output
-d Write an event detail report to standard output
-p Write a combined report to standard output, including
the statistical report followed by the event list
report
-s sitelogfile The site logfile must be specified
-c Exclude the current uptime from the reports (since the
last boot)
The third synopsis is for several additional options:
-v Write out the version of the availmon(5) set of
programs
-1 Read a single availability report from standard input
and write it out to standard output in the same format
as the event detail report
The -1 option can be used to make a single availability report more
readable. It can be used, for example, in a mail alias to filter the
result of amreceive(1M) before piping it to a mailer.
Availmon reports center around event records. Any system reboot is an
availmon event, whether a controlled shutdown or an "unscheduled" reboot,
such as a power interruption or a "crash". An event record contains the
time at which the system was previously booted, which starts the event
period, the time the event occurred, which ends the period of "uptime",
the reason for the event, and the time that the system was rebooted. If
the system stopped as a result of a hang, the exact instant at which it
stopped is not easily known; this time is estimated by a ticker daemon
Page 2
amreport(1M) amreport(1M)
normally accurate to within 5 minutes of the actual uptime. If the
ticker daemon is not enabled (see amconfig(1M)), the down time is assumed
to be 1 minute.
In an event list display, the fields shown are "Start Time" (when the
system was previously booted), the "Incident Time", when the event
occurred, the uptime and downtime in minutes, and a very brief
description of the event code, or cause of the event. In an event detail
display, the information is shown more readably on multiple lines,
including a complete event code description.
System statistics cover the aggregation of events for the given system.
Events are grouped as either "Unscheduled" or "Service Action"
(controlled shutdown) events, and are broken down into categories within
those two groups. In a statistics display, for each category in which
there was at least one event, the display includes the count of events in
that category, the total downtime (in minutes), the MTBI, or mean time
between "interrupts" and the availability as a percentage. MTBI and
availability per category are computed for events within the category as
applied to the entire time period of the report. Count, total downtime,
MTBI and availability are also displayed for the two groups, and the
final total over all events.
The average, least and most uptimes and downtimes are also included, as
well as when logging started (which is effected by use of the -f option),
when the last boot occurred (which is effected by use of the -t option),
and how long the system has been up since the last boot. Uptime since
the last boot is excluded from statistics if the -c option is used.
FILES
/var/adm/avail/availlog local log file of where local availability data
is automatically saved
SEE ALSO
amconfig(1M), amparse(1M), amsyslog(1M), amtickerd(1M), amtime1970(1M),
touch(1), curses(3X), availmon(5).
Page 3