Triggering conditions for storage system internal resource alerts

You can set up IBM Storage Insights Pro so that it examines the attributes, capacity, and performance of the internal resources of Storage Systems and notifies you when changes or violations are detected.

Important: Not all the attributes upon which you can alert are listed here. To view a complete list of attributes upon which you can alert, go to Configuration > Alert Policies. Double-click a default policy for a storage system. Click Edit Alert Definitions on the Alert Definitions tab. View the attributes that are available in the general, capacity, and performance categories. Note that the attributes that are automatically configured for alerts in the default alert policies, or default alerts, have a status of Active.

In the tables, default alerts are marked with an asterisk (*).

Tips:
  • The type of storage system determines which attributes and performance conditions are available for alerts. For example, triggering conditions for shares are available only for storage systems that are configured for file storage, such as Storwize V7000 Unified.
  • For capacity attributes, you can generate alerts when the amount of storage is greater than, less than, or equal to a specified value. You can also determine the unit of measurement for the attribute, such as KiB, MiB, GiB, or TiB.

Internal resources (common conditions)

There are a number of alert conditions that are common to many of the internal resources in a storage system. These common conditions represent key changes in your storage infrastructure. For example, you can specify conditions that generate alerts when specific internal resources are added to or deleted from a storage system, or when current data isn't being collected about resources.

By default, asset, capacity, and configuration metadata for storage systems is aggregated and collected daily. Define alerts to track daily changes to the attributes and conditions of the internal resources in your storage systems.

Table 1. Triggering attributes and conditions that are common to internal resources
General Attributes Triggering Conditions for Attributes

New resource

A resource is detected for the first time. Use this alert to be notified when new physical and logical resources are added to a storage system.

Removed physical resource

Deleted logical resource

A previously monitored resource can no longer be found. Historical data about the resource is retained, but no current data is being collected. Use these alerts to be notified if a physical or logical resource is removed, deleted, or becomes unavailable.

Physical resources include disks, RAID arrays, I/O groups, ports, nodes, host connections, clusters, and file systems. Logical resources include volumes, pools, filesets, and shares.

Clusters

Table 2. Triggering attributes and conditions for general changes on clusters
General Attributes Triggering Conditions for Attributes

New Cluster

A cluster is detected for the first time.

Removed NAS Cluster

A previously monitored NAS cluster can no longer be found. Historical data about the cluster is retained, but no current data is being collected. Use this alert to be notified if a cluster is removed or becomes unavailable.

Drives

Table 3. Triggering attributes and conditions for general changes on storage system drives
General Attributes Triggering Conditions for Attributes

New drive

A drive is detected for the first time.

Removed drive

A previously monitored drive can no longer be found. Historical data about the drive is retained, but no current data is being collected. Use this alert to be notified if a drive is removed or becomes unavailable.

Table 4. Triggering attributes and conditions for capacity changes on drives
Capacity Attributes Triggering Conditions for Attributes

Available Drive Capacity (Previously known as Available Disk Space)

The capacity that is available (not allocated) on the drive.

Capacity (Previously known as Disk Capacity)

The total amount of storage capacity that is on the drive.

Enclosures

Table 5. Triggering attributes and conditions for general changes on enclosures
General attributes Triggering conditions for attributes
Power Supplies Status Power supply status of the enclosure is not successful, warning, error.

FC Ports

Table 6. Triggering attributes and conditions for general changes on Fibre Channel ports
General Attributes Triggering Conditions for Attributes

New FC Port

A new FC port was detected for the first time.

Removed FC Port

A previously monitored FC port can no longer be found. Historical data about the port is retained, but no current data is being collected. Use this alert to be notified if a port is deleted or becomes unavailable.

Status

One of the following statuses is detected for an FC port:
Not Normal
An error or warning condition is detected on a port.
Warning
A warning condition is detected on a port.
Error
An error condition is detected on a port.

Filesets

Table 7. Triggering attributes and conditions for general changes on filesets
General Attributes Triggering Conditions for Attributes

Deleted NAS Fileset

A previously monitored NAS fileset can no longer be found. Historical data about the fileset is retained, but no current data is being collected. Use this alert to be notified if a fileset is deleted or becomes unavailable.

New Fileset

A fileset is detected for the first time.

State

A fileset is linked to a file system, unlinked from a file system, or deleting.

File Systems

Table 8. Triggering attributes and conditions for general changes on file systems
General Attributes Triggering Conditions for Attributes

New File System

A file system is detected for the first time.

Removed NAS File System

A previously monitored NAS file system can no longer be found. Historical data about the file system is retained, but no current data is being collected. Use this alert to be notified if a file system is deleted or becomes unavailable.

File System Pools

Table 9. Triggering attributes and conditions for general changes on file system pools
General Attributes Triggering Conditions for Attributes

Deleted Pool

A previously monitored NAS pool can no longer be found. Historical data about the pool is retained, but no current data is being collected. Use this alert to be notified if a pool is deleted or becomes unavailable.

New Pool

A NAS pool is detected for the first time.

Host Connections

Table 10. Triggering attributes and conditions for general changes on host connections
General Attributes Triggering Conditions for Attributes

New Host Connection

A host connection is detected for the first time.

Removed Host Connection

A previously monitored host connection can no longer be found. Historical data about the host connection is retained, but no current data is being collected. Use this alert to be notified if a host connection is removed or becomes unavailable.

Table 11. Triggering attributes and conditions for changes to performance metrics for unmap operations on host connections
Performance Attribute Triggering Conditions for Attributes
Data Rate (Unmap) Define an alert to monitor the average number of MiBs per second that were unmapped.

This metric applies to systems that are running IBM Storage Virtualize V8.1.1 or later.

Overall I/O Rate (Unmap) Define an alert to monitor the average number of unmap operations per second.

This metric applies to systems that are running IBM Storage Virtualize V8.1.1 or later.

Peak Response Time (Unmap) Define an alert to monitor the worst response time measured for an unmap operation in the sample interval.

This metric applies to systems that are running IBM Storage Virtualize V8.1.1 or later.

Response Time (Unmap) Define an alert to monitor the average number of milliseconds required to complete an unmap operation.

This metric applies to systems that are running IBM Storage Virtualize V8.1.1 or later.

Unaligned Unmap I/O Rate Define an alert to monitor the average number of volumes unmap operations per second that are not aligned on an 8K boundary.

This metric applies to systems that are running IBM Storage Virtualize V8.1.1 or later.

I/O Groups

Table 12. Triggering attributes and conditions for general changes on I/O groups
General Attributes Triggering Conditions for Attributes

New I/O Group

A new I/O group was detected for the first time.

Removed I/O Group

A previously monitored I/O group can no longer be found. Historical data about the I/O group is retained, but no current data is being collected. Use this alert to be notified if an I/O group is removed or becomes unavailable.

IP Ports

Triggering attributes and conditions are available for Internet Protocol ports on the nodes on block storage systems that run IBM Storage Virtualize, such as SAN Volume Controller, the IBM Storwize family, and some models of the IBM Storage FlashSystem family.

Table 13. Triggering attributes and conditions for general changes on IP ports
General Attributes Triggering Conditions for Attributes

Status

One of the following statuses was detected for an IP port:
  • Configured
  • Unconfigured

Removed Port

A previously monitored IP port can no longer be found. Historical data about the port is retained, but no current data is being collected. Use this alert to be notified if a port is deleted or becomes unavailable.

New Port

A new IP port was detected for the first time.

Host Attach

An IP port was attached to, or detached from, a host.

Storage Attach

An IP port was attached to, or detached from, a storage system.

Management

One of the following management statuses was detected for an IP port:
  • Configured
  • Unconfigured

Remote Copy Relationship

The remote copy relationship changed, or one of the following remote copy statuses was detected for an IP port:
  • Active
  • Unconfigured
  • Standby

Managed Disks

Table 14. Triggering attributes and conditions for general changes on managed disks
General Attributes Triggering Conditions for Attributes

Managed Disk Status

One of the following statuses is detected for a managed disk:
Not Normal
An error or warning status was detected on a managed disk.
Warning
A warning status was detected on a managed disk.
Error
An error status was detected on a managed disk.

New Managed Disk

A new managed disk was detected for the first time.

Removed Managed Disk

A previously monitored managed disk can no longer be found. Historical data about the managed disk is retained, but no current data is being collected. Use this alert to be notified if a managed disk is removed or becomes unavailable.

Table 15. Triggering attributes and conditions for capacity changes on managed disks
Capacity Attributes Triggering Conditions for Attributes
Available Capacity

The unused storage capacity on the managed disk.

Capacity (Previously known as Total Space)

The total capacity on the managed disk on the storage system. This attribute is only available for Storwize V7000 storage systems that are configured as back-end storage.

Drive Compression Ratio

The ratio of the uncompressed data size to the compressed data size for a particular managed disk in a storage system.

Define alerts for this attribute to monitor how well compression on drives is working and be automatically notified if compression ratios change by a percentage or reach a specific threshold. Significant drops (30%-50%) in the drive compression ratio between consecutive metadata collection times might indicate that a ransomware attack is encrypting your data.

Because encrypted data does not compress well, the effectiveness of compression for that targeted data is reduced. By defining an alert that detects when the compression ratio changes, you can be notified when these drops occur and of potential attacks that might be encrypting your data.

You can use the following methods to trigger drive compression ratio alerts:
  • Use the >= or <= operators to be notified when a specific compression ratio threshold is reached. For example, if your normal baseline compression ratio is 4:1, you might want to know when it drops to 3:1 or 2:1. You can then define an alert that notifies you when the compression ratio is equal to 3:1 or less. If you want to know if your ratio improves, you can also define compression ratio thresholds of 5:1 or more, 6:1 or more, and so on.
  • Use the Changes operator to be notified when your compression ratio changes by a percentage. For example, if you don't know your baseline compression ratio, or if it typically varies throughout the day, you might want to be notified only when it changes by a significant percentage. In that case, you can define an alert that notifies you when the compression ratio changes by 50% or more.
    Tip: Before a compression ratio change alert can be triggered for the first time, metadata collection must run two times. The first probe collects information about the compression ratio at the time when it runs. The next probe, which typically runs 24 hours later, collects information about the compression ratio again. If the percentage difference between the compression ratios matches or exceeds the value of the change operator, an alert is triggered.

Drive Compression Savings

The estimated amount and percentage of capacity that is saved in a particular managed disk in a storage system.

Pool Compression Ratio

The ratio of the uncompressed data size to the compressed data size for the pool that contains managed disk.

Define alerts for this attribute to monitor how well compression for all the pools in a storage system is working and be automatically notified if compression ratios change by a percentage or reach a specific threshold. Significant drops (30%-50%) in the pool compression ratio between consecutive metadata collection times might indicate that a ransomware attack is encrypting your data.

Because encrypted data does not compress well, the effectiveness of compression for that targeted data is reduced. By defining an alert that detects when the compression ratio changes, you can be notified when these drops occur and of potential attacks that might be encrypting your data.

You can use the following methods to trigger compression ratio alerts:
  • Use the >= or <= operators to be notified when a specific compression ratio threshold is reached. For example, if your normal baseline compression ratio is 4:1, you might want to know when it drops to 3:1 or 2:1. You can then define an alert that notifies you when the compression ratio is equal to 3:1 or less. If you want to know if your ratio improves, you can also define compression ratio thresholds of 5:1 or more, 6:1 or more, and so on.
  • Use the Changes operator to be notified when your compression ratio changes by a percentage. For example, if you don't know your baseline compression ratio, or if it typically varies throughout the day, you might want to be notified only when it changes by a significant percentage. In that case, you can define an alert that notifies you when the compression ratio changes by 50% or more.
    Tip: Before a compression ratio change alert can be triggered for the first time, metadata collection must run two times. The first probe collects information about the compression ratio at the time when it runs. The next probe, which typically runs 24 hours later, collects information about the compression ratio again. If the percentage difference between the compression ratios matches or exceeds the value of the change operator, an alert is triggered.

Pool Compression Savings

The estimated amount and percentage of capacity that is saved in the pool that contains the managed disk.

Total Compression Ratio

The ratio of the uncompressed data size to the compressed data size for all the managed disks in a storage system.

Define alerts for this attribute to monitor how well compression for all the managed disks in a storage system is working and be automatically notified if compression ratios change by a percentage or reach a specific threshold. Significant drops (30%-50%) in the compression ratio between consecutive metadata collection times might indicate that a ransomware attack is encrypting your data.

Because encrypted data does not compress well, the effectiveness of compression for that targeted data is reduced. By defining an alert that detects when the compression ratio changes, you can be notified when these drops occur and of potential attacks that might be encrypting your data.

You can use the following methods to trigger drive compression ratio alerts:
  • Use the >= or <= operators to be notified when a specific compression ratio threshold is reached. For example, if your normal baseline compression ratio is 4:1, you might want to know when it drops to 3:1 or 2:1. You can then define an alert that notifies you when the compression ratio is equal to 3:1 or less. If you want to know if your ratio improves, you can also define compression ratio thresholds of 5:1 or more, 6:1 or more, and so on.
  • Use the Changes operator to be notified when your compression ratio changes by a percentage. For example, if you don't know your baseline compression ratio, or if it typically varies throughout the day, you might want to be notified only when it changes by a significant percentage. In that case, you can define an alert that notifies you when the compression ratio changes by 50% or more.
    Tip: Before a compression ratio change alert can be triggered for the first time, metadata collection must run two times. The first probe collects information about the compression ratio at the time when it runs. The next probe, which typically runs 24 hours later, collects information about the compression ratio again. If the percentage difference between the compression ratios matches or exceeds the value of the change operator, an alert is triggered.

Total Compression Savings

The estimated amount and percentage of capacity that is saved in all managed disks in a particular storage system by using data compression techniques.

Modules

Table 16. Triggering attributes and conditions for general changes on modules
General Attributes Triggering Conditions for Attributes

Deleted Module

A previously monitored module can no longer be found. Use this alert to be notified if a module is removed or becomes unavailable.

Network Shared Disks

Table 17. Triggering attributes and conditions for general changes on NSDs
General Attributes Triggering Conditions for Attributes

New NSD

A new NSD was detected for the first time.

Removed NSD

A previously monitored NSD can no longer be found. Historical data about the NSD is retained, but no current data is being collected. Use this alert to be notified if an NSD is removed or becomes unavailable.

Status

One of the following statuses is detected for an NSD:
Not Normal
An error or warning status was detected on an NSD.
Warning
A warning status was detected on an NSD. This status might occur if a storage system comes online or if its version changes.
Error
An error status was detected on an NSD.

Nodes

Table 18. Triggering attributes and conditions for general changes on nodes
General Attributes Triggering Conditions for Attributes

New Node

A new node was detected for the first time.

Removed Node (Block storage)

A previously monitored node can no longer be found. Historical data about the node is retained, but no current data is being collected. Use this alert to be notified if a node is removed or becomes unavailable.

Removed NAS Node (File storage)

A previously monitored NAS node can no longer be found. Historical data about the node is retained, but no current data is being collected. Use this alert to be notified if a node is removed or becomes unavailable.

Cloud Gateway Status (File storage)

One of the following statuses is detected for a node. This attribute is available only for IBM Storage Scale System.
Not Running
The gateway service is not running because, for example, the service is stopped, no cloud account is configured, or the connection to the cloud provider failed.
Not Installed
The node is not a cloud gateway.
No File System
The node is a cloud gateway and the gateway service is running, but the node is not yet assigned to a file system.
Stopped
The node is a cloud gateway for a file system, but the gateway service is stopped.
No Cloud Account
The node is a cloud gateway for a file system and the gateway service is running, but no cloud account is configured.
Disconnected
The node is a cloud gateway, the gateway service is running, and a cloud account is configured, but the connection to the cloud provider failed.
Table 19. Triggering attributes and conditions for changes to performance metrics for cache fullness on nodes
Performance Attributes Triggering Conditions for Attributes

Max Read Cache Fullness

Define an alert to monitor the maximum amount of the lower cache which the cache partitions of the pools that are managed by the node use for read operations. If the maximum value for the cache reaches 100%, the read cache partition for one or more of the pools is full. The read operations that pass through the node to the affected pools will be queued and the I/O response times will increase for the volumes in the affected pools.

This metric applies to systems that are running IBM Storage Virtualize V7.3 or later.

Max Write Cache Fullness

Define an alert to monitor the maximum amount of the lower cache which the cache partitions of the pools that are managed by the node use for write operations. If the maximum value for the cache reaches 100%, the write cache partition for one or more of the pools is full. The write operations that pass through the node to the affected pools will be queued and the I/O response times will increase for the volumes in the affected pools.

This metric applies to systems that are running IBM Storage Virtualize V7.3 or later.

Read Cache Fullness

Define an alert to monitor the average amount of the lower cache which the cache partitions of the pools that are managed by the node use for read operations. Use this alert to monitor the average cache fullness for read operations to identify the nodes that experience heavy cache usage.

This metric applies to systems that are running IBM Storage Virtualize V7.3 or later.

Write Cache Fullness

Define an alert to monitor the average amount of the lower cache which the cache partitions of the pools that are managed by the node are using for write operations. Use this alert to monitor the average cache fullness for write operations to identify the nodes that experience heavy cache usage.

This metric applies to systems that are running IBM Storage Virtualize V7.3 or later.

Table 20. Triggering attributes and conditions for changes to performance metrics for recovering data in data reduction pools on nodes
Performance Attributes Triggering Conditions for Attributes

Data Rewrite Rate

Define an alert to monitor the rate at which data is rewritten when a host overwrites data in data reduction pools on the node.

This metric applies to systems that are running IBM Storage Virtualize V8.1.2 or later.

Extent Collection Rate

Define an alert to monitor the number of volume extents that were processed for garbage collection. The reclaimable capacity in the volume extents is collected so that it can be reused in the data reduction pools on the node.

This metric applies to systems that are running IBM Storage Virtualize V8.1.2 or later.

Data Movement Rate

Define an alert to monitor the rate at which valid data in a reclaimed volume extent is moved to a new extent in the data reduction pool on the node.

This metric applies to systems that are running IBM Storage Virtualize V8.1.2 or later.

New Address Write Rate

Define an alert to monitor the rate at which capacity is used to write the host's data to unallocated addresses in the data reduction pool on the node. Use this alert to determine which hosts are increasing the amount of capacity that is being written to data reduction pools on a node.

This metric applies to systems that are running IBM Storage Virtualize V8.1.2 or later.

Reclaimable Capacity Define an alert to monitor the amount of capacity that can be reclaimed in the data reduction pools on the node.

This metric applies to systems that are running IBM Storage Virtualize V8.1.2 or later.

Recovered Capacity Rate

Define an alert to monitor the rate at which capacity is recovered by garbage collection for reuse in the data reduction pools on the node.

This metric applies to systems that are running IBM Storage Virtualize V8.1.2 or later.

Pools

Table 21. Triggering attributes and conditions for general changes on pools
General Attributes Triggering Conditions for Attributes

Deleted Pool

A previously monitored pool can no longer be found. Historical data about the pool is retained, but no current data is being collected. Use this alert to be notified if a pool is deleted or becomes unavailable.

New Storage Pool

A new pool was detected for the first time.

Status

One of the following statuses is detected for a pool:
Not Normal
An error or warning condition is detected on a pool.
Warning
A warning condition is detected on a pool. This condition might occur if a pool goes offline.
Error
An error condition is detected on a pool. This condition might occur under the following conditions:
  • The percentage of remaining, unused volume capacity in a pool that is not available to be used is too high.
  • The available capacity in a pool that is not reserved for volumes is too low.
  • The pool total provisioned capacity exceeds the warning or critical threshold boundary value.
Table 22. Triggering attributes and conditions for capacity changes on pools
Capacity Attributes Triggering Conditions for Attributes

Adjusted Used Capacity

The amount of capacity that can be used without exceeding the capacity limit. For example, you set a capacity limit of 80% for your pools. You want to get an informational alert when the adjusted used capacity exceeds 60% and a critical alert when the adjusted used capacity exceeds 80%. So, you define an informational alert with these parameters:
Adjusted Used Capacity ≥ 60%
And, you define a critical alert with these parameters:
Adjusted Used Capacity ≥ 80%

Available Repository Capacity

The amount of available, unallocated storage space on all extents in the repository of a pool for Track Space-Efficient (TSE) thin-provisioning. This attribute applies only to the DS8000 storage systems.

You can use this alert to be notified about space-efficient volumes.

Available Virtual Capacity

The amount of total provisioned in a thin-provisioned pool that is not used by volumes.

Available Written Capacity (Previously known as Effective Available Capacity) The amount of the total provisioned capacity in the pools that is not allocated to the volumes in the pools.

Capacity-to-Limit

The amount of capacity that is available for storing data before the capacity limit is reached. For example, if you set a capacity limit, you can define a warning alert when the available capacity relative to the capacity limit, falls below the value that you specify, such as:
Capacity-to-Limit ≤ 500 GiB

Deduplication Savings

The estimated percentage of capacity that is saved by using data deduplication. The percentage is calculated across all deduplicated volumes in the pool and does not include the capacity of volumes that are not deduplicated. Available for resources that run IBM Storage Virtualize 8.1.3 or later.

Mapped Capacity (Previously known as Assigned Volume Space)

The amount of space on all the volumes in a pool that are mapped or assigned to host systems.

For a thin-provisioning pool, this value includes the total provisioned of thin-provisioned volumes, which might exceed the total capacity in the pool. For Hitachi VSP non-thin provisioning pool capacity, this value is the sum of assigned regular host-accessible volumes. Volumes that are used for thin-provisioning (pool volumes) are not included.

Enterprise HDD Capacity The total capacity on Enterprise hard disk drives in the pool. Easy Tier® can use the capacity on these drives to retier the volume extents in the pool.
Enterprise HDD Available Capacity The available capacity on Enterprise hard disk drives in the pool. Easy Tier can use the available capacity to retier the volume extents in the pool.
Enterprise HDD Available Capacity (%) The percentage of capacity on Enterprise hard disk drives in the pool that is available. Easy Tier can use the available capacity to retier the volume extents in the pool.
Flash Core Module Capacity (GiB) The total usable capacity in gibibytes (GiB) of all FlashCore Modules (FCMs) that are part of the storage pool. Available for DS8000 storage systems only.
Flash Core Module Available Capacity The storage pool's total usable capacity that is provided by FlashCore Modules. Available for DS8000 storage systems only.
Nearline HDD Capacity The total capacity on Nearline hard disk drives in the pool. Easy Tier can use the capacity on these drives to retier the volume extents in the pool.
Nearline HDD Available Capacity The available capacity on Nearline hard disk drives in the pool. Easy Tier can use the available capacity to retier the volume extents in the pool.
Nearline HDD Available Capacity (%) The percentage of capacity on Nearline hard disk drives in the pool that is available. Easy Tier can use the available capacity to retier the volume extents in the pool.

Pool Compression Ratio

The ratio of the uncompressed data size to the compressed data size for a particular pool in a storage system.

Define alerts for this attribute to monitor how well compression for all the pools in a storage system is working and be automatically notified if compression ratios change by a percentage or reach a specific threshold. Significant drops (30%-50%) in the pool compression ratio between consecutive metadata collection times might indicate that a ransomware attack is encrypting your data.

Because encrypted data does not compress well, the effectiveness of compression for that targeted data is reduced. By defining an alert that detects when the compression ratio changes, you can be notified when these drops occur and of potential attacks that might be encrypting your data.

You can use the following methods to trigger compression ratio alerts:
  • Use the >= or <= operators to be notified when a specific compression ratio threshold is reached. For example, if your normal baseline compression ratio is 4:1, you might want to know when it drops to 3:1 or 2:1. You can then define an alert that notifies you when the compression ratio is equal to 3:1 or less. If you want to know if your ratio improves, you can also define compression ratio thresholds of 5:1 or more, 6:1 or more, and so on.
  • Use the Changes operator to be notified when your compression ratio changes by a percentage. For example, if you don't know your baseline compression ratio, or if it typically varies throughout the day, you might want to be notified only when it changes by a significant percentage. In that case, you can define an alert that notifies you when the compression ratio changes by 50% or more.
    Tip: Before a compression ratio change alert can be triggered for the first time, metadata collection must run two times. The first probe collects information about the compression ratio at the time when it runs. The next probe, which typically runs 24 hours later, collects information about the compression ratio again. If the percentage difference between the compression ratios matches or exceeds the value of the change operator, an alert is triggered.

Pool Compression Savings

The estimated amount and percentage of capacity that is saved in a particular pool of a particular storage system.

Repository Space

The amount of space on all extents in the repository of a pool. This attribute applies only to the DS8000 storage systems.

Reserved Capacity (Previously known as Reserved Pool Space)

The amount of unused capacity in a pool that is reserved for provisioning and optimization tasks.

Pool capacity is reserved when a provisioning or optimization task is created, and used when the task is run.

Reserved Volume Capacity (Previously known as Unused Space)

The amount of pool capacity that is reserved but has not been used yet to store data on the thin-provisioned volume.

Safeguarded Capacity

The capacity that is consumed by all of the Safeguarded Copies for a source volume in IBM Storage Virtualize and DS8000. This value applies only to volumes that are the source in a Safeguarded Copy relationship.

Safeguarded Used Capacity (%) The percentage of safeguarded capacity currently used. For example, Safeguarded Used Capacity (%) is greater than or equal to 25%.

Shortfall

The difference between the amount of total provisioned that is committed to the volumes in the pools and the actual physical capacity that is available in the pools. As the total provisioned is allocated to the thin-provisioned and compressed volumes, the shortfall increases and becomes more critical.

This value is determined by the formula, Overprovisioned Capacity ÷ Committed but Unused Capacity

For example, the physical capacity of the pools is 70 GiB, but 150 GiB of total provisioned was committed to the thin-provisioned volumes. If the volumes are using 50 GiB, then there is still 100 GiB committed to those volumes (150 GiB − 50 GiB) with only 20 GiB of available pool capacity (70 GiB − 50 GiB). Because only 20 GiB of the pool capacity is available, 80 GiB of the committed capacity cannot be allocated (100 GiB - 20 GiB).

SCM Capacity The total capacity on Storage Class Memory (SCM) drives in the pool. Easy Tier can use the capacity on SCM drives to retier the volume extents in the pool.

Available for IBM Storage Virtualize systems, such as IBM Storage FlashSystem 9100, IBM Storage FlashSystem 7200, and the IBM Storwize family.

SCM Available Capacity The available capacity on Storage Class Memory (SCM) drives in the pool. Easy Tier can use the available capacity to retier the volume extents in the pool.

Available for IBM Storage Virtualize systems, such as IBM Storage FlashSystem 9100, IBM Storage FlashSystem 7200, and the IBM Storwize family.

SCM Available Capacity (%) The percentage of capacity on Storage Class Memory (SCM) drives in the pool that is available. Easy Tier can use the available capacity to retier the volume extents in the pool.

Available for IBM Storage Virtualize systems, such as IBM Storage FlashSystem 9100, IBM Storage FlashSystem 7200, and the IBM Storwize family.

Tier 0 Flash Capacity The total capacity on Tier 0 flash solid-state drives in the pool. Easy Tier can use the capacity on these drives to retier the volume extents in the pool.
Tier 0 Flash Available Capacity The available capacity on Tier 0 flash solid-state drives in the pool. Easy Tier can use the available capacity to retier the volume extents in the pool.
Tier 0 Flash Available Capacity (%) The percentage of capacity on Tier 0 flash solid-state drives in the pool that is available. Easy Tier can use the available capacity to retier the volume extents in the pool.
Tier 1 Flash Capacity The total capacity on Tier 1 flash solid-state drives in the pool. Easy Tier can use the capacity on these drives to retier the volume extents in the pool.
Tier 1 Flash Available Capacity The available capacity on Tier 1 flash solid-state drives in the pool. Easy Tier can use the available capacity to retier the volume extents in the pool.
Tier 1 Flash Available Capacity (%) The percentage of capacity on Tier 1 flash solid-state drives in the pool that is available. Easy Tier can use the available capacity to retier the volume extents in the pool.
Tier 2 Flash Capacity The total capacity on Tier 2 flash, high-capacity drives in the pool. Easy Tier can use the capacity on these drives to retier the volume extents in the pool.

Available for DS8000 storage systems.

Tier 2 Flash Available Capacity The available capacity on Tier 2 flash, high-capacity drives in the pool. Easy Tier can use the available capacity to retier the volume extents in the pool.

Available for DS8000 storage systems.

Tier 2 Flash Available Capacity (%) The percentage of capacity on Tier 2 flash, high-capacity drives in the pool that is available. Easy Tier can use the available capacity to retier the volume extents in the pool.

Available for DS8000 storage systems.

Total Compression Ratio

The ratio of the uncompressed data size to the compressed data size for all the pools in a storage system.

Define alerts for this attribute to monitor how well compression for all the pools in a storage system is working and be automatically notified if compression ratios change by a percentage or reach a specific threshold. Significant drops (30%-50%) in the compression ratio between consecutive metadata collection times might indicate that a ransomware attack is encrypting your data.

Because encrypted data does not compress well, the effectiveness of compression for that targeted data is reduced. By defining an alert that detects when the compression ratio changes, you can be notified when these drops occur and of potential attacks that might be encrypting your data.

You can use the following methods to trigger drive compression ratio alerts:
  • Use the >= or <= operators to be notified when a specific compression ratio threshold is reached. For example, if your normal baseline compression ratio is 4:1, you might want to know when it drops to 3:1 or 2:1. You can then define an alert that notifies you when the compression ratio is equal to 3:1 or less. If you want to know if your ratio improves, you can also define compression ratio thresholds of 5:1 or more, 6:1 or more, and so on.
  • Use the Changes operator to be notified when your compression ratio changes by a percentage. For example, if you don't know your baseline compression ratio, or if it typically varies throughout the day, you might want to be notified only when it changes by a significant percentage. In that case, you can define an alert that notifies you when the compression ratio changes by 50% or more.
    Tip: Before a compression ratio change alert can be triggered for the first time, metadata collection must run two times. The first probe collects information about the compression ratio at the time when it runs. The next probe, which typically runs 24 hours later, collects information about the compression ratio again. If the percentage difference between the compression ratios matches or exceeds the value of the change operator, an alert is triggered.

Total Compression Savings

The estimated amount and percentage of capacity that is saved in all pools in a particular storage system by using data compression techniques.

Total Reserved Capacity

The total amount of space on the pool that is reserved for provisioning and optimization tasks. Pool space is reserved when a provisioning or optimization task is created, and allocated when the task is run.

Total Provisioned

The amount of space by which the capacity of a volume exceeds the physical capacity of the associated pool.

Total Provisioned (%) (Previously known as Provisioned Capacity)

The percentage of physical space in a pool that is committed to the total provisioned of the volumes in the pool.

You can use this alert to be notified about space-efficient volumes.

Total Savings (Previously known as Total Capacity Savings) The estimated percentage of capacity that is saved by using data deduplication, data compression, and thin provisioning.

Available for IBM FlashSystem A9000 and IBM FlashSystem A9000R, IBM Storage Accelerate, XIV storage systems with firmware version 11.6 or later, and resources that run IBM Storage Virtualize.

Usable Capacity The total amount of storage space in the pool. For XIV systems and IBM Storage Accelerate, capacity represents the physical or ("hard") capacity of the pool, not the provisioned ("soft") capacity.

Used Capacity (Previously known as Allocated Space)

The amount of space that is reserved for all the volumes in a pool.

Used Capacity (%) (Previously known as Physical Allocation)

The percentage of physical capacity in the pool that is used by the standard-provisioned volumes, the thin-provisioned volumes, and the volumes in child pools. This value is always less than or equal to 100% because you cannot allocate more physical space than is available in a pool.

This value is determined by the formula, Used Capacity ÷ Capacity × 100. For example, if the space that is reserved for volumes is 50 GiB for a volume size of 200 GiB, used capacity is 25%.

Used Repository Space

The amount of used capacity on all extents in the repository of a pool. This attribute applies only to the DS8000 storage systems.

You can use this alert to be notified about space-efficient volumes.

Used Volume Space

The amount of space on the storage system that is used by volumes.

Used Written Capacity (%) (Previously known as Effective Used Capacity)

The percentage of capacity that is provisioned to the standard-provisioned volumes and the thin-provisioned volumes, given the drive compression savings.

Used Written Capacity (Previously known as Effective Used Capacity)

The total amount of total provisioned that is used by all the volumes given the drive compression savings.

User Reserved Capacity

The amount of space in the pools on the storage system that is reserved for user-defined purposes.

Virtual Capacity Limit

The maximum amount of virtual storage space available to allocate to volumes in the storage pools that are associated with the storage system.

You can use this alert to be notified about space-efficient volumes.

Virtual Volume Space

The total amount of physical space in a pool that is committed to the total virtual capacity of the volumes in the pool.

You can use this alert to be notified about space-efficient volumes.

Written Capacity Limit (Previously known as Effective Capacity)

The amount of total provisioned that can be created, given the drive compression savings.
Table 23. Triggering attributes and conditions for changes to performance metrics for cache fullness on pools
Performance Attributes Triggering Conditions for Attributes

Read and Write Cache Fullness

Define an alert to monitor the average amount of the lower cache which the pools' cache partitions on the nodes use for read and write operations. Use this alert to monitor the average cache fullness for read and write operations to identify the pools that experience heavy cache usage.

This metric applies to systems that are running IBM Storage Virtualize V7.3 or later.

Max Read and Write Cache Fullness

Define an alert to monitor the maximum amount of the lower cache, which the cache partitions on the nodes that manage the pool use for read and write operations. If the maximum value for the cache reaches 100%, one or more cache partitions on one or more pools is full. The operations that pass through the pools with full cache partitions will be queued and I/O response times will increase for the volumes in the affected pools.

This metric applies to systems that are running IBM Storage Virtualize V7.3 or later.

Quotas

Table 24. Triggering attributes and conditions for general changes on quotas
General Attributes Triggering Conditions for Attributes

Deleted Quota

A previously monitored quota can no longer be found. Historical data about the quota is retained, but no current data is being collected. Use this alert to be notified if a quota is deleted or becomes unavailable.

New Quota

A new quota was detected for the first time.

RAID Arrays

Table 25. Triggering attributes and conditions for general changes on RAID arrays
General Attributes Triggering Conditions for Attributes

New RAID Array

A new RAID array was detected for the first time.

Removed RAID Array

A previously monitored RAID array can no longer be found. Historical data about the RAID array is retained, but no current data is being collected. Use this alert to be notified if a RAID array is removed or becomes unavailable.

Status

One of the following statuses is detected for a RAID array:
Not Normal
An error or warning condition is detected on a RAID array.
Warning
A warning condition is detected on a RAID array.
Error
An error condition is detected on a RAID array.
Table 26. Triggering attributes and conditions for capacity changes on RAID arrays
Capacity Attributes Triggering Conditions for Attributes

Available Physical Capacity, Available Physical Capacity (%)

The amount and percentage of storage space that is unused on all the disk drive modules (DDMs) in the RAID array.

Available for RAID arrays with disk drive modules that use inline data compression, such as RAID arrays on IBM Storage FlashSystem 9100 and IBM Storage FlashSystem 900.

Compression Savings, Compression Savings (%)

For compressed RAID arrays, the amount and percentage of capacity that is saved by using drive compression.

Capacity (Previously known as Total Space)

For uncompressed RAID arrays, the total capacity is the same as the physical capacity and represents the total storage capacity of all the DDMs in the array.

For compressed RAID arrays, the total capacity is the estimated amount of data that can be written to the array. This value is larger than the physical capacity as the drive compression is used to reduce the size of the data.

Table 27. Triggering attributes and conditions for changes to performance metrics for RAID arrays
Performance Attribute Triggering Conditions for Attributes
Data Rate The average rate at which data is transferred in MiB per second.
I/O Rate The average number of operations per second.
Response Time The average number of milliseconds required to complete an operation.
Transfer size The average number of KiB that are transferred per I/O operation.
Disk Utilization Percentage The average percentage of time the disks that are associated with an array are busy.
Sequential I/O Percentage The percentage of operations among all I/O operations that were sequential I/O operations.

Device Adapters

Table 28. Triggering attributes and conditions for general changes on device adapters
General Attributes Triggering Conditions for Attributes

New Device Adapter

A new Device Adapter was detected for the first time.

Removed Device Adapter

A previously monitored Device Adapter can no longer be found. Historical data about the Device Adapter is retained, but no current data is being collected. Use this alert to be notified if a Device Adapter is removed or becomes unavailable.

Status

One of the following statuses is detected for a Device Adapter:
Not Normal
An error or warning condition is detected on a Device Adapter.
Warning
A warning condition is detected on a Device Adapter.
Error
An error condition is detected on a Device Adapter.
Table 29. Triggering attributes and conditions for changes to performance metrics for device adapters
Performance Attribute Triggering Conditions for Attributes
Data Rate The average rate at which data is transferred in MiB per second.
I/O Rate The average number of operations per second.
Response Time The average number of milliseconds required to complete an operation.
Transfer size The average number of KiB that are transferred per I/O operation.

Host Adapters

Table 30. Triggering attributes and conditions for general changes on host adapters
General Attributes Triggering Conditions for Attributes

New Host Adapter

A new Host Adapter was detected for the first time.

Removed Host Adapter

A previously monitored Host Adapter can no longer be found. Historical data about the Host Adapter is retained, but no current data is being collected. Use this alert to be notified if a Host Adapter is removed or becomes unavailable.

Status

One of the following statuses is detected for a Host Adapter:
Not Normal
An error or warning condition is detected on a Host Adapter.
Warning
A warning condition is detected on a Host Adapter.
Error
An error condition is detected on a Host Adapter.

Shares

Table 31. Triggering attributes and conditions for general changes on shares
General Attributes Triggering Conditions for Attributes

New Share

A new share was detected for the first time.

Deleted Share

A previously monitored share can no longer be found. Historical data about the share is retained, but no current data is being collected. Use this alert to be notified if a share is deleted or becomes unavailable.

Volumes

Table 32. Triggering attributes and conditions for general changes on volumes
General Attributes Triggering Conditions for Attributes

Deleted Volume

A previously monitored volume can no longer be found. Historical data about the volume is retained, but no current data is being collected. Use this alert to be notified if a volume is deleted or becomes unavailable.

If you are doing tasks where many volumes are being deleted, you might want to temporarily disable alerts that use the Deleted Volume attribute. For example, you might want to disable Deleted Volume alerts temporarily if you are doing maintenance tasks or decommissioning storage.

New Volume

A new volume was detected for the first time.

Status

One of the following statuses is detected for a volume:
Not Normal
An error or warning condition is detected on a RAID array.
Warning
A warning condition is detected on a RAID array.
Error
An error condition is detected on a RAID array.
Table 33. Triggering attributes and conditions for capacity changes on volumes
Capacity Attributes Triggering Conditions for Attributes

Compression Savings

The estimated percentage of capacity that is saved by using data compression. Inline compression is a software feature that is supported by IBM FlashSystem A9000 and IBM FlashSystem A9000R, IBM Storage Accelerate, XIV storage systems with firmware version 11.6 or later, and resources that run IBM Storage Virtualize.

Provisioned Capacity (Previously known as Unallocatable Space)

The amount of space by which the capacity of a volume exceeds the physical capacity of the associated pool. In thin-provisioned environments, it is possible to over commit (over provision) storage in a pool by creating volumes with more virtual capacity than can be physically allocated in the pool. This value represents the amount of volume space that cannot be allocated based on the current capacity of the pool.

Real Capacity

The total amount of storage space that is physically allocated to a volume. For thin-provisioned volumes, this value is less than the provisioned capacity of the volume. In an XIV and IBM Storage Accelerate, this value represents the physical ("hard") capacity of the volume, not the provisioned ("soft") capacity.

Remaining Managed Space

The amount of storage space that is available on a managed disk. This value is only available for Storwize V7000 storage systems that are configured as back-end storage.

Reserved Volume Capacity (Previously known as Unused Space)

The amount of pool capacity that is reserved but has not been used yet to store data on the thin-provisioned volume.

The value for Reserved Volume Capacity is available only for SAN Volume Controller and Storwize family storage systems that are configured with block storage.

Safeguarded Used Capacity (%) The percentage of safeguarded capacity currently used. For example, Safeguarded Used Capacity (%) is greater than or equal to 25%.

Space

The amount of space in a pool that is allocated to a volume.

Unused Capacity (Previously known as Unallocated Space)

The capacity in a pool that is not reserved for a volume. This value is determined by the formula: Capacity − Used Capacity

The value for Unused Capacity is available only for thin provisioned volumes.

Uncompressed Used Capacity

The amount of storage space that is used if the compressed volume space is uncompressed. For example, if 100 GiB of uncompressed data is compressed, and the size of the compressed data is 20 GiB, the value is 100.

Used Capacity (Previously known as Allocated Space)

The capacity on a pool that is physically allocated to a volume.

Written Capacity (Previously known as Written Space) The amount of data that is written from the assigned hosts to the volume before compression or data deduplication are used to reduce the size of the data.
Table 34. Triggering attributes and conditions for changes to performance metrics for unmap operations on volumes
Performance Attribute Triggering Conditions for Attributes
Data Rate (Unmap) Define an alert to monitor the average number of MiBs per second that were unmapped.

This metric applies to systems that are running IBM Storage Virtualize V8.1.1 or later.

Overall I/O Rate (Unmap) Define an alert to monitor the average number of unmap operations per second.

This metric applies to systems that are running IBM Storage Virtualize V8.1.1 or later.

Peak Response Time (Unmap) Define an alert to monitor the worst response time measured for an unmap operation in the sample interval.

This metric applies to systems that are running IBM Storage Virtualize V8.1.1 or later.

Response Time (Unmap) Define an alert to monitor the average number of milliseconds required to complete an unmap operation.

This metric applies to systems that are running IBM Storage Virtualize V8.1.1 or later.

Unaligned Unmap I/O Rate Define an alert to monitor the average number of volumes unmap operations per second that are not aligned on an 8K boundary.

This metric applies to systems that are running IBM Storage Virtualize V8.1.1 or later.

Start of change

Volume Groups

Table 35. Triggering attributes and conditions for security alerts on volumes
Performance Attribute Triggering Conditions for Attributes

Workload Anomaly Event

The combination of advanced compression formulas and entropy analysis at the node and volume level of a storage system. Use this attribute to identify when conditions on an IBM Storage Virtualize storage system might indicate a ransomware attack.

Tip: The IBM Storage Insights team used proactive, multi-condition alerts with the Workload Anomaly Event attribute to help identify when the conditions for an attack are met so that they can help mitigate the impact to your business.
Table 36. Triggering attributes and conditions for changes to snapshot capacity metrics for unmap operations on volume groups
Performance Attribute Triggering Conditions for Attributes
Snapshot Provisioned capacity* Define an alert to be notified when the amount of provisioned capacity that is used for a volume group snapshot reaches a specified threshold.
Snapshot Provisioned capacity* In the default alert policy for IBM Storage Virtualize storage systems, this attribute triggers an alert when over 80% of the pool space is used
End of change