Configuring Google Cloud Platform


Monitor your Google Cloud Platform (GCP) environment by configuring the PATROL for Google Cloud Platform KM to collect essential performance and availability data across key services. This setup provides streamlined visibility into Compute Engine, App Engine, Cloud SQL, Cloud Functions, and Kubernetes resources, enabling efficient oversight and proactive issue management.

Before you begin

To configure Google Cloud Platform (video)

Click to view a short video (3:58) of how to configure Google Cloud Platform KM to monitor your project.

icon_play.png https://youtu.be/PpSa8BP9oHk

To configure Google Cloud Platform

  1. In BMC Helix Operations Management, select Configuration > Monitor Policies > Create Policy.
  2. On the Create Monitoring Policy page, select the Monitoring tab and click Add Monitoring Configuration.
  3. From the Monitoring Solution list, select Google Cloud Platform.
  4. From the Monitor Profile and Monitor Type lists, select Google Cloud Platform.
  5. In the Google Cloud Platform Project Details section, click Add.
  6. Add the monitoring configuration as described in the following table:
FieldDescription

Project ID

Enter the ID of the Google Cloud Platform project.

Service Account Key File Name 

Enter the name of the Service Account Key file that is associated with the project ID. The Service Account Key file must be present in the <PATROL_HOME>/gcp/key directory on the PATROL Agent server. For information about how to create a service account key, see Creating-a-Service-Account-Key-in-the-Google-Cloud-Platform-project.

Compute Engine

Select this check box to enable monitoring of the Compute Engine service. By default, this service is enabled for monitoring. The KM checks the availability of the virtual machine instances and monitors the performance of CPU, Disk, and Network resources of the virtual machine instances.

Zone Filter

Expand the Zone Filter field to configure Google Cloud Platform zones for monitoring:

  • Zone Filter TypeSelect whether to Include or Exclude the Google Cloud Platform zones from monitoring.
  • Zone Name Filter—Enter the name of the Google Cloud Platform zone that you want to include or exclude from monitoring.

    You can enter the exact internal zone name provided by Google Cloud Platform, or a regular expression that matches multiple zones. To add multiple zones, enter a pipe-separated list of internal zone names.

    Filtering examples:

    • Example 1:To filter a single zone us-west1-b, enter the zone name as us-west1-b
    • Example 2:To filter zones asia-east1-c and us-east1-b, enter the regular expression as asia-east1-c|us-east1-b
    • Example 3:To filter all the zones from the South America region, enter the regular expression as southamerica.*
      Note: For the complete list of Regions and Zones, refer to Google Cloud Platform Documentation

    ​​​​

Compute Engine Filter

Expand the Compute Engine Filter field to configure the VM instances:

  • VM Instance Filter TypeSelect whether to Include or Exclude VM instances from monitoring.
  • VM Instance Name Filter—Enter the VM instance name that you want to include or exclude from monitoring.

    You can enter the exact VM instance name or a regular expression matching multiple VM instances. To add multiple entries, enter a pipe-separated list of the VM instance names.

    Filtering examples:

    • Example 1:To filter a single VM instance TestVM-1, enter the name as TestVM-1
    • Example 2:To filter VM instances DebianVM-3 and UbuntuVM-7 enter the regular expression as DebianVM-3|UbuntuVM-7
    • Example 3:To filter all the VM instances that start with the word Linux, enter the regular expression as Linux.*
App EngineSelect this checkbox to enable monitoring of the App Engine service. The KM monitors the active versions of the deployed services. It also monitors the performance of CPU, Disk, Memory, and Network resources of the App Engine service.
App Engine Filter

Expand the App Engine Filter field to configure the App Engine services:

  • Service Filter TypeSelect whether to Include or Exclude App Engine services from monitoring.
  • App Engine Service Name Filter—Enter the App Engine service name that you want to include or exclude from monitoring.

    You can enter the exact service name or a regular expression matching multiple services. To add multiple entries, enter a pipe-separated list of the service names.

    Filtering examples:

    • Example 1:To filter a single Service, AnalyzerService, enter the name as AnalyzerService
    • Example 2:To filter SchedulerService and AlertService services, enter the regular expression as SchedulerService|AlertService
    • Example 3:To filter all the services that start with the word Test, enter the regular expression as Test.*
Cloud SQL Configuration

Expand the Cloud SQL Configuration field to configure the following database services:

  • PostgreSQL Configuration
    • PostgreSQL—Select this option to enable PostgreSQL monitoring. Monitors the status of the PostgreSQL. 
    • PostgreSQL Filter Type—Select whether to Include or Exclude PostgreSQL from monitoring.
    • PostgreSQL Name Filter—Enter the PostgreSQL name that you want to include or exclude from monitoring. 

      You can enter the exact PostgreSQL name or a regular expression matching multiple PostgreSQL instances. To add multiple entries, enter a pipe-separated list of the PostgreSQL names.

      Filtering examples:

      • Example 1:To filter a single PostgreSQL, instance-1, enter the name as instance-1
      • Example 2:To filter PostgreSQL named 'instance' and 'sql', enter the regular expression instance|sql
      • Example 3:To filter all PostgreSQL databases that start with the word 'Test', enter the regular expression Test.*
  • MySQL Configuration
    • MySQL—Select this option to enable MySQL monitoring. Monitors the status of the MySQL. 
    • MySQL Filter Type—Select whether to Include or Exclude MySQL from monitoring.
    • MySQL Name Filter—Enter the MySQL name that you want to include or exclude from monitoring.

      You can enter the exact MySQL name or a regular expression matching multiple MySQL instances. To add multiple entries, enter a pipe-separated list of the MySQL names.

      Filtering examples:

      • Example 1:To filter a single MySQL, instance-1, enter the name as instance-1​​​​​​
      • Example 2:To filter MySQL named 'instance' and 'sql', enter the regular expression instance|sql
      • Example 3:To filter all MySQL that start with the word 'Test', enter the regular expression Test.*
  • SQLServer Configuration
    • SQLServer—Select this option to enable SQL Server monitoring. Monitors the status of the SQL Server. 
    • SQLServer Filter Type—Select whether to Include or Exclude SQLServer from monitoring.
    • SQLServer Name Filter—Enter the SQLServer name that you want to include or exclude from monitoring.

      You can enter the exact SQLServer name or a regular expression matching multiple SQLServer instances. To add multiple entries, enter a pipe-separated list of the SQLServer names.

      Filtering examples:

      • Example 1:To filter a single SQLServer, instance-1, enter the name as instance-1
      • Example 2:To filter SQLServer named 'instance' and 'sql', enter the regular expression instance|sql
      • Example 3:To filter all SQLServer that start with word 'Test', enter the regular expression Test.*
Cloud Functions ConfigurationCloud Functions—Select this check box to enable monitoring of the Cloud Functions service. The KM checks the status of the Cloud Function service and monitors execution time and execution count of the Cloud Functions.

Cloud Function Filter Type

Select whether to Include or Exclude Cloud Functions from monitoring.

Cloud Function Name Filter

Enter the Cloud Function name that you want to include or exclude from monitoring.

You can enter the exact Cloud Function name or a regular expression matching multiple Cloud Functions. To add multiple entries, enter a pipe-separated list of the Cloud Function names.

Filtering examples:

  • Example 1: To filter a single Cloud Function, TestFunction-1, enter the name as TestFunction-1
  • Example 2:To filter SayHello and TriggerEvent Cloud Functions, enter the regular expression as SayHello|TriggerEvent
  • Example 3:To filter all the Cloud Functions that start with the word Test, enter the regular expression as Test.*
Load Balancing Configuration

Configure how the Google Cloud load balancers are discovered and monitored. 

Load Balancing—Select this checkbox to enable load balancer monitoring.

Load Balancer Filter Type

Select Include if you want to monitor a load balancer specified in the Load Balancer Name Filter field.

Select Exclude if you don't want to monitor a load balancer specified in the Load Balancer Name Filter field.

Load Balancer Name Filter

Enter the load balancer name that you want to include or exclude from monitoring.

You can enter the exact load balancer name or a regular expression matching multiple load balancers. To add multiple entries, enter a pipe-separated list of the load balancer names.

Filtering examples:

  • Example 1: To filter the web-lb-1 load balancer, enter the following value: web-lb-1
  • Example 2: To filter the web-lb-1 and api-lb load balancers, enter the following regular expression: web-lb|api-lb
  • Example 3: To filter all load balancers that start with the word prod, enter the following regular expression: prod*
Kubernetes Engine Configuration

Configure this option to enable Kubernetes Engine monitoring. This monitors the status of the clusters, Nodes and Pods.

Kubernetes Engine—Select this checkbox to enable Kubernetes Engine monitoring.

Kubernets Engine Cluster Filter TypeSelect Include or Exclude to filter the clusters entered in the Kuberenetes Cluster Name Filter field.

Kubernets Cluster Name Filter

Enter the Kubernetes Cluster name that needs to be included or excluded from monitoring. It can be the exact name or a regular expression matching one or more Cluster names.

Example 1: To filter a Cluster named TestCluster-1, just enter TestCluster-1

Example 2: To filter Kubernetes Cluster named SayHello and TriggerEvent, enter the regular expression SayHello|TriggerEvent

Example 3: To filter all Clusters that start with word Test, enter the regular expression Test.*" id="KubernetesClusterFilterRegEx

Kubernetes Namespace Filter Type

Select Include or Exclude to filter the namespaces from the Kubernetes clusters.

Kubernetes namespace Filter

Enter the Namespaces name that needs to be included or excluded from monitoring. It can be the exact name or a regular expression matching one or more Namespace names.

Example 1: To filter a Namespace named kube-system, just enter kube-system

Example 2: To filter Namespace named SayHello and TriggerEvent, enter the regular expression SayHello|TriggerEvent 

Example 3: To filter all Namespaces that start with word Test, enter the regular expression Test.*" id="KubernetesNamspacesFilterRegEx

JVM Arguments

Enter the additional Java Virtual Machine arguments for the Java collector.

Enable Logging

Select this check box to enable the debug. The log files are located at <PATROL_HOME>/gcp/log location on the PATROL Agent server.

Log Level

Select the debug log level.

  • FINE
  • FINER
  • FINEST

FINEST level logs each debug log record.

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

JAVA Home

Enter the path to the JRE directory on the PATROL Agent server.

For example, if the JAVA location on the PATROL Agent server is /usr/java/jdk1.8.0_45/jre/bin/java path, specify /usr/java/jdk1.8.0_45/jre as the value in this field.

If the specified path does not exist or if this field is left blank, the KM searches for the JRE in the <PATROL_HOME> directory.

Enable Device Mapping

Select this check box to enable device mapping of the Compute VM instances. If this option is selected, the KM creates a device for each VM instance in the TrueSight console.

  • External DNS name - KM creates the virtual machine device by resolving DNS name from it's external IP address
  • VM instance name - KM creates the virtual machine device by using virtual machine instance name and internal IP address
  • Disabled - KM does not create the virtual machine device

     

Note: If you modify this field, restart the PATROL Agent to apply the changes.

  1. ​​Click Ok and Close.

 

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

BMC PATROL for Google Cloud Platform 26.1