Conditional
Current version v1.0.0
Last updated
Was this helpful?
Current version v1.0.0
Last updated
Was this helpful?
This action evaluates a list of conditions for an event. If an event meets a given condition, it will be sent through an output port specific to that condition. If the event does not meet any condition, it will be sent through the default output.
Set any number of conditions on your data for filtering and alerting.
In order to configure this action, you must first link it to a Listener. Go to Building a Pipeline to learn how to link.
These are the input and output ports of this Action:
To open the configuration, click the Action in the canvas and select Configuration.
Enter the required parameters:
View mode
Select your conditions using the buttons available, or write it in Code mode.
Field*
The Field option lets you choose not only the field to filter for, but the specific Action to take it from.
Conditions
Choose between the following conditions for the filter (or use the arrow keys on your keyboard to navigate up and down the list). The options you see here will differ depending on the data type of the field you have selected.
Number
(<) Less than
(≤) Less than or equal to
(>) Greater than
(≥) Greater than or equal to
(=) Equal to
(!=) Not equal to
String
Contains
Doesn't contain
Equal
Not equal
Boolean
Equal
Not equal
Contains
Does not contain
Equal to
Not equal to
Enter the value to filter in (remember to press enter if you´re writing one) and you have your condition.
Field
Choose the field to carry out the condition on.
AND/OR
Now you can add AND/OR clauses to your condition, or add a new condition entirely using the Add Condition option. Add string (contains, not contain, equals, not equal) or int (greater, less, equal, not equal) using OR & AND.
Rate Limiter Configuration
Number of requests per second*
Set a limit on the number of requests per second to launch on the ser
Click Save to complete.
Let's say you have data on error and threat detection methods in storage devices and you wish to detect threats and errors using the Cyclic Redundancy Check methods crc8, crc16 and crc24.