Configuring Google Cloud Platform
Before you begin
- Make sure that your computer meets all the requirements listed in the System-requirements topic.
- Make sure that you have the project ID and the Service Account JSON key of the Google Cloud Platform project that you want to monitor. For information about how to create a service account key, see Creating-a-Service-Account-Key-in-the-Google-Cloud-Platform-project.
- Make sure that you have created the monitoring policy for this configuration. For information about to create a monitoring policy, see Defining-a-monitoring-policy.
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.
To configure Google Cloud Platform
- In BMC Helix Operations Management, select Configuration > Monitor Policies > Create Policy.
- On the Create Monitoring Policy page, select the Monitoring tab and click Add Monitoring Configuration.
- From the Monitoring Solution list, select Google Cloud Platform.
- From the Monitor Profile and Monitor Type lists, select Google Cloud Platform.
- In the Google Cloud Platform Project Details section, click Add.
- Add the monitoring configuration as described in the following table:
| Field | Description |
|---|---|
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:
|
| Compute Engine Filter | Expand the Compute Engine Filter field to configure the VM instances:
|
| App Engine | Select 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:
|
| Cloud SQL Configuration | Expand the Cloud SQL Configuration field to configure the following database services:
|
| Cloud Functions Configuration | Cloud 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:
|
| 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:
|
| 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 Type | Select 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.
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.
Note: If you modify this field, restart the PATROL Agent to apply the changes. |
- Click Ok and Close.