arrayTranslate (Compute)

When To Use

Use arrayTranslate when a single cell contains several values packed into one string — typically a WMI/WBEM array property such as OperationalStatus, which the engine serializes as 2|11. Each element is split out, translated individually through the translation table, and the non-empty results are re-joined.

Element matching is case-insensitive, like translate^[1]. Elements that translate to an empty string are dropped from the result; unmatched elements take the table's default translation, or are dropped as well if there is no default entry.

Syntax

sources:
  physicalDisks:
    # __PATH;DeviceId;OperationalStatus
    type: wmi
    namespace: root\Microsoft\Windows\Storage
    query: SELECT __PATH, DeviceId, OperationalStatus FROM MSFT_PhysicalDisk
    computes:
    - type: arrayTranslate
      column: 3
      translationTable: ${translation::OperationalStatusInformationTranslationTable}
      resultSeparator: ' - '

# Translation tables are declared in the top-level `translations:` section
translations:
  OperationalStatusInformationTranslationTable:
    "2": ""
    "11": In Service
    "13": Lost Communication
    "53272": Device Hardware Error
    default: Unknown

Properties

Table Transformation Example

With the table above, column: 3 and resultSeparator: ' - ':

On the first row, 2 translates to an empty string and is silently dropped, leaving only In Service.

Recommended Pattern

• Map “everything is fine” codes to "" so healthy elements disappear and only anomalies remain in the informational text.
• To turn a status array into a single monitorable state, first arrayTranslate the codes into ok/degraded/failed, then apply convert^[2] with array2SimpleStatus to keep the worst one (see WinStorageSpaces).
• Use duplicateColumn upstream when you need both an informational text and a status derived from the same array.

Common Mistakes

• Forgetting that arraySeparator is a regular expression: a separator like . or + must be escaped (\., \+).
• Expecting unmatched elements to pass through unchanged: without a default entry they are removed entirely, which can produce empty cells.
• Using arrayTranslate on a plain single-value column — translate^[1] is the right compute there.
• Miscounting the column index: WMI sources prepend requested properties in query order, and __PATH counts as a column.

Community Examples

• WinStorageSpaces^[3]

From WinStorageSpaces, included directly from the connector source:

  # Translate the 2nd OperationalStatus field into a more readable string
  # __PATH;DeviceId;Status;StatusInformation;OperationalStatus
- type: arrayTranslate
  column: 4
  translationTable: ${translation::OperationalStatusInformationTranslationTable}
  resultSeparator: ' - '