Red Hat Summit Red Hat SummitSupportConsoleDevelopersStart a trialContact

Release notes for the Red Hat build of OpenTelemetry

Red Hat build of OpenTelemetry 3.9

What is new and what has changed with this release

Red Hat OpenShift Documentation Team

Abstract

Learn about the general availability and Technology Preview updates in terms of features and bugs.

1.1. About this release
Copy link

Red Hat build of OpenTelemetry 3.9 is provided through the Red Hat build of OpenTelemetry Operator 0.144.0 and based on the open source OpenTelemetry release 0.144.0.

Note

Only supported features are documented. Undocumented features are currently unsupported. If you need assistance with a feature, contact Red Hat’s support.

1.2. New features and enhancements
Copy link

The Red Hat build of OpenTelemetry 3.9 release adds the following features and enhancements.

Metric Start Time Processor

This update introduces the Metric Start Time Processor. You can use it to add start times to cumulative metrics after the Prometheus Receiver and benefit as follows:

  • Improve historical data analysis by adding start time data for cumulative values.
  • Enable the back end to accurately calculate request rates per minute.
  • Enable threshold-based alerts.
General availability of Collector components

The following components, available as a Technology Preview before this update, are fully supported from version 3.9:

  • Kubernetes Events Receiver
  • Filter Processor
  • Transform Processor
  • Prometheus Exporter
  • Prometheus Remote Write Exporter
  • Target Allocator
Upgrade to UBI 9
This release upgrades the Red Hat Universal Base Image (UBI) to version 9.
Environment variables for Operator configuration
This update adds support for overriding the Operator configuration by using environment variables.
Prometheus scrape classes in Target Allocator
This update adds support for Prometheus scrape classes in the Target Allocator component.
Configuration change for Kafka Receiver and Kafka Exporter
This update changes the configuration of the Kafka Receiver and Kafka Exporter in the OpenTelemetry Collector. The top-level encoding field is now deprecated. With this update, you must set encoding per signal type under logs, metrics, and traces. Use the raw encoding for logs only, because setting it at the top level and applying it to all signal types causes a startup failure. For examples, see "Kafka Receiver" and "Kafka Exporter".

1.3. Deprecated features
Copy link

The Red Hat build of OpenTelemetry 3.9 release deprecates the following features.

Deprecated name for OTLP gRPC Exporter
The otlp name for the OTLP gRPC Exporter in the OpenTelemetry Collector custom resource (CR) is deprecated. Use the otlp_grpc name instead. The otlp name is deprecated and planned for removal in a future release.
Deprecated name for OTLP HTTP Exporter
The otlphttp name for the OTLP HTTP Exporter in the OpenTelemetry Collector custom resource (CR) is deprecated. Use the otlp_http name instead. The otlphttp name is deprecated and planned for removal in a future release.

1.4. Removed features
Copy link

OpenCensus Receiver is removed
The deprecated OpenCensus Receiver, which provided backward compatibility with the OpenCensus project for easier migration of instrumented codebases, is removed and is no longer supported. You can use the OpenTelemetry Protocol (OTLP) and OTLP Receiver instead.

1.5. Known issues
Copy link

No metrics in Host Metrics Receiver scraper

The filesystem scraper does not produce the system.filesystem.inodes.usage and system.filesystem.usage metrics in the Host Metrics Receiver after upgrading from Collector version 0.142.0 to 0.143.0 or later. No known workaround exists.

TRACING-5963

1.6. Fixed issues
Copy link

The Red Hat build of OpenTelemetry 3.9 release fixes the following issues.

Fixed NGINX and Apache instrumentation init containers
Before this update, the NGINX and Apache instrumentation init containers were created by cloning the main container’s configuration. As a consequence, there were issues with cloned liveness and readiness probes. With this release, the NGINX and Apache instrumentation init containers are defined independently, rather than inheriting inappropriate probe settings from the main container. As a result, issues with cloned liveness and readiness probes no longer occur.
Fixed ServiceMonitor resource for Operator metrics
Before this update, the ServiceMonitor resource for the Operator metrics was not created due to a bug. With this release, the ServiceMonitor resource for the Operator metrics is created.
CVE-2025-61726

Before this update, a flaw existed in the net/url package in the Go standard library. As a consequence, a denial-of-service HTTP request with a massive number of query parameters could cause the application to consume an excessive amount of memory and eventually become unresponsive. This release eliminates this flaw.

CVE-2025-61726

Note

Some linked Jira tickets are accessible only with Red Hat credentials.

1.7. Getting support
Copy link

If you experience difficulty with a procedure described in this documentation, or with OpenShift Container Platform in general, visit the Red Hat Customer Portal.

From the Customer Portal, you can:

  • Search or browse through the Red Hat Knowledgebase of articles and solutions relating to Red Hat products.
  • Submit a support case to Red Hat Support.
  • Access other product documentation.

To identify issues with your cluster, you can use Red Hat OpenShift Lightspeed in OpenShift Cluster Manager. Red Hat OpenShift Lightspeed provides details about issues and, if available, information on how to solve a problem.

If you have a suggestion for improving this documentation or have found an error, submit a Jira issue for the most relevant documentation component. Please provide specific details, such as the section name and OpenShift Container Platform version.

Legal Notice
Copy link

Copyright © Red Hat.
Except as otherwise noted below, the text of and illustrations in this documentation are licensed by Red Hat under the Creative Commons Attribution–Share Alike 3.0 Unported license . If you distribute this document or an adaptation of it, you must provide the URL for the original version.
Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
Red Hat, the Red Hat logo, JBoss, Hibernate, and RHCE are trademarks or registered trademarks of Red Hat, LLC. or its subsidiaries in the United States and other countries.
Linux® is the registered trademark of Linus Torvalds in the United States and other countries.
XFS is a trademark or registered trademark of Hewlett Packard Enterprise Development LP or its subsidiaries in the United States and other countries.
The OpenStack® Word Mark and OpenStack logo are trademarks or registered trademarks of the Linux Foundation, used under license.
All other trademarks are the property of their respective owners.
Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust. Explore our recent updates.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Theme

© 2026 Red HatBack to top