Changelog for log technology bundle processors

Latest Dynatrace
Reference
Published May 07, 2026

Technology bundle processors include updates to the extracted fields, ensuring compliance with the Dynatrace Semantic Dictionary, and support additional use cases. This improves consistency, enables unified querying, and provides a better experience when working with logs and metrics across Dynatrace.

When processors are renamed or fields are renamed, removed, or restructured, the changes aren't automatically applied to your existing configurations.

Dynatrace still supports deprecated field names.

Overview

This page tracks updates to technology bundle processors delivered with each Dynatrace SaaS release, including renamed processors, changed field names, and removed fields. It also lists field name changes introduced when migrating from classic pipeline built-in processors to their OpenPipeline technology bundle equivalents.

Use this changelog to identify which fields and processors in your existing pipelines are affected, then follow the steps below to replace deprecated bundles with their current versions.

Update deprecated technology bundles

To replace a deprecated technology bundle, add the new version of that technology bundle, and then remove the one marked with the (Deprecated) tag, as per below:

Go to Settings > Process and contextualize > OpenPipeline > Logs > Pipelines.
Open each pipeline, and check if you have deprecated technology bundles.
If you find one, select Processor on the Processing tab, and select Technology bundle.
Choose the new version of technology you want to replace and select Choose.
Place the new technology bundle directly under the deprecated one.
Select (Actions menu) on the deprecated technology bundle.
Select Delete > Confirm.
Select Save.
Repeat steps 3–8 for each deprecated technology bundle that you want to replace.

Updates in Dynatrace SaaS 1.333

The following updates are introduced with Dynatrace SaaS version 1.333.

Changes to technology processor names

The Azure All-in-one technology processor is now Azure Services.

Changes to technology processor fields

The technology processor fields are updated as per the table below.

Technology	Change type	Deprecated field name	New field name
.NET	Changed	`logger.name`	`log.logger`
.NET	Changed	`line`	`code.line.number`
Go	Changed	`code.lineno`	`code.line.number`
Java	Changed	`logger.name`	`log.logger`
Java	Changed	`process.id`	`process.pid`
Java	Changed	`line`	`code.line.number`
NodeJS	Changed	`logger`	`log.logger`
NodeJS	Changed	`http.user_auth`	`user.id`
NodeJS	Changed	`http.version`	`network.protocol.version`
NodeJS	Changed	`http.referrer`	`http.request.header.referer`
NodeJS	Changed	`http.user_agent`	`browser.user_agent`
NodeJS	Changed	`pid`	`process.pid`
NodeJS	Changed	`http.status_code`	`http.response.status_code`
PHP	Changed	`logger.name`	`log.logger`
PHP	Changed	`priority`	`log.raw_level`
Python	Changed	`logger.name`	`log.logger`
Python	Changed	`process.id`	`process.pid`
Python	Changed	`function.name`	`code.function`
Ruby	Changed	`process.id`	`process.pid`
Amazon VPC	Changed	`protocol.number`	`network.protocol.number`
Amazon VPC	Changed	`protocol.name`	`network.protocol.name`
AWS Transit Gateway	Changed	`protocol.number`	`network.protocol.number`
AWS WAF	Changed	`http.request.version`	`network.protocol.name` + `network.protocol.version`
AWS WAF	Changed	`http.status_code`	`http.response.status_code`
JBoss	Changed	`logger.name`	`log.logger`
JBoss	Changed	`http.status_code`	`http.response.status_code`
Microsoft IIS	Changed	`http.target`	`url.path`
Microsoft IIS	Changed	`http.status_code`	`http.response.status_code`
Microsoft IIS	Changed	`referrer`	`http.request.header.referer`
Apache Tomcat	Changed	`logger.name`	`log.logger`
AWS CloudTrail	Changed	`eventTime`	`audit.time`
AWS CloudTrail	Changed	`eventSource`	`object.name`
AWS CloudTrail	Changed	`eventType` + `eventName`	`audit.action`
AWS CloudTrail	Changed	`awsRegion`	`aws.region`
AWS CloudTrail	Changed	`sourceIPAddress`	`client.ip`
AWS CloudTrail	Changed	`userAgent`	`browser.user_agent`
AWS CloudTrail	Changed	`errorCode`	`result.detail`
AWS CloudTrail	Changed	`errorMessage`	`result.message`
AWS CloudTrail	Changed	`eventCategory`	`log.source`
AWS CloudTrail	Changed	`userIdentity`	`audit.identity`
AWS CloudTrail	Changed	`responseElements.ConsoleLogin`	`audit.result`
AWS CloudTrail	Removed	`additionalEventData`
AWS CloudTrail	Removed	`requestParameters`
AWS CloudTrail	Removed	`responseElements`
AWS CloudTrail	Removed	`requestID`
AWS CloudTrail	Removed	`eventID`
AWS CloudTrail	Removed	`readOnly`
AWS CloudTrail	Removed	`recipientAccountId`
AWS CloudTrail	Removed	`vpcEndpointId`
AWS CloudTrail	Removed	`sharedEventID`
AWS CloudTrail	Removed	`eventVersion`
AWS CloudTrail	Removed	`apiVersion`
AWS CloudTrail	Removed	`managementEvent`
AWS CloudTrail	Removed	`resources`

Field name changes from classic pipeline

The table below lists technology bundles whose extracted field names have changed compared to the equivalent classic pipeline built-in processors.

Technology name	Change type	Deprecated field name	New field name
Nginx	Changed	`http.flavor`	`network.protocol.name` + `network.protocol.version`
Nginx	Changed	`net.peer.ip`	`network.peer.ip`
Nginx	Changed	`http.host`	`dt.http.request.header.host`
Nginx	Changed	`http.response_content_length`	`http.response.body.size`
Nginx	Changed	`http.status_code`	`http.response.status_code`
Nginx	Changed	`http.user_agent`	`browser.user_agent`
Nginx	Changed	`http.method`	`http.request.method`
Nginx	Changed	`http.request_content_length`	`http.request.body.size`
Nginx	Changed	`http.target`	`url.path and url.query`
Nginx	Changed	`http.request.header.referrer`	`http.request.header.referer`
Cassandra	Changed	`code.lineno`	`code.line.number`
Elasticsearch	Changed	`db.elasticsearch.duration`	`db.result.duration_sum`
Elasticsearch	Changed	`db.operation`	`db.operation.name`
Elasticsearch	Changed	`db.elasticsearch.node`	`elasticsearch.node.name`
HAProxy	Changed	`net.peer.port`	`network.peer.port`
HAProxy	Changed	`net.peer.ip`	`network.peer.ip`
HAProxy	Changed	`net.host.ip`	`network.local.address`
HAProxy	Changed	`net.host.name`	`server.address`
HAProxy	Changed	`net.host.port`	`server.port`
HAProxy	Changed	`http.flavor`	`network.protocol.name` + `network.protocol.version`
HAProxy	Changed	`http.method`	`http.request.method`
HAProxy	Changed	`http.target`	`url.path and url.query`
HAProxy	Changed	`http.status_code`	`http.response.status_code`
Azure Services	Changed	`http.flavor`	`network.protocol.name` + `network.protocol.version`
Azure Services	Changed	`http.host`	`server.address`
Azure Services	Changed	`http.scheme`	`url.scheme`