Monitoring Watson Query with IBM Cloud Monitoring

Monitoring your Watson Query instance with IBM Cloud Monitoring

You can get insight into your Watson Query instance by using the IBM Cloud Monitoring service.

Metrics can help you find bottlenecks or predict possible production problems. Watson Query forwards selected information about your instance to Monitoring so that you can monitor specific metrics such as CPU and memory usage.

Set up your Watson Query service instance

To set up monitoring for Watson Query, you must create a service instance and then enable Platform Metrics in the same region as the Watson Query instance that you want to monitor. If you have deployments in more than one region, you must provision Monitoring and enable platform metrics for each region.

To set up Monitoring, follow these steps.

From the IBM Cloud navigation menu, select Observability.
Select Monitoring.
Either use an existing Monitoring service instance or create a new one.
After the instance is ready, click Configure platform metrics to enable platform metrics.
Select a region and then a Monitoring instance from that region. If you have deployments in more than one region, you must provision Monitoring and enable platform metrics for each region.

Accessing your IBM Cloud Monitoring metrics

To see your Watson Query customer metrics dashboards in Monitoring, follow these steps.

From the IBM Cloud navigation menu, select Observability.
Select Monitoring.
Select View IBM Cloud Monitoring to open the dashboard.

For more information, see the Monitoring getting started tutorial.

You can use the following metrics by service plan.

Average CPU usage

Table 1. Average CPU usage metric metadata
Metadata	Description
`Metric Name`	`ibm_data_virtualization_ep_avg_cpu_util`
`Metric Type`	`gauge`
`Value Type`	`none`
`Segment By`	`Service instance`

Average Heap memory usage

Table 2. Average Heap memory usage metric metadata
Metadata	Description
`Metric Name`	`ibm_data_virtualization_ep_avg_heapmem_util`
`Metric Type`	`gauge`
`Value Type`	`none`
`Segment By`	`Service instance`

CPU usage

Table 3. CPU usage metric metadata
Metadata	Description
`Metric Name`	`ibm_data_virtualization_adm_cpu_util`
`Metric Type`	`gauge`
`Value Type`	`none`
`Segment By`	`Service instance`

Disk IOPS Read Total

Table 4. Disk IOPS Read Total metric metadata
Metadata	Description
`Metric Name`	`ibm_data_virtualization_ibm_disk_iops_read_total`
`Metric Type`	`gauge`
`Value Type`	`none`
`Segment By`	`Service instance`

Disk IOPS Write Total

Table 5. Disk IOPS Write Total metric metadata
Metadata	Description
`Metric Name`	`ibm_data_virtualization_ibm_disk_iops_write_total`
`Metric Type`	`gauge`
`Value Type`	`none`
`Segment By`	`Service instance`

Disk usage percent

Table 6. Disk usage percent metric metadata
Metadata	Description
`Metric Name`	`ibm_data_virtualization_ibm_disk_io_usage_percent`
`Metric Type`	`gauge`
`Value Type`	`none`
`Segment By`	`Service instance`

Heap memory usage

Table 7. Heap memory usage metric metadata
Metadata	Description
`Metric Name`	`ibm_data_virtualization_adm_heapmem_util`
`Metric Type`	`gauge`
`Value Type`	`none`
`Segment By`	`Service instance`

How long did the disk wait because a log was saved

Table 8. How long did the disk wait because a log was saved metric metadata
Metadata	Description
`Metric Name`	`ibm_data_virtualization_log_disk_wait`
`Metric Type`	`gauge`
`Value Type`	`none`
`Segment By`	`Service instance`

Maximum CPU usage

Table 9. Maximum CPU usage metric metadata
Metadata	Description
`Metric Name`	`ibm_data_virtualization_ep_max_cpu_util`
`Metric Type`	`gauge`
`Value Type`	`none`
`Segment By`	`Service instance`

Maximum Heap memory usage

Table 10. Maximum Heap memory usage metric metadata
Metadata	Description
`Metric Name`	`ibm_data_virtualization_ep_max_heapmem_util`
`Metric Type`	`gauge`
`Value Type`	`none`
`Segment By`	`Service instance`

Minimum CPU usage

Table 11. Minimum CPU usage metric metadata
Metadata	Description
`Metric Name`	`ibm_data_virtualization_ep_min_cpu_util`
`Metric Type`	`gauge`
`Value Type`	`none`
`Segment By`	`Service instance`

Minimum Heap memory usage

Table 12. Minimum Heap memory usage metric metadata
Metadata	Description
`Metric Name`	`ibm_data_virtualization_ep_min_heapmem_util`
`Metric Type`	`gauge`
`Value Type`	`none`
`Segment By`	`Service instance`

Number of active connections

Table 13. Number of active connections metric metadata
Metadata	Description
`Metric Name`	`ibm_data_virtualization_active_conn`
`Metric Type`	`gauge`
`Value Type`	`none`
`Segment By`	`Service instance`

Number of data source connection status

Table 14. Number of data source connection status metric metadata
Metadata	Description
`Metric Name`	`ibm_data_virtualization_datasource_conn_status`
`Metric Type`	`gauge`
`Value Type`	`none`
`Segment By`	`Service instance`

Number of idle connections

Table 15. Number of idle connections metric metadata
Metadata	Description
`Metric Name`	`ibm_data_virtualization_idle_conn`
`Metric Type`	`gauge`
`Value Type`	`none`
`Segment By`	`Service instance`

Number of select statements

Table 16. Number of select statements metric metadata
Metadata	Description
`Metric Name`	`ibm_data_virtualization_select_stmts`
`Metric Type`	`gauge`
`Value Type`	`none`
`Segment By`	`Service instance`

Status of BigSQL Scheduler

Table 17. Status of BigSQL Scheduler metric metadata
Metadata	Description
`Metric Name`	`ibm_data_virtualization_bigsql_scheduler_status`
`Metric Type`	`gauge`
`Value Type`	`none`
`Segment By`	`Service instance`

Worker Average CPU usage

Table 18. Worker Average CPU usage metric metadata
Metadata	Description
`Metric Name`	`ibm_data_virtualization_wkr_node_avg_cpu_util`
`Metric Type`	`gauge`
`Value Type`	`none`
`Segment By`	`Service instance`

Worker Average Heap memory usage

Table 19. Worker Average Heap memory usage metric metadata
Metadata	Description
`Metric Name`	`ibm_data_virtualization_wkr_node_avg_heapmem_util`
`Metric Type`	`gauge`
`Value Type`	`none`
`Segment By`	`Service instance`

Worker Maximum CPU usage

Table 20. Worker Maximum CPU usage metric metadata
Metadata	Description
`Metric Name`	`ibm_data_virtualization_wkr_node_max_cpu_util`
`Metric Type`	`gauge`
`Value Type`	`none`
`Segment By`	`Service instance`

Worker Maximum Heap memory usage

Table 21. Worker Maximum Heap memory usage metric metadata
Metadata	Description
`Metric Name`	`ibm_data_virtualization_wkr_node_max_heapmem_util`
`Metric Type`	`gauge`
`Value Type`	`none`
`Segment By`	`Service instance`

Worker Minimum CPU usage

Table 22. Worker Minimum CPU usage metric metadata
Metadata	Description
`Metric Name`	`ibm_data_virtualization_wkr_node_min_cpu_util`
`Metric Type`	`gauge`
`Value Type`	`none`
`Segment By`	`Service instance`

Worker Minimum Heap memory usage

Table 23. Worker Minimum Heap memory usage metric metadata
Metadata	Description
`Metric Name`	`ibm_data_virtualization_wkr_node_min_heapmem_util`
`Metric Type`	`gauge`
`Value Type`	`none`
`Segment By`	`Service instance`

Attributes for segmentation

Global Attributes

The following attributes are available for segmenting all of the metrics.

Table 24. Global attributes for segmenting metrics
Attribute	Attribute Name	Attribute Description
`Cloud Type`	`ibm_ctype`	The cloud type is a value of public, dedicated, or local.
`Location`	`ibm_location`	The location of the monitored resource, which might be a region, data center, or global.
`Resource`	`ibm_resource`	The resource that is measured by the service, which is typically an identifying name or GUID.
`Resource Type`	`ibm_resource_type`	The type of the resource that is measured by the service.
`Resource group`	`ibm_resource_group_name`	The resource group where the service instance was created.
`Scope`	`ibm_scope`	The scope is the account, organization, or space GUID associated with this metric.
`Service name`	`ibm_service_name`	Name of the service that generates this metric.

Other attributes

The following attributes are available for segmenting one or more attributes. See the individual metrics for segmentation options.

Attribute	Attribute Name	Attribute Description
`Service instance`	`ibm_service_instance`	The service instance segment identifies the instance that the metric is associated with.