This documentation supports releases of BMC Helix Continuous Optimization up to December 31, 2021. To view the latest version, select the version from the Product version menu.

Collecting additional metrics using the Stackdriver monitoring

The Google Cloud Platform - GCP API Extractor collects a default set of performance metrics from your Google Cloud Platform infrastructure. In addition to the default metrics, you can use the Monitoring agent to collect additional data such as metrics and logs from third-party applications. These metrics are useful for investigating the capacity-related issues that might occur in your Google Cloud environment. When you run the GCP API ETL, these metrics are imported into the BMC Helix Continuous Optimization database. 

Before installing the Monitoring agent, you must create and enable a Stackdriver account. A Stackdriver account contains the monitoring and other configuration information about Google Cloud Platform projects. To collect Stackdriver metrics, your GCP projects must be associated with a Stackdriver account. You can associate projects while creating a Stackdriver account or can associate them later. You can create any number of Stackdriver accounts.

  1. Create a Stackdriver account.

    1. Log in to the Google Cloud Platform console with your Google account credentials.
    2. From the project list at the upper-left corner next to Google Cloud Platform, select the project that you want to enable for Stackdriver monitoring.
    3. In the left navigation pane, click Monitoring under Stackdriver.
    4. Select Create a new Stackdriver account, and click Continue.
    5. On the Create your free Stackdriver account page, verify the project name in the Google Cloud Platform project list, and click Create Account.
    6. (Optional) Select additional Google Cloud Platform projects that you want to enable for Stackdriver monitoring, and click Continue.
    7. (Optional) Add AWS accounts to monitor as a part of this Stackdriver account. Otherwise, click Skip AWS Setup.
    8. Read the instructions for installing Stackdriver agents, and click Continue.
    9. On the Get Reports by Email page, select a frequency of receiving the performance report by email, and click Continue.
    10. After you gather the required information, click Launch Monitoring.
      The Stackdriver Monitoring page is displayed, which indicates that your Stackdriver account is ready for use.
  2. Install the Monitoring agent on each of your virtual machines.
    The Monitoring agent is available only with the Premium Tier subscription of Stackdriver.
    • For the installation instructions, see  Installing the Monitoring Agent Open link
    • For information about the service tiers for Stackdriver accounts, see   Service tiers for Stackdriver accounts Open link
  3. Configure and run the ETL. For more information, see Google Cloud Platform - GCP API ETL.
  4. Verify that the metrics are displayed in the Workspace.

Performance metrics from the agent

The following table contains the performance metrics that you get after installing the Monitoring Agent and enabling the Stackdriver monitoring. The following metric type names must be prefixed with agent.googleapis.com/That prefix has been omitted so that the names fit within the table.

BMC Helix Continuous Optimization metric

Display name (Google Cloud metric type)

Operating system
(Linux/Windows/Both)

StatisticDataTypeSub metric label keySub metric label valueSub resource label keyReducerGroupBy Fields
BYFS_USED_SPACE_PCT

Disk utilization (disk/percent_used)

BothALIGN_MEANDOUBLEStateState

device

Devices that end with fs are excluded.



BYFS_USED

Disk usage (disk/bytes_used)

LinuxALIGN_MEANDOUBLEStateUsed

device

Devices that end with fs are excluded.



BYFS_FREE

Disk usage (disk/bytes_used)

LinuxALIGN_MEANDOUBLEStateFree

device

Devices that end with fs are excluded.



BYFS_SIZE

Disk usage (disk/bytes_used)

LinuxALIGN_MEANDOUBLEState(Used + Free)

device

Devices that end with fs are excluded.



TOTAL_FS_USED

Disk usage (disk/bytes_used)

LinuxALIGN_MEANDOUBLEStateUsed

device

Devices that end with fs are excluded.



TOTAL_FS_FREE

Disk usage (disk/bytes_used)

LinuxALIGN_MEANDOUBLEStateFree

device

Devices that end with fs are excluded.



TOTAL_FS_SIZE

Disk usage (disk/bytes_used)

LinuxALIGN_MEANDOUBLEState(Used + Free)

device

Devices that end with fs are excluded.



TOTAL_FS_UTIL

Disk usage (disk/bytes_used)

LinuxALIGN_MEANDOUBLEState(Used / (Used + Free))

device

Devices that end with fs are excluded.



BYDISK_SERVICE_TIME

Disk average I/O time (disk/io_time)

LinuxALIGN_DELTAINT64

device

Devices that do not end with a digit are excluded.



BYDISK_PHYS_IO_READ_RATE

Disk operations (disk/operation_count)

LinuxALIGN_RATEDOUBLEDirectionRead

device

Devices that do not end with a digit are excluded.



BYDISK_PHYS_IO_WRITE_RATE

Disk operations (disk/operation_count)

LinuxALIGN_RATEDOUBLEDirectionWrite

device

Devices that do not end with a digit are excluded.



BYDISK_PHYS_IO_RATE

Disk operations (disk/operation_count)

LinuxALIGN_RATEDOUBLE
(Read + Write)

device

Devices that do not end with a digit are excluded.



DISK_IO_BLOCKED

Disk pending operations (disk/pending_operations)

LinuxALIGN_RATEDOUBLE

device

MEM_REAL_USED

Memory utilization (memory/percent_used)

TOTAL_REAL_MEM

BothALIGN_MEANDOUBLEState(Used + Slab)


MEM_CACHED

Memory utilization (memory/percent_used)

TOTAL_REAL_MEM

BothALIGN_MEANDOUBLEStateCached


MEM_BUFFERED

Memory utilization (memory/percent_used)

TOTAL_REAL_MEM

BothALIGN_MEANDOUBLEStateBuffered


MEM_FREE

Memory utilization (memory/percent_used)

TOTAL_REAL_MEM

BothALIGN_MEANDOUBLEState(Used + Slab + Cached + Buffered)


MEM_REAL_UTIL

Memory utilization (memory/percent_used)

BothALIGN_MEANDOUBLEState(Used + Slab)


MEM_USED

Memory utilization (memory/percent_used)

TOTAL_REAL_MEM

BothALIGN_MEANDOUBLEState(Used + Slab + Cached + Buffered)


MEM_UTIL

Memory utilization (memory/percent_used)

BothALIGN_MEANDOUBLEState(Used + Slab + Cached + Buffered)


MEM_UTIL_CACHED

Memory utilization (memory/percent_used)

BothALIGN_MEANDOUBLEStateCached


SWAP_SPACE_USED

Swap usage (swap/bytes_used)

BothALIGN_MEANDOUBLEStateUsed
REDUCE_SUMresource.labels.instance_id
SWAP_SPACE_FREE

Swap usage (swap/bytes_used)

BothALIGN_MEANDOUBLEStateFree
REDUCE_SUMresource.labels.instance_id
SWAP_SPACE_TOT

Swap usage (swap/bytes_used)

BothALIGN_MEANDOUBLE


REDUCE_SUMresource.labels.instance_id
SWAP_SPACE_UTIL

Swap usage (swap/bytes_used)

Swap usage (swap/bytes_used)

Both

ALIGN_MEAN

ALIGN_MEAN

DOUBLE

DOUBLE

StateUsed

REDUCE_SUM

REDUCE_SUM

resource.labels.instance_id

resource.labels.instance_id

NET_CONNECTIONS_CURRENT

TCP connections (network/tcp_connections)

BothALIGN_MEANDOUBLETCP_stateEstablished


CPU_UTIL_USER

CPU utilization (cpu/utilization)

LinuxALIGN_MEANDOUBLECPU_stateUser


CPU_UTIL_SYSTEM

CPU utilization (cpu/utilization)

LinuxALIGN_MEANDOUBLECPU_stateSystem


CPU_UTIL_IDLE

CPU utilization (cpu/utilization)


BothALIGN_MEANDOUBLECPU_stateIdle


CPU_UTIL_WAIT

CPU utilization (cpu/utilization)


LinuxALIGN_MEANDOUBLECPU_stateWait


CPU_UTIL_GUEST

CPU utilization (cpu/utilization)


WindowsALIGN_MEANDOUBLECPU_stateUsed


For more information, see the Google Cloud Agent metrics Open link documentation. 


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

Comments