Customizations to the following built-in configuration files (all in the conf directory) will remain in the upgraded or patched Analytics node:
Customizations to other Platform Analytics files might not remain in an upgrade or patched Platform Analytics node. Therefore, in order to meet Platform Analytics node conventions, customizations to the Platform Analytics node cannot overwrite any Platform Analytics files not in this supported list.
If you customize an existing data loader, do not directly overwrite the built-in binaries. Instead, you can edit the source code, make file, or build.xml file to build binaries with different names by following the naming conventions.
The following describes an example to customize the lsfpendingreasonloader to obtain more information for detailed pending reasons:
For example, the relevant directories and files are as follows:
The loader controller configuration file related to the pending reason data loader. This file may be modified for the new data loader.
Library files collecting Platform LSF 7.0 data.
Similarly, the ego directory contains library files collecting EGO-related data, and the license directory contains library files collecting license-related data.
Add a new data loader to collect custom data from the cluster.
For example, to create the License Scheduler workload data loader with serial number 148782, add the following files to the following relevant directories:
plc/plc_ls_workload_148782.xml
A standalone loader controller configuration file for the new data loader.
Library files collecting Platform LSF License Scheduler 7.0 data.
Similarly, the ego directory contains library files collecting EGO-related data, and the lsf directory contains library files collecting LSF-related data.