Data extraction stage in OpenPipeline
- Latest Dynatrace
- Explanation
- 6-min read
- Published Aug 20, 2026
This article describes the Data extraction stage in OpenPipeline and the available processors. In the Data extraction stage, you can extract new records from incoming records that match a condition and re-ingest them as a different data type into another pipeline. Extracted events require dedicated permissions and licensing capabilities.
Get familiar with OpenPipeline concepts of stage and processors. To learn more, see Processing in OpenPipeline.
Processors
The processors in the stage are:
- Business event
- Software development lifecycle event
Business event processor
The Business event processor extracts a business event and re-ingests it. The new event can be processed via pipelines in the OpenPipeline business events configuration scope and used for domain-specific activities such as purchases, user registrations, or transactions.
Business events extracted by this processor are not billed on ingest, but add to retain billing. To learn more, see Events - Retain.
Parameters
The following table describes the parameters available in the Business event processor.
| Parameter | Description | Required |
|---|---|---|
Name | Name of the processor. | Required |
Matching condition | DQL statement that identifies the records the processor applies to. | Required |
Event type | Type identifier for the extracted business event. Use Field name to derive the value from a record field, or Static string to set a fixed value. | Required |
Event provider | Provider identifier for the extracted event, typically the service or application name. Use Field name to derive the value from a record field, or Static string to set a fixed value. | Required |
Field extraction | Controls which source record fields are forwarded to the extracted event. Options are Extract all fields (default), Fields to extract (include only listed fields), and Fields not to extract (exclude listed fields). To learn more about field handling, see Extraction stages in OpenPipeline. | Required |
Example: Extract a purchase event from logs
The following example extracts business events from log records written when a checkout completes.
The processor applies to all records that match the following condition:
matchesValue(event.type, "purchase.*")
The processor is configured as follows:
- Event type (Field name):
event.type - Event provider (Static string):
checkout-service - Field extraction: Extract all fields
Unprocessed
{"timestamp": "2026-06-01T10:00:00Z","event.type": "purchase.completed","order.id": "ORD-7891","order.amount": 149.99,"dt.security_context": "team-commerce"}
The processor extracts a business event of type purchase.completed from provider checkout-service, with all source record fields included.
For a complete use case, see Get business events from logs and spans.
Software development lifecycle event
The Software development lifecycle event processor extracts an SDLC event and re-ingests it. The new event can be processed by pipelines in the OpenPipeline SDLC configuration scope and used to track deployments, builds, and releases from CI/CD logs or generic events.
SDLC events extracted by this processor are not billed on ingest, but add to retain billing. To learn more, see Calculate your consumption of Events - Retain (DPS).
Parameters
The following table describes the parameters available in the Software development lifecycle event processor.
| Parameter | Description | Required |
|---|---|---|
Name | Name of the processor. | Required |
Matching condition | DQL statement that identifies the records the processor applies to. | Required |
Event type | The SDLC event type, for example, | Required |
Event provider | The source system or tool that produced the event, for example, | Required |
Event category | A grouping category for the event, for example, | Required |
Event status | The outcome of the SDLC activity, for example, | Required |
Field extraction | Controls which source record fields are forwarded to the extracted event. Options are Extract all fields (default), Fields to extract (include only listed fields), and Fields not to extract (exclude listed fields). To learn more about field handling, see Extraction stages in OpenPipeline. | Required |
Example: Extract a deployment event from CI/CD logs
The following example extracts SDLC deployment events from logs emitted by a CI/CD system when a deployment completes.
The processor applies to all records that match the following condition:
matchesValue(ci.event_type, "deployment") AND isNotNull(ci.status)
The processor is configured as follows:
- Event type (Static string):
deployment - Event provider (Field name):
ci.system - Event category (Static string):
release - Event status (Field name):
ci.status - Field extraction: Extract all fields
Unprocessed
{"timestamp": "2026-06-01T10:00:00Z","ci.event_type": "deployment","ci.system": "GitHub Actions","ci.status": "success","service.name": "payment-api","version": "3.14.1"}
The processor extracts an SDLC event with type deployment, provider GitHub Actions, category release, and status success, with all source record fields included.
Use cases
- Extract business events from logs to support domain-focused analysis and dashboards.
- Derive SDLC events from CI/CD logs to track deployments, builds, and releases in Dynatrace.
Related topics
OpenPipeline