Dell PowerFlex Manager 4.6.x CLI Reference Guide

Following are some examples of filter formats:

• query to get all alerts filtered by name=HEALTH_CHECK_FAILED -

  ./powerflex_cli alerts query --session_token 0541629989f63e34 --filter 'name eq HEALTH_CHECK_FAILED'

• query alerts on multiple filters - name = HEALTH_CHECK_FAILED and severity=CRITICAL

  ./powerflex_cli alerts query --session_token 0541629989f63e34 --filter 'name eq HEALTH_CHECK_FAILED' --filter 'severity eq CRITICAL'

• query events -

  ./powerflex_cli events query --session_token a909dcc30ddca7a9

• query events with filters -

  ./run_cli.sh events query --session_token a909dcc30ddca7a9 --filter 'code eq 20010001'

You can use the following with the filters:

• eq—
• ne—means 'not equal' - can be used in the same way of "eq"
• like—when you want to query all the items that their description contains a substring. and you can use "%" as a wildcard.

  For example:

  filter=description like "%this is %"

  It returns all the items with the substring "this is " anywhere in the string. the usage and behavior of like operator and "%" is exactly as in SQL.

• in—to retreive elements that the field value is one of that list. filter=name in (SDS, PROTECTION_DOMAIN)
• gt—greater than (>)
• lt—less then (<)
• ge—greater then equal (>=)
• le—less then or equal (<=)

The greater than, less than, greater than or equal to, and less than or equal to operators behave the same as the corresponding SQL operator in brackets. They are used in the syntax similarly to equal to or not equal to operators.