Agent Enhancements

• Upgrades the following third-party libraries:

  Library	Previous Version	Upgraded Version
  jackson-core	2.17.1	2.21.1
  jackson-annotations	2.17.1	2.21
  jackson-databind	2.17.1	2.21.1
  jackson-dataformat-yaml	2.17.1	2.21.1
  argento-agent-version	26.1.1	26.2.2

• Includes bug fixes.

With this release:

• The automation script can read parameters from a configuration file, which makes it easier to manage complex installations. See プライベート合成エージェントのインストール.
• Chrome browser version 143 is supported. See ブラウザサポート.

• Kubernetes version 1.33.0 is supported. See 前提条件.

Java Agent now

• upgrades the Log4j third-party library from 2.17.1 to 2.25.3.

• supports prometheus-metric-drop-metrics node property. See prometheus-metric-drop-metrics.

• introduces the transition from an Alpine-based image to a Scratch-based image. For more information, see Support Advisory: Transition of Java Agent DockerHub Images from Alpine to Scratch Base .
• includes resolved issues. Agent Resolved Issues.

• Supports the following proxy configurations defined in controller-info.xml:
  • APPDYNAMICS_HTTP_PROXY_HOST
  • APPDYNAMICS_HTTP_PROXY_PORT
  • APPDYNAMICS_HTTP_PROXY_USER
  • APPDYNAMICS_HTTP_PROXY_PASSWORD_FILE
• Replaces Netty with OkHttp + junixSocket and includes the following third-party library upgrades:

  Library	Previous Version	Upgraded Version
  Apache Commons Lang	3.8.1	3.18.1
  Apache Commons BeanUtils	1.9.4	1.11.0
  Apache Commons Compress	1.20.0	1.26.0
  Apache Log4j Core	2.25.0	2.25.3
  Azul JRE17	17.62.18 (17.0.17)	17.64.16 (OpenJRE 17.0.18)
  Azul JRE11	11.84.18 (11.0.29)	11.86.20 (OpenJRE 11.0.30)
  Logback Core Module	1.5.18	1.5.19
  SnakeYAML	1.33	2.0
  Jetty :: Utility Servlets and Filters	9.4.46.v20220331	9.4.55.v20240627
  Protocol Buffers [Core]	2.5.0	3.25.5
  jackson-core	2.12.1	2.15.0
  Guava Java	31.1-jre	33.3.1-jre
  jackson-databind	2.12.1	2.12.7.1
  Hibernate Validator Engine	6.1.7.Final	6.2.0.Final
  Core :: Server	9.4.37.v20210219	9.4.57.v20241219
  Core :: IO	9.4.37.v20210219	9.4.40.v20210413
  Core :: HTTP	9.4.37.v20210219	12.0.12

• Includes bug fixes.

• CDM-10428

See Agent Resolved Issues.

This release includes:

• Microsoft Entra ID authentication support to connect to Azure Database for PostgreSQL. See Configure PostgreSQL Collectors.
• Database Agent can now publish upto 500,000 metrics to support high number of metrics for database file utilisation.
• support to use any CyberArk version. See Add Database Collectors.
• Database Agent 26.1 upgrades the MSSQL driver to mssql-jdbc-10.2.4.jre11.jar to comply with security standards. Hence, Database Agent now requires Java 11 - 17. See Software Requirements.
• the following third party component upgrade:

  Component	Previous Version	Upgraded Version
  MSSQL driver	9.4	10.2.4

  Note:

  In MSSQL driver 10.2.4 version, the default value of encrypt changes to true in the JDBC connection properties. Hence, if you want to configure a database collector without encryption, you must set the value of encrypt to false.

  In case you want to retain the value of encrypt as true in the JDBC connection properties,

  • you must also set the value of trustServerCertificate to true
  • or, set the following JVM args while starting the Database Agent:
    CODECopy

    -Djavax.net.ssl.trustStore=C:\example\storeName -Djavax.net.ssl.trustStorePassword=storePassword

    -Djavax.net.ssl.trustStore=C:\example\storeName
    -Djavax.net.ssl.trustStorePassword=storePassword

• resolved issues. See Agent Resolved Issues.

With this release:

• Chrome browser version 143 is supported. See Configure Synthetic Jobs.

• Hosted Synthetic Agent is available in the New York location. See Synthetic Hosted Agents.

See Agent Resolved Issues.

• Includes the following third-party library upgrades:

  Library	Previous Version	Upgraded Version
  urllib3	2.2.3	2.6.3
  Guava Java	31.1-jre	33.3.1-jre
  protobuf	4.21.6	4.25.8
  curl	8.16.0	8.17.0

• Includes bug fixes.

See Agent Resolved Issues.

• AWS version 30

• Java versions 17 and 21

Your browser applications may use GraphQL to efficiently fetch data. Starting with this release, the Controller enables monitoring of GraphQL operations on your browser applications. In the Controller UI, requests will display the path appended with the GraphQL operation name, for example, /api/graphql/getAllPosts.

To use custom headers, update and inject the JavaScript Agent script to enable GraphQL monitoring. For detailed instructions, see ブラウザアプリケーションでの GraphQL オペレーションのモニター.