Trace Processors

Enter a descriptive label for this processor. 

When you create a workflow, you will use this label to enter your processor into the workflow in the visual editor. 

This parameter is required. 

Review the following example:

name: login-trace

Enter a regular expression to match patterns in a string for a successful event.

This parameter is required. 

Review the following example: 

start_pattern: "user (?P<ID>[0-9a-fA-F]{8}) logged in"

Enter a regular expression to match patterns in a string for a failed event.

This parameter is required. 

Review the following example: 

finish_pattern: "user (?P<ID>[0-9a-fA-F]{8}) logged out"

This parameter is a golang duration string that represents the reporting (or rollup) interval for the generated statistics.

The default value is 1m.

This parameter is optional. 

Review the following example: 

interval: 2m

This parameter is a golang duration string that represents how far back the agent should look when generating anomaly scores.

The default value is 3h.

This parameter is optional. 

Review the following example: 

retention: 4h

This parameter defines threshold limits, based on calculated metrics.

When a threshold is reached, the agent notifies the corresponding trigger destinations in the same workflow.

You can configure the following trigger threshold types:

• max_duration
• anomaly_probability_percentage
• upper_limit_per_interval
• lower_limit_per_interval
• consecutive

This parameter is optional. 

Review the following example: 

trigger_thresholds: 
  anomaly_probability_percentage: 90
  upper_limit_per_interval: 250
  consecutive: 5

Enter the maximum amount of time that an event is allowed to complete. 

If an event does not complete within this duration, then a trigger is generated.

This parameter is optional. 

Review the following example: 

trigger_thresholds:
  max_duration: 50000 

This parameter sets the confidence level / probability of an anomaly that needs to be reached to trigger an alert. 

For example, if you enter 90, then an alert will trigger when there is a 90% probability that the detected pattern is an anomaly. 

Enter a number between 0 and 100.

There is no default value. 

This parameter is optional.

Review the following example: 

trigger_thresholds: 
  anomaly_probability_percentage: 90

This parameter sets a static threshold to trigger an alert.  

If the number of events that match the given pattern for the most recent reporting interval is greater than the limit, then an alert will be triggered.

There is no default value. 

This parameter is optional.

Review the following example:  

trigger_thresholds: 
  upper_limit_per_interval: 250

This parameter sets a static threshold to trigger an alert.

If the number of events that match the given pattern for the most recent reporting interval is less than the limit, then an alert will trigger.

There is no default value. 

This parameter is optional.

Review the following example: 

trigger_thresholds: 
  lower_limit_per_interval: 10

This parameter sets how many consecutive times a threshold must be exceeded to trigger an alert.  

The default value is 0, which means that any condition that is met will trigger an alert. 

This parameter is optional.

Review the following example:

trigger_thresholds: 
  consecutive: 5

Select an existing filter to add to this processor. 

To learn how to create a filter, see Filters.

This parameter is optional. 

Review the following example: 

filters:
  - extract_severity