This section provides information about issues and instructions for how to resolve or work around the issues.
Setting environment debugging options
To enable debugging, in BMC ProactiveNet Central Monitoring Administration, perform the following steps:
Log in to Central Monitoring Administration. On the All Monitoring policies page, select an existing policy, for which you want to enable debugging, and click Edit.
On the Monitor Policy Configuration page, select the Monitor Configuration check box.
On the Monitoring Configuration page, select an existing policy for which you want to enable debugging and click Edit.
Expand KM admin tab and select Data collection logging check box. This enables data collection logging of the selected policy. The logs are saved in the .../Patrol3/logdirectory, the PATROL Agent log directory. The BMC PATROL for MongoDB log files are prefixed with PLB.
For information about troubleshooting issues in BMC ProactiveNet, see Troubleshooting.
Setting global debugging options
To enable debugging, in BMC ProactiveNet Central Monitoring Administration, perform the following steps:
Log in to Central Monitoring Administration. On the All Monitoring policies page, select an existing policy, for which you want to enable debugging, and click Edit.
On the Monitor Policy Configuration page, select the Monitor Configuration check box.
On the Monitoring Configuration page, select an existing policy for which you want to enable debugging and click Edit.
Select check box at global setting. This will set ON PSL debug in a global level.
Verifying the environment details by using the tool we have in the KM for UNIX envChecker.sh and for Windows envChecker.bat
You can run this tool in command line and it will prompt for configuration information ( host , port …), in case everything is fine it will show the discovery report and in case if there is a problem it will show an error. This tool can be used before starting the configuration to check the information or in case of a failure .