Skip to Content

Troubleshooting

Review the troubleshooting information to resolve issues in PATROL for Synthetic Monitoring.

Enable log: While configuring the Synthetic monitoring, select the Enable logging check box to enable KM debugging. Ensure that you have the write permissions for the <PATROL_HOME>/stm/ directory on the PATROL Agent server, as the log file is created in the <PATROL_HOME>/stm/log directory.

The following table contains the issues that you may come across and probable actions to take:

Issue

Action

Instances are not discovered or attributes are not collecting data.

Check the monitoring status attribute value. If it is 1, the Java home or Python home directory path is incorrectly set. Correct the path.

Accuracy errors are not reported.

  • Make sure that you call the driver.verify_title() or driver.verify_data() methods before calling the driver.get() method.
  • Make sure that your Google Chrome browser has a compatible chromedriver.exe file installed on your computer.

If a given Playwright script fails to locate the browser and PATROL for Synthetic Monitoring fails to collect data by using the Playwright framework then

Specify the installation path of the respective browser with the following environment variable and restart the PATROL Agent:

PLAYWRIGHT_BROWSERS_PATH

For any other issues:

Check the log file at <PATROL_HOME>/stm/log directory.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC PATROL for Synthetic Monitoring 25.1