Troubleshooting

This topic describes how to troubleshoot issues for PATROL for Google Cloud Compute.


Enabling KM debug

If you encounter certain problems using this KM, BMC Support might request that you enable KM debug.

Using TrueSight console

In KM configuration, select the Enable Logging check box to enable debug. You can select the level of logs by using the Log Level (FINE, FINER, FINEST) option. FINEST level logs each debug log record.

Note: If debug is disabled, the log file contains only warning level log records.

Using pconfig variables

  1. Access the /GCP/Projects/<project_ name>/DEBUG pconfig variable
  2. Set this variable to 1 to enable the debug, and set to 0 to disable the debug.

The log files are located at <PATROL_HOME>/gcc/log location on the PATROL Agent server. The log file name is <PATROL Agent>-<port>-<project-ID>-GCPCollector.log.

Other issues

In the case of failures, check the annotation messages for errors, probable causes and possible corrective actions of the attributes in the same order as mentioned below. 

Monitor typeAttribute

Google Cloud Compute (GCP)

Configuration Status

Google Cloud Platform Project (GCP_PROJECT)

Monitoring Status

Google Compute Engine (GCP_GCE)

Collection Status

Was this page helpful? Yes No Submitting... Thank you

Comments