1. Configure the Script monitoring.
2. Make sure the monitoring is working fine. The monitoring parameter should be visible on the TrueSight Presentation Server console.
3. Log in to the server where the PATROL Agent(PA) is installed.
Use PCIG tool to create a new script KM package with User-defined parameters.
Steps:
$cd /opt/bmc/Uninstall/tools/pcig
$mkdir -p Patrol3/lib/knowledge/
$cp /opt/bmc/Patrol3/lib/knowledge/TRO* Patrol3/lib/knowledge/
$./pcig.l64 -p tro -s Patrol3 -r <yyyymmdd> -t "Script KM custom monitor types"
The new KM package can be located as “tro_ALL_<yyyymmdd>.tar” under /opt/bmc/Uninstall/tools/pcig
PCIG tool document:
https://docs.bmc.com/docs/display/IU113/Building+and+packaging+custom+KMs
https://docs.bmc.com/docs/PATROL4Scripting/21/importing-custom-kms-to-configure-agent-and-server-thresholds-971636745.html?src=search
4.Import this package into TSPS Repository as a single solution. After that, a new version of script KM will be visible in the TSPS repository.
5.Add server or agent threshold in policy and use the new version. The customized parameter will be available to set the threshold
The steps will be the same for the Windows platform.
There is a known issue on Windows platform.
Before executing the pcig tool, check the "Patrol3/lib/knowledge/TROMS_Script_Custom_*_Instance.xml" file.
In the first line, the encoding should be utf-8, not utf-16.
Manually change it to utf-8