CLI Guide

Table Of Contents

7 - debug (debug-level messages)

6 - info (informational messages)

5 - notice (normal but significant messages)

4 - warning (warning messages)

3 - err (error messages)

2 - crit (critical messages)

1 - alert (messages that must be handled immediately)

0 - emerg (messages notifying the system as unusable)

Default modifier is>.

[-c|--component]

name

Component name to filter. Takes a regular expression as an argument. Plain strings are searched

for in the component name.

[-e|--event-num] id Used in conjunction with a specified component. An event ID to filter.

[-m|--message] text An expression to look for in the event message. Takes a regular expression as an argument. Plain

strings are searched for in the message text.

[-n|--no-consume]

Do not halt event processing after an event matches a filter.

Description

Log filters define criteria for the destination of specific log data. A filter is placed in an ordered list, and filters see received

events in the order they sit in the list (shown by the log filter list command).

By default, filters consume received events so that a matching filter stops the processing of the event. Use the --no-

consume argument to create a filter that allows processing of matching events to continue.

Example

Filter out (hide) all messages with the string test in them:

VPlexcli:/> log filter create -m "test"

Filter added.

Filter all messages into the events log generated by the logserver component with the string Test:

VPlexcli:/> log filter create --source 1 --component logserver --message Test

Filter added.

VPlexcli:/> log filter list

1. [Source='/var/log/VPlex/cli/events.log', Component='logserver', Message matches

'Test'] Destination='null' Consume='true'

2. Component='logserver' Destination='null' Consume='true'

3. [Threshold='>0'] Destination='null' Consume='true'