Configuring Google Cloud Compute in TrueSight

Use the Add Monitoring Configuration page in the TrueSight console to configure PATROL for Google Cloud Compute and monitor your Google Cloud Platform project.

From the Google Cloud Platform Project Details page, you can achieve the following goals:

  • Configure Google Cloud Platform project for monitoring
  • Enable or disable monitoring of Compute Engine service
  • Include or exclude the Zones and Virtual Machine instances from monitoring
Reference information

 Definitions (Monitor profile, Monitor type)

Monitor Profile: Monitor profiles are profiles to which the monitor types, also known as application classes, you want to enable are associated. Each solution contains multiple monitor profiles and help to reduce unnecessary monitoring. Each monitor profile is associated with a group of monitor types. The monitor types that belong to a profile are pre-determined. You cannot add or remove monitor types from a profile.

Monitor Type: Monitor Types are similar to application classes in that they are the object classes to which application instances belong. In ProactiveNet and TrueSight Operations Managementmonitor types are similar to application classes. Monitor types are a way of classifying the data that is to be collected.

Before you begin

To configure Google Cloud Compute KM (video)

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

 https://youtu.be/PpSa8BP9oHk

Note

The steps to identify the google cloud platform project ID, create a service account key, and configure the KM are same for PATROL for Google Cloud Compute. Select the following options to configure the KM:

Monitoring Solution: Google Cloud Compute

Version: 1.0

Monitor Profile: Google Cloud Compute

Monitor Type: Google Cloud Compute

To configure Google Cloud Compute KM (steps)

  1. Access the Infrastructure Policies tab on the TrueSight console
    1. Log on to the TrueSight console.
    2. Expand the Configuration menu and select Infrastructure Policies.
      The Infrastructure Policies page is displayed. 
    3. Click Create Policy
      The Create Monitoring Policy page is displayed.
    4. Enter the policy details as described in the Defining a monitoring policy section. 

  2. Set the JAVA Home location and enable device mapping of the Compute VM instances

    Administration

    FieldDescription
    JAVA Home (1.8 or above)

    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.


  3. Define the configuration for the Google Cloud Project
    Specify the values for the following fields to configure your Google Cloud Project.

    FieldDescription
    Google Cloud Platform Project Details
    Project IDEnter the ID of the Google Cloud Platform project.
    Service Account Key File NameEnter 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>/gcc/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.


  4. Enable or disable monitoring of Compute Engine service 

    Monitor the Compute Engine service

    FieldDescription
    Compute Engine Configuration
    Compute EngineSelect 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.


  5. Include or exclude Zones and Virtual Machine instances from monitoring
    Configure filters to include or exclude Google Cloud zones and virtual machines from the Compute Engine configuration.

    FieldDescription
    Zone Filter
    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 matching 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 Google Cloud Platform Documentation

    Compute Engine Filter
    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.*


  6. KM Administration

    FieldDescription
    JVM AgrumentsEnter the additional Java Virtual Machine arguments for the Java collector.
    Enable LoggingSelect this check box to enable the debug. The log files are located at <PATROL_HOME>/gcc/log location on the PATROL Agent server.
    Log LevelSelect 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.

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

Comments