Chapter 1. Release notes for the Red Hat build of OpenTelemetry 3.8
1.1. About this release Copy linkLink copied to clipboard!
Red Hat build of OpenTelemetry 3.8 is provided through the Red Hat build of OpenTelemetry Operator 0.140.0 and based on the open source OpenTelemetry release 0.140.0.
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 linkLink copied to clipboard!
- Operator network policy improvements
- With this update, the Operator network policy for the Kubernetes API server becomes more specific and uses the API Server namespace and pod labels.
- Filelog Receiver GA
- With this update, the Filelog Receiver, which was a Technology Preview feature, reaches general availability (GA). This receiver tails and parses logs from files. You can use it, as a sidecar container or DaemonSet, to collect logs from pod filesystems.
1.3. Technology Preview features Copy linkLink copied to clipboard!
- Google Cloud Exporter (Technology Preview)
- This release introduces the Google Cloud Exporter as a Technology Preview feature for the Collector of the Red Hat build of OpenTelemetry. You can use the Google Cloud Exporter to export metrics, logs, and traces to Google Cloud’s observability services: Google Cloud Monitoring, Google Cloud Logging, and Google Cloud Trace.
- Profile signal (Technology Preview)
- This release introduces support for the Profile signal as a Technology Preview feature for receiving, processing, and exporting data in the Profile signal format. The Profile signal is a new observability data format for capturing the low-level performance of application code.
- Prometheus Remote Write Receiver (Technology Preview)
- This release introduces the Prometheus Remote Write Receiver as a Technology Preview feature for the Collector of the Red Hat build of OpenTelemetry. You can use the Prometheus Remote Write Receiver to export metrics from the Prometheus server.
Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.
For more information about the support scope of Red Hat Technology Preview features, see Technology Preview Features Support Scope.
1.4. Fixed issues Copy linkLink copied to clipboard!
- Fixed BearerTokenAuth Extension errors
Before this update, the BearerTokenAuth Extension might log errors when the service account token was refreshed. With this update, the extension correctly handles token file refresh without producing errors.
- Fixed errors from the CA Injector of cert-manager
Before this update, the CA Injector of cert-manager was logging errors related to fetching the certificates for the Red Hat build of OpenTelemetry Operator. With this update, the OpenTelemetry Collector no longer relies on cert-manager, preventing unnecessary error logs.
- Fixed short-term token authentication for the AWS Cloud Watch Exporter
Before this update, the AWS Cloud Watch Exporter ignored short-term token authentication using an Amazon Resource Name (ARN). With this update, the exporter correctly handles short-term token authentication.
Some linked Jira tickets are accessible only with Red Hat credentials.
1.5. Getting support Copy linkLink copied to clipboard!
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 Lightspeed in OpenShift Cluster Manager. Red Hat 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.