APC SU1400XLT User Manual Page 67

  • Download
  • Add to my manuals
  • Print
  • Page
    / 115
  • Table of contents
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 66
4. EVENTS
Debug logging consists of debug messages. Normally these are turned on only by developers, and
currently there exist very few of these debug messages.
Data Logging
This feature is somewhat outdated and not often used.
Data logging consists of periodically logging important data concerning the operation of the UPS. For the
definitive definition of the format, see log_data() in apcreports.c. The format varies according to the UPS
model and the information available from the UPS.
For UPS models, NBKPRO, SMART, SHARESMART, and MATRIX, the output is written in a format very
similar to what PowerChute writes. That is:
MinLineVoltage, MaxLineVoltage, OutputVoltage, BatteryVoltage, LineFrequency, LoadPercent,
UPSTemperature, AmbientTemperature, Humidity, LineVoltage, BatteryCharge, toggle
Any value that is not supported by your UPS such as AmbientTemperature and Humidity will be blank or
possibly as 0.0. In any case the commas before and after that field will still be output. The toggle value
alternates from 0 to 1 on each line. This was added at user request so that no two adjacent samples are
identical.
An actual example from the log file is:
Nov 2 12:43:05 matou apcupsd[23439]: 224.9,227.5,226.2,27.74,50.00,100.0,30.6,,,226.2,50.0,1
Status Logging
Status logging consists of logging all available information known about your UPS as a series of ASCII
records. This information is also made available by the apcupsd network information server.
For more details on STATUS logging, see the apcupsd Status Logging section for details.
EVENTS Logging
Events logging consists of logging events as they happen. For example, successful startup, power fail,
battery failure, system shutdown, ...
See the Customizing Event Handling section for more details.
Implementation Details
In order to ensure that the data logged to syslog() can be directed to different files, I have assigned
syslog() levels to each of our four types of data as follows:
1. DEBUG logging has level LOG_DEBUG
2. DATA logging has level LOG_INFO
3. STATUS logging has level LOG_NOTICE
4. EVENTS logging has levels LOG_WARNING, LOG_ERR, LOG_CRIT, and LOG_ALERT
It should be noted that more work needs to be done on the precise definitions of each of the levels for
EVENTS logging. Currently, it is roughly broken down as follows:
LOG_WARNING general information such as startup, etc.
LOG_ERR an error condition detected, e.g. communications problem with the UPS.
LOG_CRIT a serious problem has occurred such as power failure, running on UPS batteries, ...
LOG_ALERT a condition that needs immediate attention such as pending system shutdown, ...
Page view 66
1 2 ... 62 63 64 65 66 67 68 69 70 71 72 ... 114 115

Comments to this Manuals

No comments