OneAgent September 2026: what to plan before updating your fleet

OneAgent September 2026 (1.347): Java 23 dropped, Java 27, kernel 5.8, Cosign, non-root container. The plan to update your fleet without surprises.
OneAgent septembre 2026 : les nouveautés à planifier avant la mise à jour du parc

OneAgent September 2026: version 1.347 began its rollout on 30 September 2026, according to the official OneAgent release notes page (updated 8 October 2026). It lists 20 feature updates, 3 breaking changes and a batch of fixes. Before you update a fleet, sort out what touches your hosts, runtimes and clusters.

For an SRE the goal is simple: a version bump must not make a process vanish from monitoring or fire an unexpected alert. This article reads the release notes, derives an update plan and suggests checks before and after. It applies to Dynatrace SaaS; on Managed, the available version depends on your cluster.

A note on honesty: span.observer has not deployed version 1.347. The facts come from the release notes page; the order of the steps is our own analysis, to adapt to your fleet.

OneAgent September 2026: what version 1.347 contains

The page gives a single date: the start of the rollout, 30 September 2026. It gives no per-feature date and no detailed prerequisites. Features are grouped by area.

Table built from the OneAgent 1.347 release notes: Java 27, CentOS Stream 10, Rust and Tokio, short-lived processes, Kafka Binder, non-root container, CPU quota SFM event, and the breaking changes
  • Application Observability: tracing for AWS Lambda with Spring Cloud Functions, the Azure SDK Blob Storage client for Java, OpenFeature in Python, Microsoft Foundry in the Python agent, Azure Functions for Python on the Premium plan for Linux, the Azure CosmosDB client for Node.js, and the Spring Cloud Stream Kafka Binder on the consumer side (single and batch modes). For logs, the default set of JSON severity keys changes.
  • Digital Experience (RUM Web): Traffic Control behaviour, the source of user actions and new triggers.
  • Hosts: Java 27 fully monitored, CentOS Stream 10, Rust and Tokio detection, better detection of short-lived processes.
  • OneAgent platform: non-root container in classic full stack mode, monitoring of Kafka Binder consumers, an SFM event for CPU quota exhaustion.

OS and runtime prerequisites to check

Start with what can remove monitoring. According to the page, OneAgent supports LTS Java versions plus the last four versions (24, 25, 26 and 27). Java 23 is therefore no longer monitored from 1.347. You have two options: move to Java 24 or later, or stay on OneAgent 1.345 or earlier for the Java 23 services.

Next, operating systems. CentOS Stream 10 is now supported. Detection of short-lived processes improves on Linux distributions with kernel 5.8 or later, across several CPUs and on ARM64. Check your hosts’ kernels to see where the effect will show.

Finally, the Spring Cloud Stream Kafka Binder. Single mode covers a plain java.util.function.Consumer. Batch mode requires spring.cloud.stream.bindings.<name>.consumer.batch-mode: true. List your consumers before updating: new traces will appear on those services.

Breaking changes and behaviour changes

  1. RUM user actions: an action is always triggered by a user interaction. Soft navigations in quick succession merge into the same action, and a drop, change or Enter keypress can also create one. Dashboards that count actions may shift.
  2. Composefs is no longer monitored: this read-only file system always showed 100% usage and caused false alerts. Review your disk alerts.
  3. Cosign: from 1 December 2026, only Cosign is supported to verify the signature of the dynatrace/oneagent image. Docker Content Trust is not. If your CI/CD uses it, plan the switch before that date.

Kubernetes: non-root container and Log module quota

With Dynatrace Operator in classic full stack mode, the OneAgent container now runs as a non-root user. Review your pod security policies and admission rules if they constrain users. To revisit the deployment, see our article on Dynatrace Operator and Kubernetes alerts on nodes, pods and quotas.

Another change: the Log module’s CPU usage is limited by OS Agent and Watchdog. When the quota is reached, the module is throttled and a new SFM event, resource.cpu_quota_exhausted, is sent. A host that receives it may delay its logs: treat it as a signal, not noise.

Fleet update plan

  1. Inventory: OneAgent versions, kernels, Java versions, Kafka Binder consumers. For Linux installation, see OneAgent on Linux.
  2. Isolate blockers: Java 23 services, a Docker Content Trust signing chain, composefs alerts.
  3. Pilot: a representative group of hosts, then a non-critical cluster.
  4. Extend in waves, as for an MDM-managed fleet: observe before continuing.
List of four check commands: oneagentctl --version, uname -r, java -version and kubectl get pods -n dynatrace, each preceded by a comment

The oneagentctl documentation says the --version parameter displays the OneAgent version (./oneagentctl --version on Linux, from the OneAgent directory).

How to check that it works

  • Before: note each host’s version, kernel and Java version, and the open alerts.
  • After: run ./oneagentctl --version again, check that Java 24 to 27 processes remain visible, that Operator pods are ready and that the number of disk alerts is stable.
  • Search for the resource.cpu_quota_exhausted event on hosts that produce many logs.

Best practices

  • Do not update the whole fleet on the same day: the official rollout itself spreads over several weeks.
  • Keep the list of Java 23 services with an owner and a migration date.
  • Reread the original release notes before each wave: the page can be updated.

Frequently asked questions

When was OneAgent 1.347 released?

The release notes show a rollout start on 30 September 2026. They give no per-feature date.

Is Java 23 still monitored?

No, not from 1.347. Move to Java 24 or later, or stay on OneAgent 1.345 or earlier.

What does the non-root container change?

With the Operator in classic full stack mode, the OneAgent container runs as a non-root user. Check your security policies before updating.

Conclusion

Version 1.347 mostly asks you to check Java 23, the Linux kernel, Cosign signatures and pod policies. Sources: OneAgent 1.347 release notes and oneagentctl documentation.

span.observer is an independent community blog, not affiliated with Dynatrace LLC. Dynatrace is a trademark of Dynatrace LLC. Versions and dates change: check them in the official documentation for your environment.

Total
0
Shares
Leave a Reply

Your email address will not be published. Required fields are marked *

Previous Post
Faille PHP2Shell : détecter et superviser son parc

PHP2Shell vulnerability: detect and monitor your estate

Next Post
Mise à jour Dynatrace Operator 1.11 : correctifs 1.11.1, 1.10.4 et 1.9.2

Dynatrace Operator update 1.11: security fixes 1.11.1, 1.10.4 and 1.9.2

Related Posts