LSF Version 7.3 - Administering Platform LSF

Reports Administration
638 Administering Platform LSF
◆ UNIX: LSF_CONFDIR/ego/cluster_name/eservice/esc/conf/services
◆ Windows: LSF_CONFDIR\ego\cluster_name\eservice\esc\conf\
services
Loader controller The loader controller manages the data loaders. By default, the loader controller
manages the following data loaders:
◆ bldloader (License Scheduler data loader)
◆ desktopjobdataloader (Desktop job data loader)
◆ desktopclientdataloader (Desktop client data loader)
◆ desktopeventloader (Desktop active event data loader)
◆ egoconsumerresloader (consumer resource data loader)
◆ egodynamicresloader (dynamic metric data loader)
◆ egoeventsloader (EGO allocation events data loader)
◆ egostaticresloader (static attribute data loader)
◆ lsfbhostsloader (bhosts data loader)
◆ lsfeventsloader (LSF events data loader)
◆ lsfslaloader (SLA data loader)
◆ lsfresproploader (LSF resource properties data loader)
◆ sharedresusageloader (share resource usage data loader)
You can view the status of the loader controller service using the loader controller
client tool as described in View the status of the loader controller on page 641.
Log files for the loader controller and data loaders are available in the
PERF_LOGDIR
directory. There are logging levels that determine the detail of messages recorded in
the log files. In decreasing level of detail, these are
ALL (all messages), TRACE, DEBUG,
INFO, WARN, ERROR, FATAL, and OFF (no messages). By default, all service log files log
messages of
INFO level or higher (that is, all INFO, WARN, ERROR, and FATAL
messages). You can change the logging level of the
plc service using the loader
controller client tool as described in Dynamically change the log level of your
loader controller log file on page 642, or the logging level of the data loaders using
the client tool as described in Dynamically change the log level of your data loader
log files on page 642.
To balance data accuracy with computing power, you can change how often the data
loaders collect data by changing the frequency of data collection per loader, as
described in Change the frequency of data collection on page 647. To reduce the
amount of unwanted data logged in the database, you can also disable individual
data loaders from collecting data, as described in Disable data collection for
individual data loaders on page 648.
If you edit any
plc configuration files, you need to restart the plc service.
If your cluster has PERF controlled by EGO, you can edit the
plc_service.xml
service configuration file, but you must restart the
plc service and EGO on the
master host after editing the file. The
plc_service.xml file is located in the EGO
service directory:
◆ UNIX: LSF_CONFDIR/ego/cluster_name/eservice/esc/conf/services