Monitoring Integration

IBM Cloud® Databases for DataStax is deprecated and no longer supported as of 30 June 2024. For more information, see the deprecation details.

Monitoring for IBM Cloud® Databases for DataStax deployments is provided through integration with the IBM Cloud® Monitoring service. Your deployments forward selected information so you can monitor deployment health and resource usage. To see your Databases for DataStax dashboards in IBM Cloud Monitoring, you must Enable Platform Metrics in the same region as your deployment. If you have deployments in more than one region, you must provision IBM Cloud Monitoring and enable platform metrics in each region.

To access IBM Cloud Monitoring from your deployment, use the Monitoring link from the right menu. (If you do not already have a monitoring service in the same region as your deployment it says Add monitoring.)

The default dashboards are not shown until database instances begin emitting metrics.

The Monitoring link in a deployment — Figure 1. The Monitoring link

To access your deployment's monitoring dashboard from IBM Cloud Monitoring, it's in the sidebar, under IBM.

Cloud databases dashboard in monitoring — Figure 2. Cloud databases dashboard

Monitoring Availability

IBM Cloud Monitoring is available for deployments in every region. Deployments in Multi-zone Regions (MZRs) - eu-gb, eu-de, us-east, us-south, jp-tok, au-syd - have their metrics in the corresponding region.

If you have deployments that are in Single-zone Region (SZR) che01 then your logs are forwarded to an IBM Cloud Monitoring instance in another region. You need to provision monitoring instances in the region where your metrics are forwarded to. Metrics for deployments in che01 go to jp-tok.

Available Metrics

Table 1. Available Metrics
Metric Name
Disk read latency mean
Disk write latency mean
IO utilization in percent 5-minute average
IO utilization in percent 15-minute average
IO utilization in percent 30-minute average
IO utilization in percent 60-minute average
IOPS read and write total count for an instance.
Max allowed memory for an instance.
The total number of connections used.
Total disk space for an instance.
Used CPU for an instance.
Used disk space for an instance.
Used memory for an instance.

Disk read latency mean

Table 2. Disk read latency mean metric metadata
Metadata	Description
`Metric Name`	`ibm_databases_for_cassandra_disk_read_latency_mean`
`Metric Type`	`gauge`
`Value Type`	`count`
`Segment By`	`Service instance`

Disk write latency mean

Table 3. Disk write latency mean metric metadata
Metadata	Description
`Metric Name`	`ibm_databases_for_cassandra_disk_write_latency_mean`
`Metric Type`	`gauge`
`Value Type`	`count`
`Segment By`	`Service instance`

IO utilization in percent 5-minute average

How much disk I/O was used over 5 minutes as a percentage of total disk I/O available.

Table 4. IO utilization in percent 5 minute average metric metadata
Metadata	Description
`Metric Name`	`ibm_databases-for-cassandra_disk_io_utilization_percent_average_5m`
`Metric Type`	`gauge`
`Value Type`	`percent`
`Segment By`	`Service instance`

IO utilization in percent 15-minute average

How much disk I/O was used over 15 minutes as a percentage of total disk I/O available.

Table 5. IO utilization in percent 15 minute average metric metadata
Metadata	Description
`Metric Name`	`ibm_databases-for-cassandra_disk_io_utilization_percent_average_15m`
`Metric Type`	`gauge`
`Value Type`	`percent`
`Segment By`	`Service instance`

IO utilization in percent 30-minute average

How much disk I/O was used over 30 minutes as a percentage of total disk I/O available.

Table 6. IO utilization in percent 30 minute average metric metadata
Metadata	Description
`Metric Name`	`ibm_databases-for-cassandra_disk_io_utilization_percent_average_30m`
`Metric Type`	`gauge`
`Value Type`	`percent`
`Segment By`	`Service instance`

IO utilization in percent 60-minute average

How much disk I/O was used over 60 minutes as a percentage of total disk I/O available.

Table 7. IO utilization in percent 60 minute average metric metadata
Metadata	Description
`Metric Name`	`ibm_databases-for-cassandra_disk_io_utilization_percent_average_60m`
`Metric Type`	`gauge`
`Value Type`	`percent`
`Segment By`	`Service instance`

IOPS read and write total count for an instance

How many input/output operations per second your deployment is performing.

Table 8. IOPS read and write total count for an instance metric metadata
Metadata	Description
`Metric Name`	`ibm_databases-for-cassandra_disk_iops_read_write_total`
`Metric Type`	`gauge`
`Value Type`	`count`
`Segment By`	`Service instance`

Max allowed memory for an instance

The maximum amount of memory available to your deployment.

Table 9. Max allowed memory for an instance metric metadata
Metadata	Description
`Metric Name`	`ibm_databases-for-cassandra_memory_limit_bytes`
`Metric Type`	`gauge`
`Value Type`	`byte`
`Segment By`	`Service instance`

The total number of connections in use

The total number of connections in use.

Table 10. The total number of connections in use metric metadata
Metadata	Description
`Metric Name`	`ibm_databases-for-cassandra_total_connections`
`Metric Type`	`gauge`
`Value Type`	`count`
`Segment By`	`Service instance`

Total disk space for an instance

Represents the total amount of disk available to your deployment.

Table 11. Total disk space for an instance metric metadata
Metadata	Description
`Metric Name`	`ibm_databases-for-cassandra_disk_total_bytes`
`Metric Type`	`gauge`
`Value Type`	`byte`
`Segment By`	`Service instance`

Used CPU for an instance

How much CPU is used as a percentage of total CPU available.

Table 12. Used CPU for an instance metric metadata
Metadata	Description
`Metric Name`	`ibm_databases-for-cassandra_cpu_used_percent`
`Metric Type`	`gauge`
`Value Type`	`percent`
`Segment By`	`Service instance`

Used disk space for an instance

How much disk your deployment is using.

Table 13. Used disk space for an instance metric metadata
Metadata	Description
`Metric Name`	`ibm_databases-for-cassandra_disk_used_bytes`
`Metric Type`	`gauge`
`Value Type`	`byte`
`Segment By`	`Service instance`

Used memory for an instance

How much memory your deployment is using.

Table 14. Used memory for an instance metric metadata
Metadata	Description
`Metric Name`	`ibm_databases-for-cassandra_memory_used_bytes`
`Metric Type`	`gauge`
`Value Type`	`byte`
`Segment By`	`Service instance`

Used JVM heap percent

How much Java virtual machine (JVM) heap memory your deployment is using.

Table 15. Used JVM percent for an instance metric metadata
Metadata	Description
`Metric Name`	`ibm_databases_for_cassandra_jvm_heap_percent`
`Metric Type`	`graph`
`Value Type`	`percent`
`Segment By`	`Service instance`

Garbage collection percent 15-minute average

How much garbage collection has been used over 15 minutes as a percentage of total your deployment is using.

Table 16. Used JVM percent for an instance metric metadata
Metadata	Description
`Metric Name`	`ibm_cassandra_garbage_collection_percent_average_15m`
`Metric Type`	`graph`
`Value Type`	`percent`
`Segment By`	`Service instance`

Attributes for Segmentation

Global Attributes

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

Table 17. Global Attributes Metadata
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 - might be a region, data center, or global.
`Resource`	`ibm_resource`	The resource that is measured by the service - typically an identifying name or GUID.
`Resource Type`	`ibm_resource_type`	The type of the resource that is measured by the service.
`Scope`	`ibm_scope`	The scope is the account, organization, or space GUID associated with this metric.

More Attributes

Table 18. Additional Attributes Metadata
Attribute	Attribute Name	Attribute Description
`Service instance`	`ibm_service_instance`	The service instance segment identifies the instance the metric is associated with.
`Service instance name`	`ibm_service_instance_name`	The service instance name provides the user-provided name of the service instance, which isn't necessarily a unique value depending on the name that is provided by the user.
`Resource group`	`ibm_resource_group_name`	The resource group where the service instance was created.