Business event processing via classic pipeline

Dynatrace Classic
Tutorial
5-min read
Published Oct 24, 2022

Business event processing via the classic pipeline allows you to define how your data will be processed further.

You can create a processing rule that transforms incoming events.
You can also specify the retention time for your events by assigning them to buckets.

If you create multiple rules, the rules are performed in the order in which you have defined them.

We recommend utilizing business event processing with OpenPipeline as a scalable, powerful solution to manage and process business events. If you don't have access to OpenPipeline, use the classic business event processing pipeline.

Configure business event processing rules

To configure business event processing rules

Go to Settings > Business Observability > Ingest Pipeline > Processing.
Select Add rule and name your rule.
Add a Matcher to your rule by pasting your matcher-specific DQL query.

Matching based on previous rules is not supported
The matcher operates on the initial data set before applying any processing rules. Matching records modified by preceding rules is not supported. For example, the modified value of an attribute in rule 1 cannot be used as a matching value in rule 2.
Select Add item to choose the fields you will transform via the processor definition. Determine the data types and names for your fields. You can choose if the rule is Optional, Is Array, or Read-only.
- Optional: If a transformation field is marked as optional, the transformation can happen even if the field is not provided. But if a transformation field is marked as mandatory (not optional) , the transformation occurs only if the field is present in the incoming data.
- Is Array: Needs to be selected when a field contains multiple values, and you intend to work with specific values.
- Read-Only: Cannot be changed during transformation.
Add a Processor definition. Processor definitions are instructions that tell Dynatrace how to transform the data you’ve selected in the matcher DQL query. It is created using processing commands, functions and pattern matching (Dynatrace Pattern Language) that allows you to add, modify or remove incoming records.
In the Rule testing section, paste an event sample and run the test.

Your incoming data example needs to be provided in the JSON format.
Select Save changes.

Business event processing via classic pipeline

Dynatrace Classic

Tutorial

5-min read

Published Oct 24, 2022

Business event processing via the classic pipeline allows you to define how your data will be processed further.

You can create a processing rule that transforms incoming events.
You can also specify the retention time for your events by assigning them to buckets.

If you create multiple rules, the rules are performed in the order in which you have defined them.

Configure business event processing rules

To configure business event processing rules

Go to Settings > Business Observability > Ingest Pipeline > Processing.
Select Add rule and name your rule.
Add a Matcher to your rule by pasting your matcher-specific DQL query.

Matching based on previous rules is not supported
The matcher operates on the initial data set before applying any processing rules. Matching records modified by preceding rules is not supported. For example, the modified value of an attribute in rule 1 cannot be used as a matching value in rule 2.
Select Add item to choose the fields you will transform via the processor definition. Determine the data types and names for your fields. You can choose if the rule is Optional, Is Array, or Read-only.
- Optional: If a transformation field is marked as optional, the transformation can happen even if the field is not provided. But if a transformation field is marked as mandatory (not optional) , the transformation occurs only if the field is present in the incoming data.
- Is Array: Needs to be selected when a field contains multiple values, and you intend to work with specific values.
- Read-Only: Cannot be changed during transformation.
Add a Processor definition. Processor definitions are instructions that tell Dynatrace how to transform the data you’ve selected in the matcher DQL query. It is created using processing commands, functions and pattern matching (Dynatrace Pattern Language) that allows you to add, modify or remove incoming records.
In the Rule testing section, paste an event sample and run the test.

Your incoming data example needs to be provided in the JSON format.
Select Save changes.