Time interval for the SNMP availability trigger.

Warning threshold of ICMP packet loss in %.

Warning threshold of the average ICMP response time in seconds.

MIB: SNMPv2-MIB

Time (in hundredths of a second) since the network management portion of the system was last re-initialized.

Preprocessing

• Custom multiplier: 0.01

MIB: HOST-RESOURCES-MIB

The amount of time since this host was last initialized. Note that this is different from sysUpTime in the SNMPv2-MIB [RFC1907] because sysUpTime is the uptime of the network management portion of the system.

Preprocessing

• Check for not supported value: any error

  ⛔️Custom on fail: Set value to: 0

• Custom multiplier: 0.01

The item is used to collect all SNMP traps unmatched by other snmptrap items

MIB: SNMPv2-MIB

Physical location of the node (e.g., equipment room, 3rd floor). If not provided, the value is a zero-length string.

Preprocessing

• Discard unchanged with heartbeat: 12h

MIB: SNMPv2-MIB

The textual identification of the contact person for this managed node, together with information on how to contact this person. If no contact information is known, the value is the zero-length string.

Preprocessing

• Discard unchanged with heartbeat: 12h

MIB: SNMPv2-MIB

The vendor's authoritative identification of the network management subsystem contained in the entity. This value is allocated within the SMI enterprises subtree (1.3.6.1.4.1) and provides an easy and unambiguous means for determiningwhat kind of box' is being managed. For example, if vendorFlintstones, Inc.' was assigned the subtree1.3.6.1.4.1.4242, it could assign the identifier 1.3.6.1.4.1.4242.1.1 to its `Fred Router'.

Preprocessing

• Discard unchanged with heartbeat: 12h

MIB: SNMPv2-MIB

An administratively-assigned name for this managed node.By convention, this is the node's fully-qualified domain name. If the name is unknown, the value is the zero-length string.

Preprocessing

• Discard unchanged with heartbeat: 12h

MIB: SNMPv2-MIB

A textual description of the entity. This value should

include the full name and version identification of the system's hardware type, software operating-system, and

networking software.

Preprocessing

• Discard unchanged with heartbeat: 12h

Availability of SNMP checks on the host. The value of this item corresponds to availability icons in the host list.

Possible values:

0 - not available

1 - available

2 - unknown

Uptime is less than 10 minutes.

• Supermicro Aten: No SNMP data collection

The name of the system has changed. Acknowledge to close the problem manually.

SNMP is not available for polling. Please check device connectivity and SNMP settings.

• Supermicro Aten: Unavailable by ICMP ping

Last three attempts returned timeout. Please check device connectivity.

• Supermicro Aten: Unavailable by ICMP ping

Average ICMP response time is too high.

• Supermicro Aten: High ICMP ping loss
• Supermicro Aten: Unavailable by ICMP ping

Scanning ATEN-IPMI-MIB::sensorTable with filter: not connected temp sensors (Value = 0)

MIB: ATEN-IPMI-MIB

A textual string containing information about the interface.

This string should include the name of the manufacturer, the product name and the version of the interface hardware/software.

This trigger uses temperature sensor values as well as temperature sensor status if available

• Supermicro Aten: {#SENSOR_DESCR}: Temperature is above critical threshold

This trigger uses temperature sensor values as well as temperature sensor status if available

Scanning ATEN-IPMI-MIB::sensorTable with filter: not connected FAN sensors (Value = 0)

MIB: ATEN-IPMI-MIB

A textual string containing information about the interface.

This string should include the name of the manufacturer, the product name and the version of the interface hardware/software.

This macro is used for trigger expression. It can be overridden on the host or linked on the template level.

This macro is used for trigger expression. It can be overridden on the host or linked on the template level.

This macro is used in the filter of attribute and disk discoveries. It can be overridden on the host or linked on the template level.

This macro is used in the filter of attribute and disk discoveries. It can be overridden on the host or linked on the template level.

Discovery SMART disks.

This metric will contain smartctl errors.

Preprocessing

• JSON Path: $.error

• Discard unchanged with heartbeat: 1h

Preprocessing

• JSON Path: $.model_name

• Discard unchanged with heartbeat: 6h

Preprocessing

• JSON Path: $.serial_number

• Discard unchanged with heartbeat: 6h

The disk is passed the SMART self-test or not.

Preprocessing

• JSON Path: $.self_test_passed

• Discard unchanged with heartbeat: 6h

Current drive temperature.

Preprocessing

• JSON Path: $.temperature

• Discard unchanged with heartbeat: 6h

Count of hours in power-on state. The raw value of this attribute

shows total count of hours (or minutes, or seconds, depending on manufacturer)

in power-on state. "By default, the total expected lifetime of a hard disk

in perfect condition is defined as 5 years (running every day and night on

all days). This is equal to 1825 days in 24/7 mode or 43800 hours." On some

pre-2005 drives, this raw value may advance erratically and/or "wrap around"

(reset to zero periodically). https://en.wikipedia.org/wiki/S.M.A.R.T.#KnownATAS.M.A.R.T._attributes

Preprocessing

• JSON Path: $.power_on_time

• Discard unchanged with heartbeat: 6h

Contains a vendor specific estimate of the percentage of NVM subsystem

life used based on the actual usage and the manufacturer's prediction of NVM

life. A value of 100 indicates that the estimated endurance of the NVM in

the NVM subsystem has been consumed, but may not indicate an NVM subsystem

failure. The value is allowed to exceed 100. Percentages greater than 254

shall be represented as 255. This value shall be updated once per power-on

hour (when the controller is not in a sleep state).

Preprocessing

• JSON Path: $.percentage_used

• Discard unchanged with heartbeat: 6h

This field indicates critical warnings for the state of the controller.

Preprocessing

• JSON Path: $.critical_warning

• Discard unchanged with heartbeat: 6h

Contains the number of occurrences where the controller detected

an unrecovered data integrity error. Errors such as uncorrectable ECC, CRC

checksum failure, or LBA tag mismatch are included in this field.

Preprocessing

• JSON Path: $.media_errors

• Discard unchanged with heartbeat: 6h

The exit statuses of smartctl are defined by a bitmask but in decimal value. The eight different bits in the exit status have the following meanings for ATA disks; some of these values may also be returned for SCSI disks.

Bit 0: Command line did not parse.

Bit 1: Device open failed, device did not return an IDENTIFY DEVICE structure, or device is in a low-power mode (see '-n' option above).

Bit 2: Some SMART or other ATA command to the disk failed, or there was a checksum error in a SMART data structure (see '-b' option above).

Bit 3: SMART status check returned "DISK FAILING".

Bit 4: We found prefail Attributes <= threshold.

Bit 5: SMART status check returned "DISK OK" but we found that some (usage or prefail) Attributes have been <= threshold at some time in the past.

Bit 6: The device error log contains records of errors.

Bit 7: The device self-test log contains records of errors. [ATA only] Failed self-tests outdated by a newer successful extended self-test are ignored.

Preprocessing

• JSON Path: $.exit_status

• Discard unchanged with heartbeat: 6h

Stores data related to the rate of hardware read errors that occurred when reading data from a disk surface. The raw value has different structure for different vendors and is often not meaningful as a decimal number. For some drives, this number may increase during normal operation without necessarily signifying errors.

Preprocessing

• JSON Path: $.raw_read_error_rate.value

• Discard unchanged with heartbeat: 6h

Average time of spindle spin up (from zero RPM to fully operational [milliseconds]).

Preprocessing

• JSON Path: $.spin_up_time.value

• Discard unchanged with heartbeat: 6h

A tally of spindle start/stop cycles. The spindle turns on, and hence the count is increased, both when the hard disk is turned on after having before been turned entirely off (disconnected from power source) and when the hard disk returns from having previously been put to sleep mode.

Preprocessing

• JSON Path: $.start_stop_count.value

• Discard unchanged with heartbeat: 6h

This attribute indicates the count of full hard disk power on/off cycles.

Preprocessing

• JSON Path: $.power_cycle_count.value

• Discard unchanged with heartbeat: 6h

The count of errors that could not be recovered using hardware ECC.

Preprocessing

• JSON Path: $.reported_uncorrect.value

• Discard unchanged with heartbeat: 6h

Rate of seek errors of the magnetic heads. If there is a partial failure in the mechanical positioning system, then seek errors will arise. Such a failure may be due to numerous factors, such as damage to a servo, or thermal widening of the hard disk. The raw value has different structure for different vendors and is often not meaningful as a decimal number. For some drives, this number may increase during normal operation without necessarily signifying errors.

Preprocessing

• JSON Path: $.seek_error_rate.value

• Discard unchanged with heartbeat: 6h

Percentage of used reserve blocks divided by total reserve blocks.

Preprocessing

• JSON Path: $.bad_block_rate.value

• Discard unchanged with heartbeat: 6h

The total number of flash program operation failures since the drive was deployed.

Preprocessing

• JSON Path: $.program_fail_count_chip.value

• Discard unchanged with heartbeat: 6h

Disk discovered attribute.

Preprocessing

• JSON Path: $.reallocated_sector_ct.value

• Discard unchanged with heartbeat: 6h

Device serial number has changed. Acknowledge to close the problem manually.

• SMART: [{#NAME}]: Average disk temperature is critical

Command line did not parse.

Device open failed, device did not return an IDENTIFY DEVICE structure, or device is in a low-power mode.

Some SMART or other ATA command to the disk failed,
or there was a checksum error in a SMART data structure.

SMART status check returned "DISK FAILING".

We found prefail Attributes <= threshold.

SMART status check returned "DISK OK" but we found that some (usage
or prefail) Attributes have been <= threshold at some time in the past.

The device error log contains records of errors.

The device self-test log contains records of errors. [ATA only]
Failed self-tests outdated by a newer successful extended self-test are ignored.

This macro is used for trigger expression. It can be overridden on the host or linked on the template level.

This macro is used for trigger expression. It can be overridden on the host or linked on the template level.

This macro is used in the filter of attribute and disk discoveries. It can be overridden on the host or linked on the template level.

This macro is used in the filter of attribute and disk discoveries. It can be overridden on the host or linked on the template level.

Discovery SMART disks.

This metric will contain smartctl errors.

Preprocessing

• JSON Path: $.error

• Discard unchanged with heartbeat: 1h

Preprocessing

• JSON Path: $.model_name

• Discard unchanged with heartbeat: 6h

Preprocessing

• JSON Path: $.serial_number

• Discard unchanged with heartbeat: 6h

The disk is passed the SMART self-test or not.

Preprocessing

• JSON Path: $.self_test_passed

• Discard unchanged with heartbeat: 6h

Current drive temperature.

Preprocessing

• JSON Path: $.temperature

• Discard unchanged with heartbeat: 6h

Count of hours in power-on state. The raw value of this attribute

shows total count of hours (or minutes, or seconds, depending on manufacturer)

in power-on state. "By default, the total expected lifetime of a hard disk

in perfect condition is defined as 5 years (running every day and night on

all days). This is equal to 1825 days in 24/7 mode or 43800 hours." On some

pre-2005 drives, this raw value may advance erratically and/or "wrap around"

(reset to zero periodically). https://en.wikipedia.org/wiki/S.M.A.R.T.#KnownATAS.M.A.R.T._attributes

Preprocessing

• JSON Path: $.power_on_time

• Discard unchanged with heartbeat: 6h

Contains a vendor specific estimate of the percentage of NVM subsystem

life used based on the actual usage and the manufacturer's prediction of NVM

life. A value of 100 indicates that the estimated endurance of the NVM in

the NVM subsystem has been consumed, but may not indicate an NVM subsystem

failure. The value is allowed to exceed 100. Percentages greater than 254

shall be represented as 255. This value shall be updated once per power-on

hour (when the controller is not in a sleep state).

Preprocessing

• JSON Path: $.percentage_used

• Discard unchanged with heartbeat: 6h

This field indicates critical warnings for the state of the controller.

Preprocessing

• JSON Path: $.critical_warning

• Discard unchanged with heartbeat: 6h

Contains the number of occurrences where the controller detected

an unrecovered data integrity error. Errors such as uncorrectable ECC, CRC

checksum failure, or LBA tag mismatch are included in this field.

Preprocessing

• JSON Path: $.media_errors

• Discard unchanged with heartbeat: 6h

The exit statuses of smartctl are defined by a bitmask but in decimal value. The eight different bits in the exit status have the following meanings for ATA disks; some of these values may also be returned for SCSI disks.

Bit 0: Command line did not parse.

Bit 1: Device open failed, device did not return an IDENTIFY DEVICE structure, or device is in a low-power mode (see '-n' option above).

Bit 2: Some SMART or other ATA command to the disk failed, or there was a checksum error in a SMART data structure (see '-b' option above).

Bit 3: SMART status check returned "DISK FAILING".

Bit 4: We found prefail Attributes <= threshold.

Bit 5: SMART status check returned "DISK OK" but we found that some (usage or prefail) Attributes have been <= threshold at some time in the past.

Bit 6: The device error log contains records of errors.

Bit 7: The device self-test log contains records of errors. [ATA only] Failed self-tests outdated by a newer successful extended self-test are ignored.

Preprocessing

• JSON Path: $.exit_status

• Discard unchanged with heartbeat: 6h

Stores data related to the rate of hardware read errors that occurred when reading data from a disk surface. The raw value has different structure for different vendors and is often not meaningful as a decimal number. For some drives, this number may increase during normal operation without necessarily signifying errors.

Preprocessing

• JSON Path: $.raw_read_error_rate.value

• Discard unchanged with heartbeat: 6h

Average time of spindle spin up (from zero RPM to fully operational [milliseconds]).

Preprocessing

• JSON Path: $.spin_up_time.value

• Discard unchanged with heartbeat: 6h

A tally of spindle start/stop cycles. The spindle turns on, and hence the count is increased, both when the hard disk is turned on after having before been turned entirely off (disconnected from power source) and when the hard disk returns from having previously been put to sleep mode.

Preprocessing

• JSON Path: $.start_stop_count.value

• Discard unchanged with heartbeat: 6h

This attribute indicates the count of full hard disk power on/off cycles.

Preprocessing

• JSON Path: $.power_cycle_count.value

• Discard unchanged with heartbeat: 6h

The count of errors that could not be recovered using hardware ECC.

Preprocessing

• JSON Path: $.reported_uncorrect.value

• Discard unchanged with heartbeat: 6h

Rate of seek errors of the magnetic heads. If there is a partial failure in the mechanical positioning system, then seek errors will arise. Such a failure may be due to numerous factors, such as damage to a servo, or thermal widening of the hard disk. The raw value has different structure for different vendors and is often not meaningful as a decimal number. For some drives, this number may increase during normal operation without necessarily signifying errors.

Preprocessing

• JSON Path: $.seek_error_rate.value

• Discard unchanged with heartbeat: 6h

Percentage of used reserve blocks divided by total reserve blocks.

Preprocessing

• JSON Path: $.bad_block_rate.value

• Discard unchanged with heartbeat: 6h

The total number of flash program operation failures since the drive was deployed.

Preprocessing

• JSON Path: $.program_fail_count_chip.value

• Discard unchanged with heartbeat: 6h

Disk discovered attribute.

Preprocessing

• JSON Path: $.reallocated_sector_ct.value

• Discard unchanged with heartbeat: 6h

Device serial number has changed. Acknowledge to close the problem manually.

• SMART: [{#NAME}]: Average disk temperature is critical

Command line did not parse.

Device open failed, device did not return an IDENTIFY DEVICE structure, or device is in a low-power mode.

Some SMART or other ATA command to the disk failed,
or there was a checksum error in a SMART data structure.

SMART status check returned "DISK FAILING".

We found prefail Attributes <= threshold.

SMART status check returned "DISK OK" but we found that some (usage
or prefail) Attributes have been <= threshold at some time in the past.

The device error log contains records of errors.

The device self-test log contains records of errors. [ATA only]
Failed self-tests outdated by a newer successful extended self-test are ignored.

• Intel SR1630: Power

• Intel SR1630: Baseboard Temp Critical [{ITEM.VALUE}]
• Intel SR1630: Power

• Intel SR1630: Power

• Intel SR1630: BB +1.05V PCH Critical [{ITEM.VALUE}]
• Intel SR1630: Power

• Intel SR1630: Power

• Intel SR1630: BB +1.1V P1 Vccp Critical [{ITEM.VALUE}]
• Intel SR1630: Power

• Intel SR1630: Power

• Intel SR1630: BB +1.5V P1 DDR3 Critical [{ITEM.VALUE}]
• Intel SR1630: Power

• Intel SR1630: Power

• Intel SR1630: BB +3.3V Critical [{ITEM.VALUE}]
• Intel SR1630: Power

• Intel SR1630: BB +3.3V STBY Critical [{ITEM.VALUE}]

• Intel SR1630: Power

• Intel SR1630: BB +5.0V Critical [{ITEM.VALUE}]
• Intel SR1630: Power

• Intel SR1630: Power

• Intel SR1630: Front Panel Temp Critical [{ITEM.VALUE}]
• Intel SR1630: Power

• Intel SR1630: Power

• Intel SR1630: Power
• Intel SR1630: System Fan 2 Critical [{ITEM.VALUE}]

• Intel SR1630: Power

• Intel SR1630: Power
• Intel SR1630: System Fan 3 Critical [{ITEM.VALUE}]

• Intel SR1530: Power

• Intel SR1530: BB +1.8V SM Critical [{ITEM.VALUE}]
• Intel SR1530: Power

• Intel SR1530: Power

• Intel SR1530: BB +3.3V Critical [{ITEM.VALUE}]
• Intel SR1530: Power

• Intel SR1530: BB +3.3V STBY Critical [{ITEM.VALUE}]

• Intel SR1530: Power

• Intel SR1530: BB +5.0V Critical [{ITEM.VALUE}]
• Intel SR1530: Power

• Intel SR1530: BB Ambient Temp Critical [{ITEM.VALUE}]

Time interval for the SNMP availability trigger.

Warning threshold of ICMP packet loss in %.

Warning threshold of the average ICMP response time in seconds.

MIB: IMM-MIB

Indicates status of system health for the system in which the IMM resides. Value of 'nonRecoverable' indicates a severe error has occurred and the system may not be functioning. A value of 'critical' indicates that an error has occurred but the system is currently functioning properly. A value of 'nonCritical' indicates that a condition has occurred that may change the state of the system in the future but currently the system is working properly. A value of 'normal' indicates that the system is operating normally.

MIB: IMM-MIB

Preprocessing

• Discard unchanged with heartbeat: 1d

MIB: IMM-MIB

Machine serial number VPD information

Preprocessing

• Discard unchanged with heartbeat: 1d

MIB: SNMPv2-MIB

Time (in hundredths of a second) since the network management portion of the system was last re-initialized.

Preprocessing

• Custom multiplier: 0.01

MIB: HOST-RESOURCES-MIB

The amount of time since this host was last initialized. Note that this is different from sysUpTime in the SNMPv2-MIB [RFC1907] because sysUpTime is the uptime of the network management portion of the system.

Preprocessing

• Check for not supported value: any error

  ⛔️Custom on fail: Set value to: 0

• Custom multiplier: 0.01

The item is used to collect all SNMP traps unmatched by other snmptrap items

MIB: SNMPv2-MIB

Physical location of the node (e.g., equipment room, 3rd floor). If not provided, the value is a zero-length string.

Preprocessing

• Discard unchanged with heartbeat: 12h

MIB: SNMPv2-MIB

The textual identification of the contact person for this managed node, together with information on how to contact this person. If no contact information is known, the value is the zero-length string.

Preprocessing

• Discard unchanged with heartbeat: 12h

MIB: SNMPv2-MIB

The vendor's authoritative identification of the network management subsystem contained in the entity. This value is allocated within the SMI enterprises subtree (1.3.6.1.4.1) and provides an easy and unambiguous means for determiningwhat kind of box' is being managed. For example, if vendorFlintstones, Inc.' was assigned the subtree1.3.6.1.4.1.4242, it could assign the identifier 1.3.6.1.4.1.4242.1.1 to its `Fred Router'.

Preprocessing

• Discard unchanged with heartbeat: 12h

MIB: SNMPv2-MIB

An administratively-assigned name for this managed node.By convention, this is the node's fully-qualified domain name. If the name is unknown, the value is the zero-length string.

Preprocessing

• Discard unchanged with heartbeat: 12h

MIB: SNMPv2-MIB

A textual description of the entity. This value should

include the full name and version identification of the system's hardware type, software operating-system, and

networking software.

Preprocessing

• Discard unchanged with heartbeat: 12h

Availability of SNMP checks on the host. The value of this item corresponds to availability icons in the host list.

Possible values:

0 - not available

1 - available

2 - unknown

Please check the device for faults

Please check the device for errors

• IBM IMM: System is in unrecoverable state!

Please check the device for warnings

• IBM IMM: System is in unrecoverable state!
• IBM IMM: System status is in critical state

Device serial number has changed. Acknowledge to close the problem manually.

Uptime is less than 10 minutes.

• IBM IMM: No SNMP data collection

The name of the system has changed. Acknowledge to close the problem manually.

SNMP is not available for polling. Please check device connectivity and SNMP settings.

• IBM IMM: Unavailable by ICMP ping

Last three attempts returned timeout. Please check device connectivity.

• IBM IMM: Unavailable by ICMP ping

Average ICMP response time is too high.

• IBM IMM: High ICMP ping loss
• IBM IMM: Unavailable by ICMP ping

Scanning IMM-MIB::tempTable

MIB: IMM-MIB

Temperature readings of testpoint: {#SNMPVALUE}

This trigger uses temperature sensor values as well as temperature sensor status if available

• IBM IMM: {#SNMPVALUE}: Temperature is above critical threshold

This trigger uses temperature sensor values as well as temperature sensor status if available

Scanning IMM-MIB::tempTable with Ambient filter

MIB: IMM-MIB

Temperature readings of testpoint: Ambient

This trigger uses temperature sensor values as well as temperature sensor status if available

• IBM IMM: Ambient: Temperature is above critical threshold

This trigger uses temperature sensor values as well as temperature sensor status if available

Scanning IMM-MIB::tempTable with CPU filter

MIB: IMM-MIB

Temperature readings of testpoint: CPU

This trigger uses temperature sensor values as well as temperature sensor status if available

• IBM IMM: CPU: Temperature is above critical threshold

This trigger uses temperature sensor values as well as temperature sensor status if available

IMM-MIB::powerFruName

MIB: IMM-MIB

A description of the power module status.

Please check the power supply unit for errors

IMM-MIB::fanDescr

MIB: IMM-MIB

A description of the fan component status.

MIB: IMM-MIB

Fan speed expressed in percent(%) of maximum RPM.

An octet string expressed as 'ddd% of maximum' where:d is a decimal digit or blank space for a leading zero.

If the fan is determined not to be running or the fan speed cannot be determined, the string will indicate 'Offline'.

Preprocessing

• Regular expression: (\d{1,3}) *%( of maximum)? \1

Please check the fan unit

MIB: IMM-MIB

MIB: IMM-MIB

disk module FRU name.

Please check physical disk for warnings or errors

Specify password for API.

Specify user name for API.

Response timeout for API.

The API scheme (http/https).

The hostname or IP address of the API host.

The API port.

The JSON with the result from requests to API.

A list of errors from API requests.

Preprocessing

• JSON Path: $.errors

• Discard unchanged with heartbeat: 1h

A list of enclosures.

Preprocessing

• JSON Path: $.enclosures

  ⛔️Custom on fail: Discard value

Data of the datacenters.

Preprocessing

• JSON Path: $.datacenters

  ⛔️Custom on fail: Discard value

Data of the ethernet networks.

Preprocessing

• JSON Path: $.["ethernet-networks"]

  ⛔️Custom on fail: Discard value

Data of the fabrics.

Preprocessing

• JSON Path: $.fabrics

  ⛔️Custom on fail: Discard value

Data of the FC networks.

Preprocessing

• JSON Path: $.["fc-networks"]

  ⛔️Custom on fail: Discard value

Data of the hypervisor managers.

Preprocessing

• JSON Path: $.["hypervisor-managers"]

  ⛔️Custom on fail: Discard value

Data of the interconnects.

Preprocessing

• JSON Path: $.interconnects

  ⛔️Custom on fail: Discard value

Data of the logical enclosures.

Preprocessing

• JSON Path: $.["logical-enclosures"]

  ⛔️Custom on fail: Discard value

Data of the racks.

Preprocessing

• JSON Path: $.racks

  ⛔️Custom on fail: Discard value

Data of the server hardware.

Preprocessing

• JSON Path: $.["server-hardware"]

  ⛔️Custom on fail: Discard value

Data of the storage pools.

Preprocessing

• JSON Path: $.["storage-pools"]

  ⛔️Custom on fail: Discard value

Data of the storage systems.

Preprocessing

• JSON Path: $.["storage-systems"]

  ⛔️Custom on fail: Discard value

Data of the storage volumes.

Preprocessing

• JSON Path: $.["storage-volumes"]

  ⛔️Custom on fail: Discard value

Data of the uplink sets.

Preprocessing

• JSON Path: $.["uplink-sets"]

  ⛔️Custom on fail: Discard value

Checks if the service is running and accepting the TCP connections.

Preprocessing

• Discard unchanged with heartbeat: 10m

Zabbix has received errors from API.

• HPE Synergy: Service is unavailable

A list of the appliance bays in the enclosure.

Preprocessing

• JSON Path: $.members.[0].applianceBays

• Discard unchanged with heartbeat: 6h

Data of the appliance bay [{#ENCLOSURENAME}:{#BAYNUMBER}].

Preprocessing

• JSON Path: The text is too long. Please see the template.

The model name of the appliance.

Preprocessing

• JSON Path: $.model

• Discard unchanged with heartbeat: 1d

The part number of the appliance.

Preprocessing

• JSON Path: $.partNumber

• Discard unchanged with heartbeat: 1d

Yes, if the appliance is powered on; false, otherwise.

Preprocessing

• JSON Path: $.poweredOn

• Boolean to decimal

• Discard unchanged with heartbeat: 1h

The power state of the appliance bay.

EFuse - the power state of the bay - it has been EFused.

Reset - the power state of the bay - it has been reset.

SoftReset - the power state of the bay - it has been softly reset.

Unknown - the power state of the bay is unknown.

Preprocessing

• JSON Path: $.bayPowerState

• Replace: EFuse -> 0

• Replace: SoftReset -> 1

• Replace: Reset -> 2

• Replace: Unknown -> 3

• In range: 0 -> 3

  ⛔️Custom on fail: Set value to: 3

Indicates whether an appliance is present in the bay:

Absent - the device slot is empty;

PresenceNoOp - the device slot is uninitialized;

PresenceUnknown - the device presence is unknown;

Present - the device slot has a device in it;

Subsumed - the device slot is configured to be part of another device slot. Not applicable for the fan or power supply bays.

Preprocessing

• JSON Path: $.devicePresence

• Replace: Absent -> 0

• Replace: PresenceNoOp -> 1

• Replace: PresenceUnknown -> 2

• Replace: Present -> 3

• Replace: Subsumed -> 4

• In range: 0 -> 4

  ⛔️Custom on fail: Set value to: 2

• Discard unchanged with heartbeat: 1h

The serial number of the appliance.

Preprocessing

• JSON Path: $.serialNumber

• Discard unchanged with heartbeat: 1d

The spare part number of the appliance.

Preprocessing

• JSON Path: $.sparePartNumber

• Discard unchanged with heartbeat: 1d

The hardware status of the appliance:

Critical - requires immediate attention;

Disabled - the resource is currently not operational;

OK - indicates normal/informational behavior;

Unknown - the health status is not yet known or cannot be determined;

Warning - requires attention soon.

Preprocessing

• JSON Path: $.status

• Discard unchanged with heartbeat: 10m

• Replace: Critical -> 0

• Replace: Disabled -> 1

• Replace: OK -> 2

• Replace: Unknown -> 3

• Replace: Warning -> 4

• In range: 0 -> 4

  ⛔️Custom on fail: Set value to: 3

The appliance [{#ENCLOSURENAME}:{#BAYNUMBER}] status is critical. Needs immediate attention.

The appliance [{#ENCLOSURENAME}:{#BAYNUMBER}] status is warning. Needs attention soon.

The appliance [{#ENCLOSURENAME}:{#BAYNUMBER}] is currently not operational

SDX cross fabric module connects to all computing devices installed in the system enclosure and brings in the capability of hard partitioning. Crossbar details are relevant only for enclosures with type "SDX".

Preprocessing

• JSON Path: $.members.[0].crossBars

• Discard unchanged with heartbeat: 6h

Crossbar [{#ENCLOSURENAME}:{#BAYNUMBER}] data

Preprocessing

• JSON Path: The text is too long. Please see the template.

The hardware version.

Preprocessing

• JSON Path: $.hwVersion

• Discard unchanged with heartbeat: 1d

The part number provided by the manufacturer.

Preprocessing

• JSON Path: $.partNumber

• Discard unchanged with heartbeat: 1d

The presence in a bay:

Absent - the device slot is empty;

PresenceNoOp - the device slot is uninitialized;

PresenceUnknown - the device presence is unknown;

Present - the device slot has a device in it;

Subsumed - the device slot is configured to be part of another device slot. Not applicable for the fan or power supply bays.

Preprocessing

• JSON Path: $.presence

• Replace: Absent -> 0

• Replace: PresenceNoOp -> 1

• Replace: PresenceUnknown -> 2

• Replace: Present -> 3

• Replace: Subsumed -> 4

• In range: 0 -> 4

  ⛔️Custom on fail: Set value to: 2

• Discard unchanged with heartbeat: 1h

A serial number.

Preprocessing

• JSON Path: $.serialNumber

• Discard unchanged with heartbeat: 1d

The overall health status of the crossbar:

Critical - requires immediate attention;

Disabled - the resource is currently not operational;

OK - indicates normal/informational behavior;

Unknown - the health status is not yet known or cannot be determined;

Warning - requires attention soon.

Preprocessing

• JSON Path: $.status

• Discard unchanged with heartbeat: 10m

• Replace: Critical -> 0

• Replace: Disabled -> 1

• Replace: OK -> 2

• Replace: Unknown -> 3

• Replace: Warning -> 4

• In range: 0 -> 4

  ⛔️Custom on fail: Set value to: 3

The device slot is configured to be part of another device slot.

The crossbar [{#ENCLOSURENAME}:{#BAYNUMBER}] status is critical. Needs immediate attention.

The crossbar [{#ENCLOSURENAME}:{#BAYNUMBER}] status is warning. Needs attention soon.

The crossbar [{#ENCLOSURENAME}:{#BAYNUMBER}] currently not operational.

A list of the datacenters.

Preprocessing

• JSON Path: $.members

• Discard unchanged with heartbeat: 6h

Data of the datacenter [{#NAME}].

Preprocessing

• JSON Path: $.members[?(@.name == "{#NAME}")].first()

The current state of the resource. The valid values include Adding, AddError, Configured, CredentialError, Refreshing, RefreshError, Removing, RemoveError, and Unmanaged.

Preprocessing

• JSON Path: $.state

• Replace: Adding -> 0

• Replace: AddError -> 1

• Replace: Configured -> 2

• Replace: CredentialError -> 3

• Replace: Refreshing -> 4

• Replace: RefreshError -> 5

• Replace: Removing -> 6

• Replace: RemoveError -> 7

• Replace: Unmanaged -> 8

• In range: 0 -> 8

  ⛔️Custom on fail: Set value to: 9

The overall health status of the resource. The following are the valid values for the status of the resource:

OK - indicates normal/informational behavior;

Disabled - indicates that a resource is not operational;

Warning - requires attention soon;

Critical - requires immediate attention;

Unknown - should be avoided, but there may be rare occasions when the status is unknown.

Preprocessing

• JSON Path: $.status

• Discard unchanged with heartbeat: 10m

• Replace: Critical -> 0

• Replace: Disabled -> 1

• Replace: OK -> 2

• Replace: Unknown -> 3

• Replace: Warning -> 4

• In range: 0 -> 4

  ⛔️Custom on fail: Set value to: 3

The adding of the datacenter [{#NAME}] has failed.

The datacenter [{#NAME}] has a credential error.

The datacenter [{#NAME}] has a refresh error.

The datacenter [{#NAME}] has a remove error.

The datacenter [{#NAME}] status is critical. Needs immediate attention.

The datacenter [{#NAME}] status is warning. Needs attention soon.

the datacenter [{#NAME}] currently not operational.

A list of device bays in the enclosure.

Preprocessing

• JSON Path: $.members.[0].deviceBays

• Discard unchanged with heartbeat: 6h

Data of the device [{#ENCLOSURENAME}:{#BAYNUMBER}].

Preprocessing

• JSON Path: The text is too long. Please see the template.

The model name of an unsupported device occupying the bay if available.

Preprocessing

• JSON Path: $.model

• Discard unchanged with heartbeat: 1d

The power allocated for the enclosed blade.

Preprocessing

• JSON Path: $.powerAllocationWatts

• Discard unchanged with heartbeat: 1h

Indicates whether a device is present:

Absent - the device slot is empty;

PresenceNoOp - the device slot is uninitialized;

PresenceUnknown - the device presence is unknown;

Present - the device slot has a device in it;

Subsumed - the device slot is configured to be part of another device slot. Not applicable for the fan or power supply bays.

Preprocessing

• JSON Path: $.devicePresence

• Replace: Absent -> 0

• Replace: PresenceNoOp -> 1

• Replace: PresenceUnknown -> 2

• Replace: Present -> 3

• Replace: Subsumed -> 4

• In range: 0 -> 4

  ⛔️Custom on fail: Set value to: 2

• Discard unchanged with heartbeat: 1h

If available, the serial number of any device occupying the bay.

Preprocessing

• JSON Path: $.serialNumber

  ⛔️Custom on fail: Discard value

• Discard unchanged with heartbeat: 1d

The device slot is configured to be part of another device slot.

A list of enclosures resources.

Preprocessing

• JSON Path: $.members

• Discard unchanged with heartbeat: 6h

Data of the enclosure [{#NAME}].

Preprocessing

• JSON Path: $.members[?(@.name == "{#NAME}")].first()

The number of the appliance bays in the enclosure.

Preprocessing

• JSON Path: $.applianceBayCount

• Discard unchanged with heartbeat: 1h

The number of the device bays in the enclosure.

Preprocessing

• JSON Path: $.deviceBayCount

• Discard unchanged with heartbeat: 1h

The amount of power allocated for the blades in the enclosure.

Preprocessing

• JSON Path: $.deviceBayWatts

The number of the fan bays in the enclosure.

Preprocessing

• JSON Path: $.fanBayCount

• Discard unchanged with heartbeat: 1h

The name of the current firmware baseline.

Preprocessing

• JSON Path: $.fwBaselineName

• Discard unchanged with heartbeat: 1d

The number of the interconnect bays in the enclosure.

Preprocessing

• JSON Path: $.interconnectBayCount

• Discard unchanged with heartbeat: 1h

The amount of power allocated for the interconnects in the enclosure.

Preprocessing

• JSON Path: $.interconnectBayWatts

The minimum number of the power supplies needed.

Preprocessing

• JSON Path: $.minimumPowerSupplies

• Discard unchanged with heartbeat: 1d

The minimum number of the power supplies needed to fulfill the redundant line feed power mode.

Preprocessing

• JSON Path: $.minimumPowerSuppliesForRedundantPowerFeed

• Discard unchanged with heartbeat: 1d

The enclosure model name, for example, "BladeSystem c7000 Enclosure G2.

Preprocessing

• JSON Path: $.enclosureModel

• Discard unchanged with heartbeat: 1d

The part number of the enclosure.

Preprocessing

• JSON Path: $.partNumber

• Discard unchanged with heartbeat: 1d

The amount of the power allocated for the fans and management devices of the enclosure.

Preprocessing

• JSON Path: $.fansAndManagementDevicesWatts

The power capacity based on power mode.

Preprocessing

• JSON Path: $.powerCapacityWatts

The number of the power supply bays in the enclosure.

Preprocessing

• JSON Path: $.powerSupplyBayCount

• Discard unchanged with heartbeat: 1h

The serial number of the enclosure.

Preprocessing

• JSON Path: $.serialNumber

• Discard unchanged with heartbeat: 1d

The current resource state of the enclosure:

Adding - the enclosure is being added;

Configured - the enclosure is configured and is a part of the logical enclosure. This is the usual state for an enclosure under full management;

Configuring - a transient state while the enclosure is being configured for a logical enclosure;

Interrupted - the previous operation on the enclosure did not complete. The operation should be re-attempted;

Monitored - the enclosure is being monitored. It is not a part of the logical enclosure and only hardware-control operations are available;

Pending - there are pending operations on the enclosure. Additional operations are denied;

RemoveFailed - the previous operation to remove the enclosure did not succeed. The operation should be re-attempted;

Removing - the enclosure is being removed;

Unmanaged - the enclosure has been discovered, but has not yet been added for the management or monitoring;

Unsupported - the enclosure model or version is not currently supported by HPE OneView. It cannot be configured or monitored.

Preprocessing

• JSON Path: $.state

• Replace: Adding -> 0

• Replace: Configured -> 1

• Replace: Configuring -> 2

• Replace: Interrupted -> 3

• Replace: Monitored -> 4

• Replace: Pending -> 5

• Replace: RemoveFailed -> 6

• Replace: Removing -> 7

• Replace: Unmanaged -> 8

• Replace: Unsupported -> 9

• In range: 0 -> 9

  ⛔️Custom on fail: Set value to: 10

Indicates the reason why the resource in its current state:

Missing - the enclosure is no longer connected into the frame link topology;

None - no reason is available, or none applies;

NotAdded - the enclosure has not been added;

NotOwner - the enclosure reports being managed by something other than this HPE OneView;

OperationFailed - a prior operation was interrupted;

Unowned - the enclosure reports are not being under the management;

UnsupportedFirmware - the firmware version of the enclosure is not supported by this version of HPE OneView;

UpdatingFirmware - a firmware update is in progress.

Preprocessing

• JSON Path: $.stateReason

• Replace: Missing -> 0

• Replace: None -> 1

• Replace: NotAdded -> 2

• Replace: NotOwner -> 3

• Replace: OperationFailed -> 4

• Replace: Unowned -> 5

• Replace: UnsupportedFirmware -> 6

• Replace: UpdatingFirmware -> 7

• In range: 0 -> 7

  ⛔️Custom on fail: Set value to: 8

The overall health status of the enclosure.

The enclosure status reflects the hardware health of the enclosure, all the bays, and the enclosure components (e.g. the enclosure mid-plane, fans, power supplies, Synergy Frame Link Modules, and Synergy Composers). It explicitly does not include the status of the other HPE OneView resources such as the blades (server hardware), the interconnects, and the drive enclosures.

Critical - requires immediate attention.

Disabled - the resource is currently not operational.

OK - indicates normal/informational behavior.

Unknown - the health status is not yet known or cannot be determined.

Warning - requires attention soon.

Preprocessing

• JSON Path: $.status

• Discard unchanged with heartbeat: 10m

• Replace: Critical -> 0

• Replace: Disabled -> 1

• Replace: OK -> 2

• Replace: Unknown -> 3

• Replace: Warning -> 4

• In range: 0 -> 4

  ⛔️Custom on fail: Set value to: 3

The total amount of the power allocated in the enclosure.

Preprocessing

• JSON Path: $.powerAllocatedWatts

The amount of the unallocated power in the enclosure.

Preprocessing

• JSON Path: $.powerAvailableWatts

The type of the enclosure, for example, "C7000" or "SY12000" or "SDX".

Preprocessing

• JSON Path: $.enclosureType

• Discard unchanged with heartbeat: 6h

The previous operation on the enclosure did not complete. The operation should be re-attempted.

The enclosure model or version is not currently supported by HPE OneView. It cannot be configured or monitored.

The previous operation to remove the enclosure did not succeed. The operation should be re-attempted.

The enclosure is no longer connected into the frame link topology.

The enclosure reports are not being under the management.

The status of the enclosure [{#NAME}] is critical. Needs immediate attention.

The status of the enclosure [{#NAME}] is warning. Needs attention soon.

The enclosure [{#NAME}] is currently not operational.

A list of the ethernet networks.

Preprocessing

• JSON Path: $.members

• Discard unchanged with heartbeat: 6h

Data of the ethernet network [{#NAME}].

Preprocessing

• JSON Path: $.members[?(@.name == "{#NAME}")].first()

The current state of the resource.

Preprocessing

• JSON Path: $.state

• Discard unchanged with heartbeat: 1h

The overall health status of the resource. The following are the valid values for the status of the resource:

OK - indicates normal/informational behavior;

Disabled - indicates that the resource is not operational;

Warning - requires attention soon;

Critical - requires immediate attention;

Unknown - should be avoided, but there may be rare occasions when the status is unknown.

Preprocessing

• JSON Path: $.status

• Discard unchanged with heartbeat: 10m

• Replace: Critical -> 0

• Replace: Disabled -> 1

• Replace: OK -> 2

• Replace: Unknown -> 3

• Replace: Warning -> 4

• In range: 0 -> 4

  ⛔️Custom on fail: Set value to: 3

The ethernet network [{#NAME}] status is critical. Needs immediate attention.

The ethernet network [{#NAME}] status is warning. Needs attention soon.

The ethernet network [{#NAME}] is currently not operational.

A list of the fabrics.

Preprocessing

• JSON Path: $.members

• Discard unchanged with heartbeat: 6h

Data of the fabric [{#NAME}].

Preprocessing

• JSON Path: $.members[?(@.name == "{#NAME}")].first()

The current state of the resource.

Preprocessing

• JSON Path: $.state

• Discard unchanged with heartbeat: 1h

The overall health status of the resource. The following are the valid values for the status of the resource:

OK - indicates normal/informational behavior;

Disabled - indicates that the resource is not operational;

Warning - requires attention soon;

Critical - requires immediate attention;

Unknown - should be avoided, but there may be rare occasions when the status is unknown.

Preprocessing

• JSON Path: $.status

• Discard unchanged with heartbeat: 10m

• Replace: Critical -> 0

• Replace: Disabled -> 1

• Replace: OK -> 2

• Replace: Unknown -> 3

• Replace: Warning -> 4

• In range: 0 -> 4

  ⛔️Custom on fail: Set value to: 3

The status of the fabric [{#NAME}] is critical. Needs immediate attention.

The status of the fabric [{#NAME}] is warning. Needs attention soon.

The status of the fabric [{#NAME}] is currently not operational.

A list of the fan bays in the enclosure.

Preprocessing

• JSON Path: $.members.[0].fanBays

• Discard unchanged with heartbeat: 6h

Data of the fan [{#ENCLOSURENAME}:{#BAYNUMBER}].

Preprocessing

• JSON Path: The text is too long. Please see the template.

The common descriptive model of the fan.

Preprocessing

• JSON Path: $.model

• Discard unchanged with heartbeat: 1d

The part number of the fan.

Preprocessing

• JSON Path: $.partNumber

• Discard unchanged with heartbeat: 1d

Indicates whether a fan is present:

Absent - the device slot is empty;

PresenceNoOp - the device slot is uninitialized;

PresenceUnknown - the device presence is unknown;

Present - the device slot has a device in it;

Subsumed - the device slot is configured to be part of another device slot. Not applicable for the fan or power supply bays.

Preprocessing

• JSON Path: $.devicePresence

• Replace: Absent -> 0

• Replace: PresenceNoOp -> 1

• Replace: PresenceUnknown -> 2

• Replace: Present -> 3

• Replace: Subsumed -> 4

• In range: 0 -> 4

  ⛔️Custom on fail: Set value to: 2

• Discard unchanged with heartbeat: 1h

Indicates whether the enclosure configuration requires a fan to be present in the bay.

Preprocessing

• JSON Path: $.deviceRequired

• Boolean to decimal

• Discard unchanged with heartbeat: 1h

The serial number of the fan.

Preprocessing

• JSON Path: $.serialNumber

• Discard unchanged with heartbeat: 1d

The spare part number to be used when ordering an additional or replacement fan of this type.

Preprocessing

• JSON Path: $.sparePartNumber

• Discard unchanged with heartbeat: 1d

The current state of the fan:

Degraded - a fan is degraded;

Failed - a fan has failed;

Misplaced - a fan is present, but not required in this bay, and the overall fan configuration is not compliant with the enclosure fan placement rules;

Missing - a fan is required, but is not present;

OK - a fan bay has no issues;

Unknown - the state of a fan is unknown.

Preprocessing

• JSON Path: $.state

  ⛔️Custom on fail: Set value to: 5

• Replace: Degraded -> 0

• Replace: Failed -> 1

• Replace: Misplaced -> 2

• Replace: Missing -> 3

• Replace: OK -> 4

• In range: 0 -> 4

  ⛔️Custom on fail: Set value to: 5

The overall health status of the fan:

Critical - requires immediate attention;

Disabled - the resource is currently not operational;

OK - indicates normal/informational behavior;

Unknown - the health status is not yet known or cannot be determined;

Warning - requires attention soon.

Preprocessing

• JSON Path: $.status

• Discard unchanged with heartbeat: 10m

• Replace: Critical -> 0

• Replace: Disabled -> 1

• Replace: OK -> 2

• Replace: Unknown -> 3

• Replace: Warning -> 4

• In range: 0 -> 4

  ⛔️Custom on fail: Set value to: 3

The fan [{#ENCLOSURENAME}:{#BAYNUMBER}] is in degraded state.

The fan [{#ENCLOSURENAME}:{#BAYNUMBER}] is in failed state.

The fan [{#ENCLOSURENAME}:{#BAYNUMBER}] is misplaced.

The fan [{#ENCLOSURENAME}:{#BAYNUMBER}] is missing.

The fan [{#ENCLOSURENAME}:{#BAYNUMBER}] status is critical. Needs immediate attention.

The fan [{#ENCLOSURENAME}:{#BAYNUMBER}] status is warning. Needs attention soon.

The fan [{#ENCLOSURENAME}:{#BAYNUMBER}] is currently not operational.

A list of the FC networks.

Preprocessing

• JSON Path: $.members

• Discard unchanged with heartbeat: 6h

Data of the FC network [{#NAME}].

Preprocessing

• JSON Path: $.members[?(@.name == "{#NAME}")].first()

The current state of the resource.

Preprocessing

• JSON Path: $.state

• Discard unchanged with heartbeat: 1h

The overall health status of the resource. The following are the valid values for the status of the resource:

OK - indicates normal/informational behavior;

Disabled - indicates that the resource is not operational;

Warning - requires attention soon;

Critical - requires immediate attention;

Unknown - should be avoided, but there may be rare occasions when the status is unknown.

Preprocessing

• JSON Path: $.status

• Discard unchanged with heartbeat: 10m

• Replace: Critical -> 0

• Replace: Disabled -> 1

• Replace: OK -> 2

• Replace: Unknown -> 3

• Replace: Warning -> 4

• In range: 0 -> 4

  ⛔️Custom on fail: Set value to: 3

The FC network [{#NAME}] status is critical. Needs immediate attention.

The FC network [{#NAME}] status is warning. Needs attention soon.

The FC network [{#NAME}] is currently not operational.

A list of the hypervisor managers.

Preprocessing

• JSON Path: $.members

• Discard unchanged with heartbeat: 6h

Data of the hypervisor manager [{#NAME}].

Preprocessing

• JSON Path: $.members[?(@.displayName == "{#NAME}")].first()

The current state of the resource. The valid values include Connected, Disconnected, Configuring and Error.

Preprocessing

• JSON Path: $.state

• Replace: Connected -> 0

• Replace: Disconnected -> 1

• Replace: Configuring -> 2

• Replace: Error -> 3

• In range: 0 -> 3

  ⛔️Custom on fail: Set value to: 4

Indicates the reason why the resource is in its current state.

Preprocessing

• JSON Path: $.stateReason

• Discard unchanged with heartbeat: 1h

The current status of this resource:

Critical - requires immediate attention;

Disabled - the resource is currently not operational;

OK - indicates normal/informational behavior;

Unknown - the health status is not yet known or cannot be determined;

Warning - requires attention soon.

Preprocessing

• JSON Path: $.status

• Discard unchanged with heartbeat: 10m

• Replace: Critical -> 0

• Replace: Disabled -> 1

• Replace: OK -> 2

• Replace: Unknown -> 3

• Replace: Warning -> 4

• In range: 0 -> 4

  ⛔️Custom on fail: Set value to: 3

The hypervisor manager [{#NAME}] has an error.

The hypervisor manager [{#NAME}] status is critical. Needs immediate attention.

The hypervisor manager [{#NAME}] status is warning. Needs attention soon.

The hypervisor manager [{#NAME}] is currently not operational.

Interconnects are centrally managed by their containing logical interconnect. The interconnect provides a physical view of a detailed downlink and uplink port state and configuration, including the current link state, speed, port role (uplink, downlink, or stacking), current pluggable media, power state, and immediate connected neighbor.

Preprocessing

• JSON Path: $.members

• Discard unchanged with heartbeat: 6h

Data of the interconnect [{#NAME}].

Preprocessing

• JSON Path: $.members[?(@.name == "{#NAME}")].first()

The health status of the interconnect hardware.

Preprocessing

• JSON Path: $.interconnectHardwareHealth

• Discard unchanged with heartbeat: 1h

The interconnect model.

Preprocessing

• JSON Path: $.model

• Discard unchanged with heartbeat: 1d

The part number of the interconnect.

Preprocessing

• JSON Path: $.partNumber

• Discard unchanged with heartbeat: 1d

The number of ports on the interconnect.

Preprocessing

• JSON Path: $.portCount

• Discard unchanged with heartbeat: 1h

The serial number of the interconnect.

Preprocessing

• JSON Path: $.serialNumber

• Discard unchanged with heartbeat: 1d

The spare part number of the interconnect.

Preprocessing

• JSON Path: $.sparePartNumber

• Discard unchanged with heartbeat: 1d

The current state of the resource.

Preprocessing

• JSON Path: $.state

• Discard unchanged with heartbeat: 1h

The overall health status of the resource. The following are the valid values for the status of the resource:

OK - indicates normal/informational behavior;

Disabled - indicates that the resource is not operational;

Warning - requires attention soon;

Critical - requires immediate attention;

Unknown - should be avoided, but there may be rare occasions when the status is unknown.

Preprocessing

• JSON Path: $.status

• Discard unchanged with heartbeat: 10m

• Replace: Critical -> 0

• Replace: Disabled -> 1

• Replace: OK -> 2

• Replace: Unknown -> 3

• Replace: Warning -> 4

• In range: 0 -> 4

  ⛔️Custom on fail: Set value to: 3

The interconnect [{#NAME}] status is critical. Needs immediate attention.

The interconnect [{#NAME}] status is warning. Needs attention soon.

The interconnect [{#NAME}] is currently not operational.

A list of the logical enclosures.

Preprocessing

• JSON Path: $.members

• Discard unchanged with heartbeat: 6h

Data of the logical enclosure [{#NAME}].

Preprocessing

• JSON Path: $.members[?(@.name == "{#NAME}")].first()

The current resource state of the logical enclosure:

Consistent - this is the expected state of the logical enclosure. The logical enclosure configuration is consistent with the enclosure group, and the configuration of the hardware resources is consistent with the logical enclosure configuration;

Creating - the logical enclosure is being created;

DeleteFailed - the prior attempt to delete the logical enclosure failed. Retry the delete operation potentially with the force option. No other logical enclosure operations are allowed in this state;

Deleting - the logical enclosure is being deleted;

Inconsistent - the configuration of the logical enclosure differs from that of the enclosure group, or the configuration of the hardware resources is inconsistent with the logical enclosure configuration. Perform an Update from group, Reapply configuration, or Update firmware action as an appropriate to bring the configuration back into consistency;

Updating - configuration changes are being applied to the hardware configuration.

Preprocessing

• JSON Path: $.state

• Replace: Inconsistent -> 0

• Replace: Creating -> 1

• Replace: DeleteFailed -> 2

• Replace: Deleting -> 3

• Replace: Consistent -> 4

• Replace: Updating -> 5

• In range: 0 -> 5

  ⛔️Custom on fail: Set value to: 6

The overall health status of the resource. The following are the valid values for the status of the resource:

OK - indicates normal/informational behavior;

Disabled - indicates that the resource is not operational;

Warning - requires attention soon;

Critical - requires immediate attention;

Unknown - should be avoided, but there may be rare occasions when the status is unknown.

Preprocessing

• JSON Path: $.status

• Discard unchanged with heartbeat: 10m

• Replace: Critical -> 0

• Replace: Disabled -> 1

• Replace: OK -> 2

• Replace: Unknown -> 3

• Replace: Warning -> 4

• In range: 0 -> 4

  ⛔️Custom on fail: Set value to: 3

Indicator that the deletion of a logical enclosure failed.

The configuration of the logical enclosure differs from that of the enclosure group, or the configuration of the hardware resources is inconsistent with the logical enclosure configuration. Perform an Update from group, Reapply configuration, or Update firmware action as an appropriate to bring the configuration back into consistency.

The status of the logical enclosure [{#NAME}] is critical. Needs immediate attention.

The status of the logical enclosure [{#NAME}] is warning. Needs attention soon.

The logical enclosure [{#NAME}] is currently not operational.

Electrically isolated hardware partition (nPar). Partition details are relevant only for enclosures with type "SDX".

Preprocessing

• JSON Path: $.members.[0].partitions

• Discard unchanged with heartbeat: 6h

Data of the partition [{#ENCLOSURENAME}:{#PARTITIONID}].

Preprocessing

• JSON Path: The text is too long. Please see the template.

The number of blades in the partition.

Preprocessing

• JSON Path: $.deviceCount

• Discard unchanged with heartbeat: 10m

Indicates the health of the partition and the health of its owned resources (blades and IO bays) as reported by the firmware. If a problem is detected with one of the resources, the health of the partition is reported as Degraded. If all the resources in the partition are operating correctly, the health of the partition is reported as OK.

NparDegrade - one or more resources in the partition are unhealthy.

NparHealthInvalid - a partition health is invalid.

NparHealthMax - a delimiter defined by the firmware.

NparOk - all the resources in the partition are healthy.

Preprocessing

• JSON Path: $.partitionHealth

• Replace: NparDegrade -> 0

• Replace: NparHealthInvalid -> 1

• Replace: NparHealthMax -> 2

• Replace: NparOk -> 3

• In range: 0 -> 3

  ⛔️Custom on fail: Set value to: 4

The total memory of the partition.

Preprocessing

• JSON Path: $.memoryMb

• Custom multiplier: 1048576

• Discard unchanged with heartbeat: 1h

The number of processors in the partition.

Preprocessing

• JSON Path: $.processorCount

• Discard unchanged with heartbeat: 10m

Indicates whether the partition has been booted and also indicates its current power state:

ParStatusActive - a partition is active when a 'poweron' operation is initiated on the partition and the firmware boot process is started;

ParStatusInactive - a partition is in an inactive state after it has been created or shut down;

ParStatusInvalid - a partition status is invalid;

ParStatusManualRepair - a partition under manual repair;

ParStatusMax - a delimiter defined by the OA firmware;

ParStatusUndefined - partition status is undefined;

ParStatusUnknown - a partition might report an Unknown state after an OA restart. This state is possible when the firmware is not able to identify the correct partition state due to the internal firmware errors at an OA startup. The state is persistent and can only be cleared by force powering off of the partition from the OA. A partition in this state will not accept any partition operation except parstatus and force poweroff. Any active OS instances continue to run unhindered even when the partition is in an unknown state.

Preprocessing

• JSON Path: $.partitionStatus

• Discard unchanged with heartbeat: 10m

• Replace: ParStatusActive -> 0

• Replace: ParStatusInactive -> 1

• Replace: ParStatusInvalid -> 2

• Replace: ParStatusManualRepair -> 3

• Replace: ParStatusMax -> 4

• Replace: ParStatusUndefined -> 5

• Replace: ParStatusUnknown -> 6

• In range: 0 -> 6

  ⛔️Custom on fail: Set value to: 6

The partition health is invalid.

One or more resources in the partition are unhealthy.

The partition status is invalid.

List of power supply bays in the enclosure.

Preprocessing

• JSON Path: $.members.[0].powerSupplyBays

• Discard unchanged with heartbeat: 6h

Data of the power Supply [{#ENCLOSURENAME}:{#BAYNUMBER}].

Preprocessing

• JSON Path: The text is too long. Please see the template.

The common descriptive model of the power supply.

Preprocessing

• JSON Path: $.model

• Discard unchanged with heartbeat: 1d

The output capacity of the power supply.

Preprocessing

• JSON Path: $.outputCapacityWatts

• Discard unchanged with heartbeat: 1h

The part number of the power supply.

Preprocessing

• JSON Path: $.partNumber

• Discard unchanged with heartbeat: 1d

Indicates whether a power supply is present:

Absent - the device slot is empty;

PresenceNoOp - the device slot is uninitialized;

PresenceUnknown - the device presence is unknown;

Present - the device slot has a device in it;

Subsumed - the device slot is configured to be part of another device slot. Not applicable for the fan or power supply bays.

Preprocessing

• JSON Path: $.devicePresence

• Replace: Absent -> 0

• Replace: PresenceNoOp -> 1

• Replace: PresenceUnknown -> 2

• Replace: Present -> 3

• Replace: Subsumed -> 4

• In range: 0 -> 4

  ⛔️Custom on fail: Set value to: 2

• Discard unchanged with heartbeat: 1h

The unique serial number of the power supply.

Preprocessing

• JSON Path: $.serialNumber

• Discard unchanged with heartbeat: 1d

The spare part number to be used when ordering an additional or replacement power supply of this type.

Preprocessing

• JSON Path: $.sparePartNumber

• Discard unchanged with heartbeat: 1d

The overall health status of the resource. The following are the valid values for the status of the resource:

OK - indicates normal/informational behavior;

Disabled - indicates that the resource is not operational;

Warning - requires attention soon;

Critical - requires immediate attention;

Unknown - should be avoided, but there may be rare occasions when the status is unknown.

Preprocessing

• JSON Path: $.status

• Discard unchanged with heartbeat: 10m

• Replace: Critical -> 0

• Replace: Disabled -> 1

• Replace: OK -> 2

• Replace: Unknown -> 3

• Replace: Warning -> 4

• In range: 0 -> 4

  ⛔️Custom on fail: Set value to: 3

The status of the power supply [{#ENCLOSURENAME}:{#BAYNUMBER}] is critical. Needs immediate attention.

The status of the power supply [{#ENCLOSURENAME}:{#BAYNUMBER}] is warning. Needs attention soon.

The status of Power Supply [{#ENCLOSURENAME}:{#BAYNUMBER}] is currently not operational.

A list of the racks.

Preprocessing

• JSON Path: $.members

• Discard unchanged with heartbeat: 6h

Data of the rack [{#NAME}].

Preprocessing

• JSON Path: $.members[?(@.name == "{#NAME}")].first()

The current state of the resource. the valid values include Adding, AddError, Configured, CredentialError, Refreshing, RefreshError, Removing, RemoveError, and Unmanaged.

Preprocessing

• JSON Path: $.state

• Replace: Adding -> 0

• Replace: AddError -> 1

• Replace: Configured -> 2

• Replace: CredentialError -> 3

• Replace: Refreshing -> 4

• Replace: RefreshError -> 5

• Replace: Removing -> 6

• Replace: RemoveError -> 7

• Replace: Unmanaged -> 8

• In range: 0 -> 8

  ⛔️Custom on fail: Set value to: 9

The overall health status of the resource. The following are the valid values for the status of the resource:

OK - indicates normal/informational behavior;

Disabled - indicates that the resource is not operational;

Warning - requires attention soon;

Critical - requires immediate attention;

Unknown - should be avoided, but there may be rare occasions when the status is unknown.

Preprocessing

• JSON Path: $.status

• Discard unchanged with heartbeat: 10m

• Replace: Critical -> 0

• Replace: Disabled -> 1

• Replace: OK -> 2

• Replace: Unknown -> 3

• Replace: Warning -> 4

• In range: 0 -> 4

  ⛔️Custom on fail: Set value to: 3

Adding the rack [{#NAME}] failed.

The rack [{#NAME}] has credential error.

The rack [{#NAME}] has refresh error.

The rack [{#NAME}] has remove error.

The rack [{#NAME}] status is critical. Needs immediate attention.

The rack [{#NAME}] status is warning. Needs attention soon.

The rack [{#NAME}] is currently not operational.

The server hardware resource is a representation of a physical server.

Preprocessing

• JSON Path: $.members

• Discard unchanged with heartbeat: 6h

Data of the server [{#SERVER_NAME}:{#LOCATION}].

Preprocessing

• JSON Path: $.members[?(@.name == "{#LOCATION}")].first()

The maintenance flag of the Server Hardware - disruptive maintenance operations, such as firmware update, can cause many server hardware alerts to be generated in a short period of time. Example: network connectivity is lost or the server reset is detected. When this field is set, predefined alerts for this particular device are suppressed. This field is set only when firmware update is ongoing. The alerts are processed normally once firmware update operation completes. Possible values are Maintenance and Normal.

Preprocessing

• JSON Path: $.maintenanceState

  ⛔️Custom on fail: Discard value

• Replace: Maintenance -> 0

• Replace: Normal -> 1

• In range: 0 -> 1

  ⛔️Custom on fail: Set value to: 2

This field is set to Firmware update when the server is put under maintenance.

Preprocessing

• JSON Path: $.maintenanceStateReason

  ⛔️Custom on fail: Discard value

• Discard unchanged with heartbeat: 1h

The amount of memory installed on this server hardware.

Preprocessing

• JSON Path: $.memoryMb

• Custom multiplier: 1048576

• Discard unchanged with heartbeat: 1h

The state of an ongoing virtual connect manager (VCM) migration:

Migrating - the enclosure is in the process of migrating from VCM;

NotApplicable - the enclosure did not require or has already completed the migration;

Unknown - the migration state is unknown.

Preprocessing

• JSON Path: $.migrationState

  ⛔️Custom on fail: Discard value

• Replace: Migrating -> 0

• Replace: NotApplicable -> 1

• Replace: Unknown -> 2

• In range: 0 -> 2

  ⛔️Custom on fail: Set value to: 2

The model string of the full server hardware.

Preprocessing

• JSON Path: $.model

• Discard unchanged with heartbeat: 1d

The part number for this server hardware.

Preprocessing

• JSON Path: $.partNumber

• Discard unchanged with heartbeat: 1d

The current power state of the server hardware. The values are Unknown, On, Off, PoweringOn, PoweringOff or Resetting.

Preprocessing

• JSON Path: $.powerState

• Replace: PoweringOff -> 0

• Replace: PoweringOn -> 1

• Replace: Resetting -> 2

• Replace: Unknown -> 3

• Replace: Off -> 4

• Replace: On -> 5

• In range: 0 -> 5

  ⛔️Custom on fail: Set value to: 3

The number of cores available per processor.

Preprocessing

• JSON Path: $.processorCoreCount

• Discard unchanged with heartbeat: 1h

The number of processors installed on this server hardware.

Preprocessing

• JSON Path: $.processorCount

• Discard unchanged with heartbeat: 1h

The speed of the CPUs.

Preprocessing

• JSON Path: $.processorSpeedMhz

• Discard unchanged with heartbeat: 1h

The type of the CPU installed on this server hardware.

Preprocessing

• JSON Path: $.processorType

• Discard unchanged with heartbeat: 1d

The serial number of the server hardware.

Preprocessing

• JSON Path: $.serialNumber

• Discard unchanged with heartbeat: 1d

The current resource state of the server hardware. The allowable values are:

Unknown - not initialized;

Adding - a server is being added;

NoProfileApplied - a server successfully added;

Monitored - a server is being monitored;

Unmanaged - a discovered and supported server;

Removing - a server is being removed;

RemoveFailed - an unsuccessful server removal;

Removed - a server is successfully removed;

ApplyingProfile - a server is successfully removed;

ProfileApplied - a profile is successfully applied;

RemovingProfile - a profile is being removed;

ProfileError - an Unsuccessful profile is applied or removed;

Unsupported - a server model or version is not currently supported by the appliance;

UpdatingFirmware - a server firmware update is in progress.

Preprocessing

• JSON Path: $.state

• Replace: Unknown -> 0

• Replace: Adding -> 1

• Replace: NoProfileApplied -> 2

• Replace: Monitored -> 3

• Replace: Unmanaged -> 4

• Replace: Removing -> 5

• Replace: RemoveFailed -> 6

• Replace: Removed -> 7

• Replace: ApplyingProfile -> 8

• Replace: ProfileApplied -> 9

• Replace: RemovingProfile -> 10

• Replace: ProfileError -> 11

• Replace: Unsupported -> 12

• Replace: UpdatingFirmware -> 13

• In range: 0 -> 13

  ⛔️Custom on fail: Set value to: 0

The reason for the current resource state of the server hardware. This only applies if the state is Unmanaged, otherwise it is set to NotApplicable. The allowable values are:

Unsupported - a server model or version is not currently supported by the appliance;

UpdatingFirmware - a server firmware update is in progress;

NotApplicable - when PhysicalServerState is anything besides Unmanaged;

NotOwner - no claim on the server;

Inventory - a server is added by the PDU;

Unconfigured - the discovery data is incomplete or an iLO configuration has failed;

UnsupportedFirmware - an iLO firmware version is below the minimum support level;

Interrupted - when PhysicalServerState is a result of an operation that was terminated before completing;

CommunicationError - an appliance cannot communicate with an iLO or an OA.

Preprocessing

• JSON Path: $.stateReason

• Discard unchanged with heartbeat: 1h

The overall health status of the resource. The following are the valid values for the status of the resource:

OK - indicates normal/informational behavior;

Disabled - indicates that the resource is not operational;

Warning - requires attention soon;

Critical - requires immediate attention;

Unknown - should be avoided, but there may be rare occasions when the status is unknown.

Preprocessing

• JSON Path: $.status

• Discard unchanged with heartbeat: 10m

• Replace: Critical -> 0

• Replace: Disabled -> 1

• Replace: OK -> 2

• Replace: Unknown -> 3

• Replace: Warning -> 4

• In range: 0 -> 4

  ⛔️Custom on fail: Set value to: 3

The disruptive maintenance operations like firmware update can cause many server hardware alerts to be generated in a short period of time. Example: Network connectivity is lost or the server reset is detected.

The unsuccessful profile application or removal.

The server is not initialized.

The server model or version is not currently supported by the appliance.

The previous operation to remove the server hardware did not succeed. The operation should be re-attempted.

Discovered a supported server.

The status of the server [{#SERVER_NAME}:{#LOCATION}] is critical. Needs immediate attention.

The status of the server [{#SERVER_NAME}:{#LOCATION}] is warning. Needs attention soon.

The server [{#SERVER_NAME}:{#LOCATION}] is currently not operational.

A list of the storage pools.

Preprocessing

• JSON Path: $.members

• Discard unchanged with heartbeat: 6h

Data of the storage pool [{#NAME}].

Preprocessing

• JSON Path: $.members[?(@.name == "{#NAME}")].first()

The capacity allocated from the storage pool in bytes.

Preprocessing

• JSON Path: $.allocatedCapacity

The free capacity available from the storage pool in bytes.

Preprocessing

• JSON Path: $.freeCapacity

The pool capacity allocated to the snapshots in bytes.

Preprocessing

• JSON Path: The text is too long. Please see the template.

The current state of the resource:

AddFailed - an attempt to add the resource failed;

Adding - the resource is in the process of being added;

Configured - the resource is configured;

Connected - the appliance has connected to the resource;

Copying - the resource is in the process of being copied;

CreateFailed - an attempt to create the resource failed;

Creating - the resource is in the process of being created;

DeleteFailed - an attempt to delete the resource failed;

Deleting - the resource is in the process of being deleted;

Discovered - the resource has been discovered by the appliance, but it is not managed by the appliance;

Managed - the resource is managed by the appliance;

Normal - the resource is in a normal state;

UpdateFailed - an attempt to update the resource failed;

Updating - the resource is in the process of being updated.

Preprocessing

• JSON Path: $.state

• Replace: AddFailed -> 0

• Replace: Adding -> 1

• Replace: Configured -> 2

• Replace: Connected -> 3

• Replace: Copying -> 4

• Replace: CreateFailed -> 5

• Replace: Creating -> 6

• Replace: DeleteFailed -> 7

• Replace: Deleting -> 8

• Replace: Discovered -> 9

• Replace: Managed -> 10

• Replace: Normal -> 11

• Replace: UpdateFailed -> 12

• Replace: Updating -> 13

• In range: 0 -> 13

  ⛔️Custom on fail: Set value to: 14

The overall health status of the resource. The following are the valid values for the status of the resource:

OK - indicates normal/informational behavior;

Disabled - indicates that the resource is not operational;

Warning - requires attention soon;

Critical - requires immediate attention;

Unknown - should be avoided, but there may be rare occasions when the status is unknown.

Preprocessing

• JSON Path: $.status

• Discard unchanged with heartbeat: 10m

• Replace: Critical -> 0

• Replace: Disabled -> 1

• Replace: OK -> 2

• Replace: Unknown -> 3

• Replace: Warning -> 4

• In range: 0 -> 4

  ⛔️Custom on fail: Set value to: 3

The total capacity of the storage pool in bytes.

Preprocessing

• JSON Path: $.totalCapacity

Adding of the storage pool [{#NAME}] failed.

Creating of the storage pool [{#NAME}] failed.

Deletion of the storage pool [{#NAME}] failed.

Updating of the storage pool [{#NAME}] failed.

The status of the storage pool [{#NAME}] is critical. Needs immediate attention.

The status of the storage pool [{#NAME}] is warning. Needs attention soon.

The storage pool [{#NAME}] is currently not operational.

A list of the storage systems.

Preprocessing

• JSON Path: $.members

• Discard unchanged with heartbeat: 6h

Data of the storage system [{#NAME}].

Preprocessing

• JSON Path: $.members[?(@.name == "{#NAME}")].first()

The capacity allocated in bytes.

Preprocessing

• JSON Path: $.allocatedCapacity

The free capacity of the storage system in bytes.

Preprocessing

• JSON Path: $.freeCapacity

The current state of the resource:

AddFailed - an attempt to add the resource failed;

Adding - the resource is in the process of being added;

Configured - the resource is configured;

Connected - the appliance has connected to the resource;

Copying - the resource is in the process of being copied;

CreateFailed - an attempt to create the resource failed;

Creating - the resource is in the process of being created;

DeleteFailed - an attempt to delete the resource failed;

Deleting - the resource is in the process of being deleted;

Discovered - the resource has been discovered by the appliance, but it is not managed by the appliance;

Managed - the resource is managed by the appliance;

Normal - the resource is in a normal state;

UpdateFailed - an attempt to update the resource failed;

Updating - the resource is in the process of being updated.

Preprocessing

• JSON Path: $.state

• Replace: AddFailed -> 0

• Replace: Adding -> 1

• Replace: Configured -> 2

• Replace: Connected -> 3

• Replace: Copying -> 4

• Replace: CreateFailed -> 5

• Replace: Creating -> 6

• Replace: DeleteFailed -> 7

• Replace: Deleting -> 8

• Replace: Discovered -> 9

• Replace: Managed -> 10

• Replace: Normal -> 11

• Replace: UpdateFailed -> 12

• Replace: Updating -> 13

• In range: 0 -> 13

  ⛔️Custom on fail: Set value to: 14

The overall health status of the resource. The following are the valid values for the status of the resource:

OK - indicates normal/informational behavior;

Disabled - indicates that the resource is not operational;

Warning - requires attention soon;

Critical - requires immediate attention;

Unknown - should be avoided, but there may be rare occasions when the status is unknown.

Preprocessing

• JSON Path: $.status

• Discard unchanged with heartbeat: 10m

• Replace: Critical -> 0

• Replace: Disabled -> 1

• Replace: OK -> 2

• Replace: Unknown -> 3

• Replace: Warning -> 4

• In range: 0 -> 4

  ⛔️Custom on fail: Set value to: 3

The total capacity of the storage system in bytes.

Preprocessing

• JSON Path: $.totalCapacity

Adding the storage system [{#NAME}] failed.

Creating of the storage system [{#NAME}] failed.

Deletion of the storage system [{#NAME}] failed.

Updating of the storage system [{#NAME}] failed.

The status of the storage system [{#NAME}] is critical. Needs immediate attention.

The status of the storage system [{#NAME}] is warning. Needs attention soon.

The storage system [{#NAME}] is currently not operational.

A list of the storage volumes.

Preprocessing

• JSON Path: $.members

• Discard unchanged with heartbeat: 6h

Data of the storage volume [{#NAME}].

Preprocessing

• JSON Path: $.members[?(@.name == "{#NAME}")].first()

The capacity allocated in bytes.

Preprocessing

• JSON Path: $.allocatedCapacity

The total provisioned capacity of the volume in bytes.

Preprocessing

• JSON Path: $.provisionedCapacity

The current state of the resource:

AddFailed - an attempt to add the resource failed;

Adding - the resource is in the process of being added;

Configured - the resource is configured;

Connected - the appliance has connected to the resource;

Copying - the resource is in the process of being copied;

CreateFailed - an attempt to create the resource failed;

Creating - the resource is in the process of being created;

DeleteFailed - an attempt to delete the resource failed;

Deleting - the resource is in the process of being deleted;

Discovered - the resource has been discovered by the appliance, but it is not managed by the appliance;

Managed - the resource is managed by the appliance;

Normal - the resource is in a normal state;

UpdateFailed - an attempt to update the resource failed;

Updating - the resource is in the process of being updated.

Preprocessing

• JSON Path: $.state

• Replace: AddFailed -> 0

• Replace: Adding -> 1

• Replace: Configured -> 2

• Replace: Connected -> 3

• Replace: Copying -> 4

• Replace: CreateFailed -> 5

• Replace: Creating -> 6

• Replace: DeleteFailed -> 7

• Replace: Deleting -> 8

• Replace: Discovered -> 9

• Replace: Managed -> 10

• Replace: Normal -> 11

• Replace: UpdateFailed -> 12

• Replace: Updating -> 13

• In range: 0 -> 13

  ⛔️Custom on fail: Set value to: 14

The overall health status of the resource. The following are the valid values for the status of the resource:

OK - indicates normal/informational behavior;

Disabled - indicates that the resource is not operational;

Warning - requires attention soon;

Critical - requires immediate attention;

Unknown - should be avoided, but there may be rare occasions when the status is unknown.

Preprocessing