Supported Metrics
The following tabs represent the Metric Category of Vast Data Platform
Availability
Capacity
Usage
Performance
| Native Type | Metric Name | Display Name | Units | Application Version | Description | Is Default Metric |
|---|---|---|---|---|---|---|
| Vast Data Cluster | vastdata_cluster_license_Status | License Status | Count | 1.0.0 | License Status.Possible States are EXPIRED(0), ACTIVE(1) and PENDING(2).Pending means not yet activated. The license is either initializing or the start date is in the future. Expired means the expiration date has passed and the license is no longer active. Active means the start date has passed and the license was activated. | Yes |
| vastdata_cluster_cnode_Cores | Cluster CNode Cores Count | Count | 1.0.0 | Number of CNode Cores. | Yes | |
| vastdata_cluster_leader_Status | Cluster Leader Status | Count | 1.0.0 | Cluster Leader Status.Possible states are DOWN(0), UP(1) and UNKNOWN(3). | Yes | |
| vastdata_cluster_Status | Cluster Status | 1.0.0 | Cluster Status.Possible states are UNKNOWN(0), ONLINE(1), INIT(2), ACTIVATING(3), OFFLINE(4) and FAILED(5). | Yes | ||
| vastdata_snapshot_IsLocked | Snapshot Is Locked | 1.0.0 | Lock the snapshot from being deleted by cleanup. Return TRUE if snapshot is Locked else FALSE. | Yes | ||
| vastdata_snapshot_Status | Snapshot Status | 1.0.0 | Snapshot status.Possible states are FAILED(0), SUCCEED(1), CREATING(2), INIT(3), RETRYING(4), DELETING(5), RETRY_DELETE(6). | Yes | ||
| Vast Data CBox | vastdata_cbox_Status | CBox Status | 1.0.0 | CBox Status. Possible states are UNKNOWN(0), ACTIVE(1), ACTIVATING(2), INIT(3), INACTIVE(4), DEACTIVATING(5), FAILED(6), FAILING(7), COUNT(8). | Yes | |
| Vast Data Cnode | vastdata_cnode_led_Status | CNode LED Status | 1.0.0 | CNode LED Status. | Yes | |
| vastdata_cnode_Status | CNode Status | 1.0.0 | CNode Status. Possible States are UNKNOWN(0), ACTIVE(1), ACTIVATING(2), INIT(3), INACTIVE(4), DEACTIVATING(5), FAILED(6), FAILING(7), COUNT(8). | Yes | ||
| Vast Data DBox | vastdata_dbox_Status | DBox Status | 1.0.0 | DBox Status. Possible States are UNKNOWN(0), ACTIVE(1), ACTIVATING(2), INIT(3), INACTIVE(4), DEACTIVATING(5), FAILED(6), FAILING(7), COUNT(8). | Yes | |
| Vast Data DNode | vastdata_dnode_led_Status | DNode LED Status | 1.0.0 | DNode LED Status, Possible states are OFF(0), ON(1) and BLINK(2). | Yes | |
| vastdata_dnode_Status | DNode Status | 1.0.0 | DNode Status. Possible States are UNKNOWN(0), ACTIVE(1), ACTIVATING(2), INIT(3), INACTIVE(4), DEACTIVATING(5), FAILED(6), FAILING(7), COUNT(8). | Yes | ||
| Vast Data SSD | vastdata_ssd_IsEnabled | SSD Is Enabled | 1.0.0 | SSD Enabled.Possible values are TRUE and FALSE. | Yes | |
| vastdata_ssd_Status | SSD Status | 1.0.0 | SSD Status. Possible values are UNKNOWN(0), HEALTHY(1), FAILED(2), LOGIN_FAILED(3), FAILING(4), ACTIVE(5), ACTIVATING(6), INACTIVE(7), DEACTIVATING(8), PHASING_OUT(9), ENTER_PHASING_OUT(10), EXIT_PHASING_OUT(11). | Yes | ||
| Vast Data NVRAM | vastdata_nvram_IsEnabled | NVRAM Is Enabled | 1.0.0 | NVRAM Enabled.Possible values are TRUE and FALSE. | Yes | |
| vastdata_nvram_Status | NVRAM Status | 1.0.0 | NVRAM Status. Possible values are UNKNOWN(0), HEALTHY(1), FAILED(2), LOGIN_FAILED(3), FAILING(4), ACTIVE(5), ACTIVATING(6), INACTIVE(7), DEACTIVATING(8), PHASING_OUT(9), ENTER_PHASING_OUT(10), EXIT_PHASING_OUT(11). | Yes | ||
| Vast Data NIC | vastdata_nic_link_Status | NIC Link Status | 1.0.0 | NIC Link Status,Possible staes are UNKNOWN(0), UP(1), DOWN(2). | Yes | |
| vastdata_nic_Status | NIC Status | 1.0.0 | NIC Status, Possible staes are UNKNOWN(0), HEALTHY(1), FAILED(2), LOGIN_FAILED(3), FAILING(4), ACTIVE(5), ACTIVATING(6), INACTIVE(7), DEACTIVATING(8), PHASING_OUT(9), ENTER_PHASING_OUT(10), EXIT_PHASING_OUT(11), UP(12), DOWN(13). | Yes | ||
| Vast Data PSU | vastdata_psu_Status | PSU Status | 1.0.0 | PSU Status Possible states are UNKNOWN(0), HEALTHY(1), FAILED(2), LOGIN_FAILED(3), FAILING(4), ACTIVE(5), ACTIVATING(6), INACTIVE(7), DEACTIVATING(8), PHASING_OUT(9), ENTER_PHASING_OUT(10), EXIT_PHASING_OUT(11), UP(12), DEGRADED(13), DISCONNECTED_CABLE(14), AC_LOST(15), PREDICTIVE_FAILURE(16), CONFIGURATION_ERROR(17), PSU_OUT(18), PSU_NOT_PRESENT(19). | Yes | |
| Vast Data Fan | vastdata_fan_Status | Fan Status | 1.0.0 | Fan Status. Possible states are UNKNOWN(0), HEALTHY(1), OK(2), FAILED(3), LOGIN_FAILED(4), FAILING(5), ACTIVE(6), ACTIVATING(7), INACTIVE(8), DEACTIVATING(9), PHASING_OUT(10), ENTER_PHASING_OUT(11), EXIT_PHASING_OUT(12), LOWER_NON_RECOVERABLE(13), LOWER_CRITICAL(14), LOWER_NON_CRITICAL(15). | Yes | |
| Vast Data Switch | vastdata_switch_Status | Switch Status | 1.0.0 | Switch Status, Possible states are UNKNOWN(0), HEALTHY(1), OK(2), ERROR(3), FAILED(4), LOGIN_FAILED(5), FAILING(6), ACTIVE(7), ACTIVATING(8), INACTIVE(9), DEACTIVATING(10), PHASING_OUT(11), ENTER_PHASING_OUT(12), EXIT_PHASING_OUT(13). | Yes | |
| vastdata_switch_port_Status | Switch Port Status | 1.0.0 | Port Status, Possible states are UNKNOWN(0), HEALTHY(1), FAILED(2), LOGIN_FAILED(3), FAILING(4), ACTIVE(5), ACTIVATING(5), INACTIVE(7), DEACTIVATING(8), PHASING_OUT(9), ENTER_PHASING_OUT(10), EXIT_PHASING_OUT(11), UP(12), DOWN(13). | Yes | ||
| Vast Data Quota | vastdata_quota_Blockedusers | Quota Blocked Users | count | 1.0.0 | The number of users that are blocked from writing to the quota path due to exceeding a hard user/group quota limit. | Yes |
| vastdata_quota_ExceededUsers | Quota Exceeded Users | 1.0.0 | The number of users that have exceeded a user quota. | Yes | ||
| vastdata_quota_Status | Quota Status | 1.0.0 | Quota Status.Possible states are FAILED(0), OK(1), GRACE_EXPIRED(2), HARD_EXCEEDED(3), INODE_HARD_EXCEEDED(4), HARD_BOTH_EXCEEDED(5), SOFT_EXCEEDED(6), INODE_SOFT_EXCEEDED(7), SOFT_BOTH_EXCEEDED(8). | Yes |
| Native Type | Metric Name | Display Name | Units | Application Version | Description | Is Default Metric |
|---|---|---|---|---|---|---|
| Vast Data Cluster | vastdata_cluster_license_ValidPeriod | License validity period | Count | 1.0.0 | The period, in Days, for which the license is valid. The period begins on the start date. Unlimited means that the license does not expire. | No |
| vastdata_cluster_license_ValidPeriodIsUnlimited | License Validity Period Is Unlimited | Days | 2.0.0 | Returns TRUE if License validity period is UNLIMITED else FALSE. | No | |
| vastdata_cluster_drive_Size | Cluster Drive Size | TB | 1.0.0 | Drive size for mocked devices | Yes | |
| vastdata_cluster_license_Capacity | License Capacity | TB | 2.0.0 | The usable capacity allowed by the license. | Yes | |
| vastdata_cluster_license_CapacityIsUnlimited | License Capacity Is Unlimited | 2.0.0 | Return TRUE if License capacity is UNLIMITED else FALSE. | Yes | ||
| vastdata_cluster_license_DaysRemainForExpiry | Days remain for License Expiry | Days | 2.0.0 | Days remain for License Expiry. | Yes | |
| vastdata_cluster_license_IsUnlimitedExpiry | License Expiry Is Unlimited | Days | 2.0.0 | Return TRUE if License doesn't expire else FALSE. | Yes | |
| vastdata_cluster_DataReductionRatio | Cluster Data Reduction Ratio | 1.0.0 | Data reduction ratio (logical_space_in_use / physical_space_in_use) | Yes | ||
| vastdata_cluster_FreeUsableCapacity | Cluster Free Usable Capacity | TB | 1.0.0 | The amount of usable capacity that is not in use, in TB. | Yes | |
| vastdata_cluster_logical_DataReductionRatio | Cluster Logical Data Reduction Ratio | % | 1.0.0 | Logical data reduction ratio percentage | Yes | |
| vastdata_cluster_logical_Space | Cluster Total Estimated Logical Space | TB | 1.0.0 | Total Estimated Logical Space | Yes | |
| vastdata_cluster_nvram_Size | Cluster NVRAM Size | TB | 1.0.0 | NVRAM Size | Yes | |
| vastdata_cluster_physical_DataReductionRatio | Cluster Physical data reduction ratio percentage | % | 1.0.0 | Physical data reduction ratio percentage | Yes | |
| vastdata_cluster_physical_Space | Cluster Total Physical Space | TB | 1.0.0 | Total Physical Space | Yes | |
| vastdata_cluster_quota_Capacity | Cluster Quota Allocated Capacity | TB | 1.0.0 | Cluster Quota Allocated Capacity | Yes | |
| vastdata_cluster_UsableCapacity | Cluster Usable Capacity | TB | 1.0.0 | The usable capacity of the cluster, in TB. This is always smaller than the physical capacity due to an overhead introduced by data protection. VAST Cluster protects data with RAID stripes. The data protection overhead varies by size of stripe which in turn varies based upon the number of storage enclosures (DBoxes) in a cluster. | Yes | |
| vastdata_snapshot_DaysRemainForExpiry | Snapshot Expiration Time In Days | Days | 1.0.0 | Snapshot Expiration Time In Days | Yes | |
| Vast Data SSD | vastdata_ssd_TotalSpace | SSD Total Space | Count | 1.0.0 | Total SSD space | Yes |
| Vast Data NVRAM | vastdata_nvram_TotalSpace | NVRAM Total Space | TB | 1.0.0 | Total NVRAM space | Yes |
| Vast Data Quota | vastdata_quota_CapacityUtilisation | Quota Capacity Usage In Percentage | % | 1.0.0 | Percentage of capacity limit in use | Yes |
| Native Type | Metric Name | Display Name | Units | Application Version | Description | Is Default Metric |
|---|---|---|---|---|---|---|
| Vast Data Cluster | vastdata_cluster_api_Statistics | Cluster Api Statistics | Count | 1.0.0 | Returns number of Api calls happened for each nativetype for every monitoring poll. | No |
| vastdata_cluster_estore_CapacityInUse | Cluster Logical Space In Use | TB | 1.0.0 | Logical Space In Use (TB) | Yes | |
| vastdata_cluster_logical_FreeSpace | Cluster Logical Free Space | TB | 1.0.0 | The estimated effective free capacity remaining for writing data to the cluster, computed dynamically based upon the observed DRR and overhead impact | Yes | |
| vastdata_cluster_physical_FreeSpace | Cluster Physical Free Space | TB | 1.0.0 | Free Physical Space | Yes | |
| vastdata_cluster_physical_UsableSpace | Cluster Physical Usable Free Space | TB | 1.0.0 | Free Usable Space, in TB | Yes | |
| vastdata_cluster_logicalauxiliary_SpaceInUse | Cluster Logical Auxiliary Space In Use | TB | 1.0.0 | The amount of logical data written to the cluster that was deleted and is being held as auxiliary data, either by snapshots or as deletion in process, in TB | Yes | |
| vastdata_cluster_logical_InodeCount | Cluster Logical Inodes Count | count | 1.0.0 | Number of files and directories | Yes | |
| vastdata_cluster_logical_SpaceUsePercent | Cluster Logical Space Use Percentage | % | 1.0.0 | Logical space in use percentage | Yes | |
| vastdata_cluster_logical_SpaceInUse | Cluster Logical Space In Use | TB | 1.0.0 | Logical Space In Use | Yes | |
| vastdata_cluster_physical_SpaceUsePercent | Cluster Physical space in use percentage | % | 1.0.0 | Physical space in use percentage | Yes | |
| vastdata_cluster_physical_SpaceInUse | Cluster Physical Space In Use | TB | 1.0.0 | Physical Space In Use | Yes | |
| vastdata_cluster_quota_UsedCapacity | Cluster Quota Used Capacity | TB | 1.0.0 | Cluster Quota Used Capacity | Yes | |
| vastdata_cluster_quota_CapcityUtilisation | Cluster Quota Used Capacity Percentage | % | 1.0.0 | Cluster Quota Used Capacity Percentage | Yes | |
| Vast Data SSD | vastdata_ssd_SpaceInUse | SSD space in use | TB | 1.0.0 | SSD space in use. | Yes |
| Vast Data NVRAM | vastdata_nvram_SpaceInUse | NVRAM space in use | TB | 1.0.0 | NVRAM space in use. | Yes |
| Vast Data Quota | vastdata_quota_PercentageIndoes | Quota Files and Directories Limit Usage In Percentage | % | 1.0.0 | Percentage of files and directories limit in use. | Yes |
| vastdata_quota_PercentageIndoes | Quota Files and Directories Limit Usage In Percentage | % | 1.0.0 | Percentage of files and directories limit in use. | Yes | |
| vastdata_quota_UsedCapacity | Quota Used Capacity | TB | 1.0.0 | Used capacity in TB. | Yes | |
| vastdata_quota_UsedIndoes | Quota unique files and directories count | Count | 1.0.0 | Number of directories and unique files under the path. | Yes | |
| vastdata_quota_UsedLimitedCapacity | Quota Limited Used Capacity | TB | 1.0.0 | Used Limited capacity in TB. | Yes |
| Native Type | Metric Name | Display Name | Units | Application Version | Description | Is Default Metric |
|---|---|---|---|---|---|---|
| Vast Data Cluster | vastdata_cluster_Bandwidth | Cluster Bandwidth | MB | 1.0.0 | Cluster Bandwidth. | Yes |
| vastdata_cluster_Iops | Cluster IOPS | IOPS | 1.0.0 | Cluster IOPS | Yes | |
| vastdata_cluster_Latency | Cluster Latency | ms | 1.0.0 | Cluster Latency | Yes | |
| vastdata_cluster_metadata_Iops | Cluster Meta Data IOPS | IOPS | 1.0.0 | Meta-data IOPS | Yes | |
| vastdata_cluster_ndb_Bandwidth | Cluster NDB query bandwidth total (MB) | MB | 1.0.0 | NDB query bandwidth total (MB) | Yes | |
| vastdata_cluster_ndb_ReadBandwidth | Cluster NDB query bandwidth read (MB) | MB | 1.0.0 | NDB query bandwidth read (MB) | Yes | |
| vastdata_cluster_ndb_WriteBandwidth | Cluster NDB query bandwidth write (MB) | MB | 1.0.0 | NDB query bandwidth write (MB) | Yes | |
| vastdata_cluster_read_Bandwidth | Cluster Read Bandwidth | MB | 1.0.0 | Read Bandwidth | Yes | |
| vastdata_cluster_read_Iops | Cluster Read IOPS | rops | 1.0.0 | Read IOPS | Yes | |
| vastdata_cluster_read_Latency | Cluster Read Latency | ms | 1.0.0 | Read Latency | Yes | |
| vastdata_cluster_metadata_ReadIops | Cluster Read Meta-data IOPS | rops | 1.0.0 | Read Meta-data IOPS | Yes | |
| vastdata_cluster_replication_Bandwidth | Cluster Replication Bandwidth | MB | 1.0.0 | Replication Bandwidth | Yes | |
| vastdata_cluster_replication_Iops | Cluster Replication IOPS | IOPS | 1.0.0 | Replication IOPS | Yes | |
| vastdata_cluster_replication_Latency | Cluster Replication Latency | ms | 1.0.0 | Replication Latency | Yes | |
| vastdata_cluster_replication_ReadBandwidth | Cluster Replication Read Bandwidth | MB | 1.0.0 | Replication Read Bandwidth | Yes | |
| vastdata_cluster_replication_ReadIops | Cluster Replication Read IOPS | rops | 1.0.0 | Replication Read IOPS | Yes | |
| vastdata_cluster_replication_ReadLatency | Cluster Replication Read Latency | ms | 1.0.0 | Replication Read Latency | Yes | |
| vastdata_cluster_replication_WriteBandwidth | Cluster Replication Write Bandwidth | MB | 1.0.0 | Replication Write Bandwidth | Yes | |
| vastdata_cluster_replication_WriteIops | Cluster Replication Write IOPS | wops | 1.0.0 | Replication Write IOPS | Yes | |
| vastdata_cluster_replication_WriteLatency | Cluster Replication Write Latency | ms | 1.0.0 | Replication Write Latency | Yes | |
| vastdata_cluster_write_Bandwidth | Cluster Write Bandwidth | MB | 1.0.0 | Write Bandwidth | Yes | |
| vastdata_cluster_write_Iops | Cluster Write IOPS | wops | 1.0.0 | Write IOPS | Yes | |
| vastdata_cluster_write_Latency | Cluster Write Latency | ms | 1.0.0 | Write Latency | Yes | |
| vastdata_cluster_metadata_WriteIops | Cluster Write Meta Data IOPS | wops | 1.0.0 | Write MetaData IOPS | Yes | |
| Vast Data Fan | vastdata_fan_Speed | Fan Speed | rpm | 1.0.0 | Fan Speed. | Yes |
Default Monitoring Configurations
Vast Data Platform has default Global Device Management Policies, Global Templates, Global Monitors and Global metrics in OpsRamp. User can customise these default monitoring configurations as per their business use cases by cloning respective global templates and global Device Management Policies. OpsRamp recommend to do this activity before installing the app to avoid noise alerts and data.
Default Global Device Management PoliciesOpsRamp will have a Global Device Management Policy for each Native Type of Vast Data Platform. We can find those Device Management Policies at Setup → Resources → Device Management Policies → Search with suggested names in global scope.
Each Device Management Policy follows below naming convention :
{appName nativeType - version}
Ex : vast-data-platfrom Vast Data Cluster - 1 (i.e, appName = vast-data-platfrom, nativeType =Vast Data Cluster, version = 1)
Default Global TemplatesOpsRamp will have a Global template for each Native Type of Vast Data Platform. We can find those templates at Setup → Monitoring → Templates → Search with suggested names in global scope.
Each template follows below naming convention :
{appName nativeType 'Template' - version}
Ex : vast-data-platfrom Vast Data Cluster Template - 1 (i.e, appName = vast-data-platfrom , nativeType = Vast Data Cluster Template, version = 1)
Default Global MonitorsOpsRamp will have a Global Monitors for each Native Type which has monitoring support. We can find those monitors at Setup → Monitoring → Monitors → Search with suggested names in global scope.
Each Monitors follows below naming convention :
{monitorKey appName nativeType - version}
Ex : Vast Data Cluster Monitor vast-data-platfrom Vast Data Cluster 1 (i.e, monitorKey = Vast Data Cluster Monitor, appName = vast-data-platfrom, nativeType = Vast Data Cluster, version = 1)