You can forward unprocessed or processed data from Dynatrace to your cloud object storage via OpenPipeline.
To set up forwarding, see Configure forwarding via OpenPipeline.
Forwarding is an OpenPipeline data-flow step to forward records from OpenPipeline to supported cloud object storage for compliance, auditing, or external system integration.
You can choose to forward records
Forwarding configurations define how Dynatrace should forward a set of records to your cloud object storage. Each configuration is bound to its configuration scope (such as logs, events, or metrics). You can create multiple forwarding configurations and switch on/off, modify, or delete existing ones.
Each forwarding configuration specifies whether to send processed or unprocessed records, the source, and the destination. It consists of the following:
Name: A unique custom identifier
Source: The existing ingest sources or pipelines whose records you want to forward. Depending on the source, the forwarding configuration sends unprocessed or processed records. If you choose to send from
Matching condition: The DQL query that defines the data set you want to forward.
Destination: The cloud object storage to which you want to forward your records. It's defined by
A connection with a Dynatrace AWS or Azure Connector pointing to the cloud object storage.
A valid cloud vendor storage identifier (the bucket name in AWS or GCP and the container URL in Azure)
Segmentation
Records to forward are grouped in batches approximately either once a minute or when they reach maximum 16 MB of size. Then they are assigned a bulk pattern and are compressed into GZIP NDJSON format. Forwarded records contain the pattern placeholders in their path in the following order:
Optional Date and time placeholders:
<DDMMYYYY><YYYYMMDD><HH><HHmmss.SSSS>Required Bulk identifier: <bulk-id>
Required Bulk format: .json.gz
If .gz is omitted, GZIP is still executed, and the file has a non-matching file extension.
Additional optional processing: Apply further processing to records and forward only what the destination system requires. Available processors include DQL, Add fields, Remove fields, Drop, and Rename fields.
You can manage forwarding configurations via the Settings API POST /api/v2/settings/objects request and the data-forwarding schema of the configuration scope:
builtin:openpipeline.<configuration.scope>.data-forwarding
Replace <configuration.scope> with the scope you want to forward.
bizevents)davis.events)davis.problems)events)events.sdlc)events.security)logs)metrics)security.events)smartscape.events)spans)system.events)user.events)usersessions)