Edge Delta Conditional Group Processor

The Edge Delta conditional group processor groups processors under a condition.

3 minute read

Overview

The conditional group processor groups existing processors and executes them in sequence only if a condition is met. This is different to enabling individual conditions on each processor and is a method for branching the processing logic. You might use this approach if a required condition for a second processor would be removed by a preceding processor.

Configuration

To configure this processor, drag existing processors into it and configure the parent condition. You can order the processors in the execution order. In this example, the extract metric and aggregate metric processors execute on data items where the level attribute is Emergency.

This configuration generates the following YAML:

- name: kubernetes_input_jt1iw_multiprocessor
  type: sequence
  processors:
  - type: sequence
    metadata: '{"id":"KhP8KO88Kvhitx9aN_3pQ","type":"sequence","name":"Conditional
      Group"}'
    condition: attributes["level"] == "Emergency"
    processors:
    - type: extract_metric
      metadata: '{"id":"_rK4ucX4G8oDcrXWwXh2r","type":"extract_metric","name":"Extract
        Metric"}'
      extract_metric_rules:
      - name: status_code
        description: A count of each unique status code
        unit: "1"
        gauge:
          value: attributes["status"]
    - type: aggregate_metric
      metadata: '{"id":"NoQMsANzEU7ltYMb5r1G0","type":"aggregate_metric","name":"Aggregate
        Metric"}'
      data_types:
      - metric
      aggregate_metric_rules:
      - name: Count per status code
        conditions:
        - attributes["response_time_ms"] > 2500
        interval: 1m0s
        aggregation_type: count

Options

condition

The condition parameter contains a conditional phrase of an OTTL statement. It restricts operation of the processor to only data items where the condition is met. Those data items that do not match the condition are passed without processing. You configure it in the interface and an OTTL condition is generated. It is optional. You can select one of the following operators:

Operator	Name	Description	Example
`==`	Equal to	Returns `true` if both values are exactly the same	`attributes["status"] == "OK"`
`!=`	Not equal to	Returns `true` if the values are not the same	`attributes["level"] != "debug"`
`>`	Greater than	Returns `true` if the left value is greater than the right	`attributes["duration_ms"] > 1000`
`>=`	Greater than or equal	Returns `true` if the left value is greater than or equal to the right	`attributes["score"] >= 90`
`<`	Less than	Returns `true` if the left value is less than the right	`attributes["load"] < 0.75`
`<=`	Less than or equal	Returns `true` if the left value is less than or equal to the right	`attributes["retries"] <= 3`
`matches`	Regex match	Returns `true` if the string matches a regular expression	`isMatch(attributes["name"], ".*\\.name$"`

It is defined in YAML as follows:

- name: _multiprocessor
  type: sequence
  processors:
  - type: <processor type>
    condition: attributes["request"]["path"] == "/json/view"

processors

The processors parameter specifies the processors that are child objects of the multiprocessor or a conditional group processor. They define a processor and all its required parameters. You define it by dragging existing processors onto the Conditional Group. A processors parameter is required for a conditional group processor.