HP Integrity NonStop H-Series Podręcznik Użytkownika Strona 101

  • Pobierz
  • Dodaj do moich podręczników
  • Drukuj
  • Strona
    / 346
  • Spis treści
  • BOOKMARKI
  • Oceniono. / 5. Na podstawie oceny klientów
Przeglądanie stron 100
HP NonStop Shadowbase Command Definitions
Collector Command Descriptions
HP NonStop Shadowbase Command Reference Manual—785421-002
92
AUDMON shows the AUDMON process controlling the Collector.
DURATION shows the time duration for the statistics. Either from the initial
startup of the COLL or from the last RESET.
Notes:
If the lag is greater than 100 hours, it will be displayed as “>100
HOURS”.
If the Collector/Consumer is caught up, zeros will be shown.
If there are no messages busy or queued for a Consumer, the lag
times will be blank.
If the Collector has been suspended via AUDCOM, the lag times will
show “NOT READING”.
If a Consumer is not in a state to receive messages (e.g., it has been
suspended via AUDCOM), the lag times will show “NOT PROC.”
(meaning not processing).
The following is an example using the DETAIL option (the new
information is in bold).
The timestamps, and latencies output are computed and displayed in
<hours>:<minutes>:<seconds>. <milliseconds> format. It should be
noted that many of these timestamps are generated using audit trail
event timestamps, which are notoriously inexact. Deviations of a few
seconds (to as much as a minute) of ‘inexact drift’ can occur. For busy
systems, the audit trail timestamps will generally be more accurate
than they are for less-busy systems.
Due to the audit trail event timestamp inaccuracies described above,
lag statistics may show far greater latency than what is actually
occurring.
LATENCY WARNING STATUS – This section indicates the current
status. Possible values are: ENABLED, DISABLED, BEHIND or
CAUGHT UP. These last two states will only appear if the
LATENCYTHRESHOLD parameter is set greater than 0. In this case, it
also indicates the time it entered this state.
ETS shows the timestamp of the oldest unacknowledged event sent to the
Consumer. The LTS (latency, or latest, timestamp) Shows the timestamp
of last event read from the audit trail.
ETS LAG (CUR) shows what the lag time is from the oldest event being
tracked to the current wall clock time. In this context, tracked events are
the events that have been read from audit, and are either queued to or
have been sent to a Consumer, but have not yet been ACK’d by that
Consumer It is not the same thing as the RESTARTFILE lag time (see
below), however it is possible that the oldest event being tracked by the
Collector is the oldest event for a current transaction (a transaction that
the Collector has not seen a commit or abort for).
LTS shows the timestamp of the last event read from the audit trail.
Przeglądanie stron 100
1 2 ... 96 97 98 99 100 101 102 103 104 105 106 ... 345 346

Komentarze do niniejszej Instrukcji

Brak uwag