Monitoring IBM PowerVC
After you install the Instana agent, IBM PowerVC sensor is installed automatically. You can view metrics that are related to IBM PowerVC in the Instana UI after you configure IBM PowerVC sensor as outlined in the Configuring section.
Supported information
Supported operating systems
The supported operating systems of the IBM PowerVC sensor are consistent with host agents requirements, which can be checked in the Supported operating systems section of each host agent, such as Supported operating systems for Unix.
Supported versions
IBM PowerVC sensor supports IBM PowerVC 2.x.x.
Currently, a maximum of two regions are supported per IBM PowerVC configuration.
Ports used by PowerVC sensor
Ensure that the following ports are exposed for PowerVC sensor to access the PowerVC APIs:
- Port 5000: Identity service (keystone) endpoint
- Port 8774: Compute (nova) endpoint
- Port 9000: Block storage (cinder) endpoint
- Port 9696: Networking (neutron) endpoint
For more information about port usage for PowerVC, see ports that are used by PowerVC on the management server.
Configuring
Restriction: Only remote monitoring is supported.
To connect to IBM PowerVC, you need to configure the following fields in the agent configuration file <agent_install_dir>/etc/instana/configuration.yaml. You can configure multiple IBM PowerVCs.
#PowerVC
com.instana.plugin.powervc:
remote: # multiple configurations supported
- host: '' # hostname or IP of powerVC server
port: '' # default port is '5000' of powerVC API Server
user: '' # username to access the powerVC server
password: '' # password to access the powerVC server
poll_rate: 15 # poll rate in seconds
project: ''
connectionTimeout: 50 # It is the timeout until a connection with the server is established. Default is 50 seconds.
connectionRequestTimeout: 50 # It is the time to fetch a connection from the connection pool. Default is 50 seconds.
socketTimeout: 50 # It is socket read time out. Default is 50 seconds.
The following example displays the configuration settings:
com.instana.plugin.powervc:
remote: # multiple configurations supported
- host: 'hostname-1' # hostname or IP of powerVC server
port: '5000' # default port is '5000' of powerVC API Server
user: 'user' # username to access the powerVC server
password: 'password' # password to access the powerVC server
poll_rate: 15 # poll rate in seconds
project: 'project'
connectionTimeout: 50 # It is the timeout until a connection with the server is established. Default is 50 seconds.
connectionRequestTimeout: 50 # It is the time to fetch a connection from the connection pool. Default is 50 seconds.
socketTimeout: 50 # It is socket read time out. Default is 50 seconds.
Viewing metrics
After you configure the sensor, you can view metrics that are related to IBM PowerVC in the Instana UI.
To view the metrics, complete the following steps:
- In the sidebar of the Instana UI, select Platform.
- Click IBM PowerVC, and then select a specific region.
You can now see the details of that region in the Summary tab. Each region has the following components. To view the metrics of each component, click its respective tab in the IBM PowerVC dashboard.
Region details
The following metrics are available for each region:
| Metric | Description | Granularity |
|---|---|---|
| Hostname | The hostname of the IBM PowerVC configuration. | 15 seconds |
| Host IP | The host IP of the IBM PowerVC configuration. | 15 seconds |
| CPU Usage by All VMs | The usage of CPU in percentage across all the virtual machines. | 15 seconds |
| Memory Usage by All VMs | The usage of memory in percentage across all the virtual machines. | 15 seconds |
| Storage Usage by All VMs | The usage of storage in percentage across all the virtual machines. | 15 seconds |
| Total Cores Used | The total number of CPU cores that are used across the specific region. | 15 seconds |
| Total Instances Used | The total number of instances that are used across the specific region. | 15 seconds |
| Total RAM Used | The total amount of RAM that is used across the specific region. | 15 seconds |
| Total Server Groups Used | The total number of server groups that are used across the specific region. | 15 seconds |
| Total Floating IPs Used | The total number of floating IPs that are used across the specific region. | 15 seconds |
| Total Security Groups Used | The total number of security groups that are used across the specific region. | 15 seconds |
Hypervisors metrics
The following metrics are available for each hypervisor:
| Metric | Description | Granularity |
|---|---|---|
| Name | The hypervisor name. | 15 seconds |
| ID | The hypervisor ID. | 15 seconds |
| Host IP | The IP address of the host. | 15 seconds |
| Type | The hypervisor type. | 15 seconds |
| CPU Usage | The usage of CPU in percentage. | 15 seconds |
| Total CPU | The total available CPU. | 15 seconds |
| Memory Usage | The usage of memory in percentage. | 15 seconds |
| Total Memory (GiB) | The total available memory. | 15 seconds |
| Storage Usage | The usage of storage in percentage. | 15 seconds |
| Total Storage (MiB) | The total available file system storage. | 15 seconds |
| Instance Count | The count of running virtual machine instances of the hypervisor. | 15 seconds |
| Status | The status of the hypervisor: enabled or disabled. | 15 seconds |
| State | The state of the hypervisor: up or down. | 15 seconds |
The following KPIs are available for each hypervisor on their respective dashboard:
| Metric | Description | Granularity |
|---|---|---|
| ID | The hypervisor ID. | 15 seconds |
| CPU Architecture | The CPU architecture information. | 15 seconds |
| CPU Model | The CPU model information. | 15 seconds |
| CPU Vendor | The CPU vendor information. | 15 seconds |
| CPU Cores | The number of CPU cores. | 15 seconds |
| Status | The status of the hypervisor: enabled or disabled. | 15 seconds |
| State | The state of the hypervisor: up or down. | 15 seconds |
| Host IP | The IP address of the hypervisor’s host. | 15 seconds |
| Hypervisor Type | The type of the hypervisor. | 15 seconds |
| Hypervisor Version | The version of the hypervisor. | 15 seconds |
The following time series graphs are provided for each hypervisor:
| Metric | Description | Granularity |
|---|---|---|
| CPU Usage | The usage of CPU in percentage. | 15 seconds |
| Memory Usage | The usage of memory in percentage. | 15 seconds |
| Instance Count | The count of running virtual machine instances of the hypervisor. | 15 seconds |
| Storage Usage | The usage of storage in percentage. | 15 seconds |
| Current Workload | The count of all the currently active hypervisor operations. | 15 seconds |
Compute instances metrics
The following metrics are available for each compute server:
| Metric | Description | Granularity |
|---|---|---|
| Name | The compute server name. | 15 seconds |
| Host Name | The compute server host name. | 15 seconds |
| IP | The IP of the compute server. | 15 seconds |
| CPU Utilization | The usage of the CPU in percentage. | 15 seconds |
| Total CPU | The total number of CPU resources. | 15 seconds |
| Total Memory | The total memory of compute server. | 15 seconds |
| State | The state of the compute server: Stopped, Active, or Error. | 15 seconds |
The following KPIs are available for each compute server on their respective dashboard:
| Metric | Description | Granularity |
|---|---|---|
| CPU Utilization | The usage of the CPU in percentage. | 15 seconds |
| Total CPU | The total number of CPU resources. | 15 seconds |
| Total Memory | The total memory of compute server. | 15 seconds |
Flavors metrics
The following metrics are available for each flavor:
| Metric | Description | Granularity |
|---|---|---|
| Flavor ID | The flavor ID. | 15 seconds |
| Flavor Name | The flavor name. | 15 seconds |
| Memory (GB) | The amount of RAM (in gigabytes) that is available for use. | 15 seconds |
| Root Disk (GB) | The amount of disk space (in gigabytes) that is allocated to use for the root (/) partition. | 15 seconds |
| Ephimeral Disk (GB) | The amount of disk space (in gigabytes) that is allocated to use for the ephemeral partition. | 15 seconds |
| vCPU | The number of virtual CPUs that is allocated to the server. | 15 seconds |
Images metrics
The following metrics are available for all the images in the selected hypervisor in the region:
| Metric | Description | Granularity |
|---|---|---|
| Image ID | The display name of the virtual machine instance. | 15 seconds |
| Images Name | The ID of the image. | 15 seconds |
| Created | The date and time when the resource was created. | 15 seconds |
| Updated | The date and time when the resource was updated. | 15 seconds |
| Image Size (MB) | The size of the image file in MB. | 15 seconds |
| Status | The image status. The possible values can be found Image Statuses | 15 seconds |
Storage metrics
The following metrics are available for each storage:
| Metric | Description | Granularity |
|---|---|---|
| Name | The storage name. | 15 seconds |
| IP | The IP of the storage. | 15 seconds |
| Volume Count | The number of volumes that are created by the storage. | 15 seconds |
| Available Capacity (GB) | The capacity that is available in the storage provider in GB. | 15 seconds |
| Total Capacity (GB) | The total capacity of the storage provider in GB. | 15 seconds |
| State | The state of the storage. | 15 seconds |
Troubleshooting
You might encounter the following issues while you set up the IBM PowerVC sensor:
Unable to find valid certification path
The following exception in the log indicates that the IBM PowerVC host server uses a self-signed certificate, and the certificate needs to be imported into the cacert of the JVM:
sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target.
PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target.
To resolve this issue, import a self-signed certificate into the cacert of the JVM by following the instructions from Self-Signed Certificate.
Invalid server certificate
The server certificate is invalid if the Subject Alternative Name (SAN) in the self-signed certificate does not have the expected IP address.
To resolve this issue, correct the server certificate, and import it again.
HTTP 403 Forbidden response status code
The HTTP 403 Forbidden response status code indicates that the server understands the request but refuses to authorize it.
To resolve this issue, verify the credentials that are provided in the configuration.yaml file with all the required permissions to the user.