User guide

22
heartbeat-
frequency
The number of seconds between each
client heartbeat message to the LCE
server. If “0”, it will not send heartbeats.
A positive integer.
0
300
statistics-
frequency
The number of minutes between each
client host performance statistics report to
the LCE server. If “0”, it will not send
statistics.
A positive integer.
0
60
compress-events
Whether or not to compress events before
transmitting them to the LCE server.
Marginally saves bandwidth, marginally
increases CPU usage.
0 or 1
(0=off,1=on)
0
1
log-directory
The path to which the LCE Client writes its
own log file (startup information, errors,
warning, and optional debug information).
A full path name.
/opt/lce_client/
client-debug
Reports additional debugging information if
this key is present.
There are no values
needed here; the key will
be empty.
N/A
Performance Reporting
When the LCE Client sends performance statistics to the LCE server, the exact information sent depends on the operating
system (e.g., swap and cache data is not available on all platforms). The various performance logs are normalized to the
“lce” event type for easy analysis. When viewed using the Raw Syslog Events tool, the data appears similar to the
following screen capture:
This data is very useful for troubleshooting performance issues on the remote LCE Client. Used in conjunction with the
“process” LCE event type that hourly monitors and reports on system processes, runaway processes can be quickly
debugged and resolved before they completely take the LCE client system down.