Juniper MEDIA FLOW MANAGER 2.0.2 - ADMINISTRATOR S GUIDE AND CLI, Руководство администратора

Страница: 143 / 156

stats 143
Media Flow Manager Administrator’s Guide CHAPTER 5 CLI Commands
•
filename <filename>
—If a
filename
is specified, the stats are exported to a file of
that name; otherwise a name is chosen automatically and contains the name of the
report and the time and date of the export. Any automatically-chosen name is given a
.csv
extension. If the user specifies a name,
.csv
is added if it is not already part of
the name. The word
custom
should be a reserved report name (no reports should be
named that) to leave room in the command set for later allowing you to specify
manually which series to export. If the filename is specified, it must come just after the
report name. If the
after
and/or
before
arguments are specified, they may come in
either order relative to each other.
•
sample <sample_ID>
—Configure sampled statistics. See “stats samples," next, for a list
of supported samples.
•
clear
—Clear all data from this sample series.
•
interval
—Set the amount of time in seconds (1 - 2147483647) between sample
polling for the specified group of sample data.
show stats
alarm [<alarm_ID>]
chd [<CHD_ID>]
cpu
sample [<sample_ID>]
Notes:
•
alarm
—Status of all alarms or the specified alarm, whether or not it is in an error state.
•
chd
—Statistics CHDs settings.
•
cpu
—Basic statistics about CPU utilization: the current level, the peak over the past hour,
and the average over the last hour.
•
sample
—Sampling interval for all samples, or the specified one.
stats alarms
Enable or disable the specified alarm with
stats alarm <alarm_ID> enable
; the
no
variant
disables the specified alarm. Set a threshold value for each alarm using the
stats alarm
<alarm_ID> rising
or
stats alarm <alarm_ID> falling
commands; the alarm is triggered
when the specified threshold is reached. Alarms that can be enabled or disabled are described
in
Table 6 , below.
stats alarm rate-limit count
Specify three time limits for tracking and, potentially, limiting how many of this type of alarm to
send. The duration and count of each bucket for
short
,
medium
, and
long
are meant to be
ordered such that the
short
bucket has the smallest time duration (
window
) and smallest
maximum allowed
count
. The
rate-limit
applies to all three buckets simultaneously. Separate
counts of alarms are kept for
error
alarm events and
clear
alarm events. For each alarm type,
a single skip count is kept and is reported when the alarm event is later sent. When an alarm
event count is exceeded for any bucket, only the skipped count is incremented (not any of the
alarm event counts). For example, if the
short
bucket allows 5 alarm events per 5 minutes, the
sixth alarm and above that occur during the 5 minute window only increment the skip count.