Davis stage in OpenPipeline
- Latest Dynatrace
- Explanation
- 4-min read
- Published Aug 20, 2026
This article describes the Davis stage in OpenPipeline and the available processors. In the Davis stage, you can extract Davis events from incoming records that match a condition and send them to root cause analysis. 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:
- Davis event
Davis event processor
The Davis event processor extracts a Davis event from a record and sends it to root cause analysis, where it can be used for anomaly detection, problem correlation, and alerting.
Davis 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 Davis 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 name | Name of the created Davis event. Supports template variables ( | Required |
Event description | Additional context for the event. Supports Markdown formatting. | Optional |
Event properties | Predefined list of key-value pairs to attach to the triggered event. Add further properties to provide more context for problem correlation. | Optional |
Example: Create a Davis event from a log record
The following example creates a Davis event when a log record signals a high error rate, providing context for Dynatrace Intelligence causal AI to correlate with related problems.
The processor applies to all records that match the following condition:
matchesValue(log.level, "ERROR") AND toDouble(error.rate_percent) > 5.0
The matching condition applies to
{"timestamp": "2026-06-01T10:00:00Z","log.level": "ERROR","service.name": "payment-api","error.rate_percent": 7.2,"content": "Error rate threshold exceeded"}
The event template is configured as follows:
- Event name:
High error rate on {service.name} - Event description:
Error rate reached {error.rate_percent}% on {service.name}. Investigate affected service. - Event properties:
event.type = CUSTOM_ALERT
The processor extracts a Davis event with the title High error rate on payment-api and sends it to root cause analysis. Dynatrace Intelligence causal AI processes the event and can correlate it with related problems on the service.
To learn more, see Set up alerts based on events extracted from logs and Detect problems with Logs.
Use cases
- Trigger Davis alerts from log records that signal application or infrastructure threshold breaches.
- Correlate events from multiple data sources, such as logs and metrics, in the Dynatrace Intelligence causal AI problem feed.
- Generate custom alerts from telemetry sources that don't natively produce Davis events.
OpenPipeline