Skip to content

[DOCS-15231] Add 2.20.0 to Upgrade Worker guide #38580

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
maycmlee wants to merge 4 commits into
base: master
Choose a base branch
from
+28 −3
Open

[DOCS-15231] Add 2.20.0 to Upgrade Worker guide #38580

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
36f78bc
add 2.20.0
maycmlee Jul 29, 2026
a565e4e
valid tokens
maycmlee Jul 29, 2026
c47c6d7
remove extra line
maycmlee Jul 29, 2026
8857af6
Merge branch 'master' into may/upgrade-worker-guide-2.20.0
maycmlee Jul 30, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
31 changes: 28 additions & 3 deletions content/en/observability_pipelines/guide/upgrade_worker.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
title: Upgrade the Worker Guide
description: Learn about new features, enhancements, and fixes for Worker versions 2.7 to 2.19.
description: Learn about new features, enhancements, and fixes for Worker versions 2.7 to 2.20.
disable_toc: false
aliases:
- /observability_pipelines/guide/upgrade_worker_2_7/
Expand All @@ -14,6 +14,32 @@

This guide goes over how to upgrade to a specific Worker version and the updates for that version.

## Worker version 2.20.0

To upgrade to Worker version 2.20.0:

- Docker: Run the `docker pull` command for the [2.20.0 image][50].
- Kubernetes: See the [Helm chart][2] and [Upgrade the Worker][37].
- APT: Run the command `apt-get install observability-pipelines-worker=2.20.0`.
- RPM: Run the command `sudo yum install observability-pipelines-worker-2.20.0`.

Worker version 2.20.0 gives you access to the following:

#### New features

- The OpenTelemetry and Splunk HEC sources now support hot-reloading TLS certificates, so certificate rotations are applied without restarting the Worker.

Check warning on line 30 in content/en/observability_pipelines/guide/upgrade_worker.md

View workflow job for this annotation

GitHub Actions / vale

Datadog.tense 

Avoid temporal words like 'now'.

#### Enhancements

- The Split Array processor's performance has been improved.
- The HTTP/S Server source now uses a case-insensitive match for the header name field when you configure authentication tokens.

Check warning on line 35 in content/en/observability_pipelines/guide/upgrade_worker.md

View workflow job for this annotation

GitHub Actions / vale

Datadog.tense 

Avoid temporal words like 'now'.
- The Splunk HEC source now accepts an optional list of tokens for authenticating events.

Check warning on line 36 in content/en/observability_pipelines/guide/upgrade_worker.md

View workflow job for this annotation

GitHub Actions / vale

Datadog.tense 

Avoid temporal words like 'now'.

#### Fixes

- The Add Fields processor now increments the `component_errors_total` metric when it fails to update an event.

Check warning on line 40 in content/en/observability_pipelines/guide/upgrade_worker.md

View workflow job for this annotation

GitHub Actions / vale

Datadog.tense 

Avoid temporal words like 'now'.
- Fixed TLS certificate hostname verification issue for destinations with a configured server name, so that the server name is used for verification.

## Worker version 2.19.0

To upgrade to Worker version 2.19.0:
Expand Down Expand Up @@ -102,7 +128,6 @@

- The Generate Metrics processor's performance has been improved to reduce CPU overhead when using `group_by` tag labels.
- For the Custom Processor, the performance of `parse_regex_all` has been improved by reusing the compiled regex across invocations.
- The Splunk HEC source now supports the `enabled` field on `valid_tokens` entries. Disabled tokens are excluded from authentication and enrichment.

@brett0000FF brett0000FF Jul 31, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Waas this supposed to get deleted?

@maycmlee maycmlee Jul 31, 2026

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, thanks for checking! Both deleted valid_tokens entries are supposed to be deleted.


#### Fixes

Expand Down Expand Up @@ -150,7 +175,6 @@
#### New features

- [Databricks Zerobus][47] destination: Send log data to Databricks Unity Catalog tables using the Zerobus ingestion service. The Databricks destination supports OAuth 2.0 authentication, automatic schema fetching from Unity Catalog, and protobuf batch encoding.
- The Splunk HEC source now accepts an optional `valid_tokens` list for token-based authentication managed using environment variables or a configured secrets backend.
- The Splunk HEC source now supports enriching incoming log events using the VRL decoder.
- The Amazon S3 destination now supports Apache Parquet batch encoding with flexible schema definitions and configurable compression (Snappy, ZSTD, GZIP, LZ4, or none).
- For the Custom Processor:
Expand Down Expand Up @@ -658,3 +682,4 @@
[47]: /observability_pipelines/destinations/databricks/
[48]: https://hub.docker.com/r/datadog/observability-pipelines-worker/tags?name=2.18.0
[49]: https://hub.docker.com/r/datadog/observability-pipelines-worker/tags?name=2.19.0
[50]: https://hub.docker.com/r/datadog/observability-pipelines-worker/tags?name=2.20.0
Loading