This release supports:

• Chrome browser version 137. See Configure Synthetic Jobs.
• enabling performance logs on the Chrome browser. See:

  • Set up PSA in Docker Engine

  • Set up PSA in Red Hat OpenShift

  • Set up PSA in Amazon EKS

  • Set up PSA in Minikube

  • Set up PSA in Azure AKS

This release:

• introduces the resources parameter within the instrumentation rules to specify the init container resources. See Auto-Instrumentation Configuration.
• includes support for RedHat OpenShift 4.17 (AWS).
• provides an option to use the nodeSelector parameter in values.yaml file for metrics server. See Metrics Server Config at Install the Cluster Agent and Install the Cluster Agent with Helm Charts.
• updates the Cluster Agent to Golang 1.24.3.
• updates the following libraries for AppDynamics Operator:

  Library	Previous Version	Upgraded Version
  testify	1.8.4	1.9.0
  apimachinery	0.29.2	0.31.1
  protobuf	1.34.1	1.34.2
  client-go	0.29.2	0.31.0
  net	0.34.0	0.36.0
  xxhash	2.2.0	2.3.0
  go-spew	1.1.1	1.1.2
  json-patch/v5	5.8.0	5.9.0
  swag	0.22.3	0.22.4

• updates the following library for Cluster Agent:

  Library	Previous Version	Upgraded Version
  viper	1.19.0	1.20.1
  mock	0.5.0	0.5.2
  net	0.37.0	0.40.0
  protobuf	1.36.5	1.36.6
  apimachinery	0.32.2	0.33.0
  client-go	0.32.2	0.33.0

For bug fix, see Agent Resolved Issues.

Docker Hub

• Supports OpenShift clusters.
• Supports up to 75 Java Agents on a single m4.4xlarge node in a containerized environment.

  The number of supported Java Agents depends on various factors, and the mentioned limit of 75 is based on the instrumentation of a simple Java application.

• Supports flowgroup_limit configuration. The details to use this configuration is mentioned in the Why do I see the error, "ERROR ip_flowgrp_lookup: flowgrp alloc failed"? FAQ.
• Fixes bugs. See Agent Resolved Issues.
• Upgrades the following third-party libraries:

  Library	Previous Version	Upgraded Version
  curl	8.11.1	8.13.0
  protobuf	4.21.0	4.21.6

You can now:

• install supported agents using the smartagentctlbinary. See Install Supported Agents Using smartagentctl.
• install the required supported agents on a remote host. You can also automate the installation on multiple remote Linux or Windows hosts by using remote.yaml file. See Install Supported Agents in Remote Host.
• If you do not specify start_as_process in the custom configuration details for Machine Agent installation, Smart agent runs Machine Agent based on the following permissions:
  • root user: Machine Agent runs as a service
  • non-root user: Machine Agent runs as a process. You cannot run the agent as a service with this permission.See Machine Agent Custom Configuration.

For bug fix, see Agent Resolved Issues.

For known issue, see Agent Known Issues.