Regular expression examples
A small sample of the possible constructs for Regular Expressions.
| Example of | Code | Description |
|---|---|---|
|
OR functionality |
usage | space |
Matches events with usage or space. The vertical bar separates alternatives. |
|
Matching preceding character zero or one time |
file? |
Matches events that contain fil or file, such as filesystem. In addition to ?, the * and + characters can be used to match a set of strings. |
|
Bracket construct |
slices[te] |
Matches events with terms such as, slicestor, sliceserver, etc. The items in the bracket are interpreted as t or e. |
|
One term followed by another |
reporting status |
Matches events with reporting status. This pattern represents a request to match based on a specific ordering, one term after another. It is a constrained AND search. |
|
Combining parentheses with a preceding element 0 or 1 time |
r(eb)?oot |
Matches events with root and reboot |
An error is displayed if an invalid regular expression is provided.
Search covers all items, both events and incidents. The severity filter allows for multiple severity types to be identified. Multiple devices, cabinets, sites, and storage pools can be selected, depending on context.
All filters appear on the dashboard and top Monitor page, but the Monitor Storage Pool page contains Slicestor® devices.
As filters are chosen, they are displayed in the Current Filter section. It is recommended to specify a time range to reduce the search scope.