Combined Agent Client Collector release notes for upgrades from Xanadu to Yokohama

yokohama Combined Product Files

Release

yokohama

ft:locale

en-US

ft:publication_title

yokohama Combined Product Files

ft:clusterId

delta3yx

bundleId

delta3yx

Combined Agent Client Collector release notes for upgrades from Xanadu to Yokohama

Release version: Yokohama

Updated July 20, 2026

10 minutes to read

Summarize

Summarized using AI

Summary of Combined Agent Client Collector release notes for upgrades from Xanadu to Yokohama

This document consolidates release notes for the Agent Client Collector (ACC) upgrades from the Xanadu to Yokohama versions, summarizing new features, changes, activation details, and other relevant information. It is designed to assist ServiceNow customers in preparing for and executing upgrades effectively, highlighting enhancements in security, functionality, and integration capabilities across releases.

Show full answer Show less

New Features

Security and Configuration Enhancements: The allow list can now be loaded solely from a configuration file to improve system security. Agent log levels can be configured remotely from the ServiceNow instance, and secure agent connections are supported via self-signed certificates added to the OS truststore.
Expanded Checks and Monitoring: Enhanced Linux and Windows checks provide more detailed system information. New Windows event and network port checks improve event collection and port availability monitoring. File attribute scanning and software identification on Linux and Windows devices aid in license management and security.
Kubernetes Visibility Agent Improvements: Starting in version 3.6.3, Informer pods can be remotely upgraded and configured from the ServiceNow instance, reducing dependence on Kubernetes administrators. Support for storing ServiceNow instance credentials in Microsoft Azure Vault (AKS) and Google Cloud Secret Manager (GKE) enhances credential security. Custom root certificate authorities can be mounted to enable secure Informer communication.
MID Server and Installation Updates: MID-less installation options conserve MID Server resources, allowing Agent Client Collector deployment without a MID Server. Proxy server support is available for MID-less installations. Manual upgrade procedures for macOS systems are introduced.
Operational Efficiency and Error Management: High-volume upgrades streamline mass Agent Client Collector deployments. Consolidated agent error views and the ability to create tasks for error resolution improve troubleshooting and operational management.
Additional Features: Multi-architecture Docker image support (arm64 and amd64) ensures compatibility across environments. Event creation can be blocked for non-existent entities to reduce noise. Notifications for agent key expiration enhance security maintenance.

Changes

The Windows event check was renamed and enhanced to gather more comprehensive data.
The Service Error Management plugin now depends on the ACC-F scoped app, which installs automatically with it.
New parameters allow finer control over checks running in shell execution mode, improving security and flexibility.
Agent Client Collector for Visibility has been renamed to Kubernetes Visibility Agent, with Cloud Native Operations (CNO) for Visibility extracted as a separate application, clarifying product structure.
Metric Explorer can now be used to explore and monitor metrics independently of Agent Client Collector Monitoring installation.

Activation and Requirements

Agent Client Collector requires activation of the Agent Client Collector Framework plugin (snagent) and the Agent Client Collector Monitoring plugin (snitmon) in instances where Event Management is installed. There are no new browser, localization, or accessibility requirements introduced between Xanadu and Yokohama.

Practical Implications for ServiceNow Customers

Upgrading to Yokohama enhances security by enabling secure agent connections and credential management through cloud vaults.
Expanded checks and monitoring capabilities provide deeper visibility into Linux, Windows, and Kubernetes environments, supporting better operational insights.
MID-less installation options reduce infrastructure complexity and resource usage.
Remote management of Kubernetes Informer pods streamlines administration and reduces dependency on Kubernetes administrators.
Error consolidation and task creation improve incident management workflows.
High-volume upgrade support facilitates efficient scaling across large deployments.

By understanding these improvements and changes, ServiceNow customers can plan and execute upgrades with confidence, leveraging new capabilities to enhance monitoring, security, and operational efficiency.

Consolidated page of all release notes for Agent Client Collector from Xanadu to Yokohama.

How to use this page

To help you prepare for your upgrade, we have combined the cross-family Agent Client Collector release notes onto one page. Read this summary of the new features, changes, and updated information for your product from Xanadu to Yokohama.

Tip:

If there were no updates for a release notes section in a certain family release, we included a short note for your reference. For example, if a product did not have any updates in Tokyo, the row says "No updates for this release."

Important information for upgrading Agent Client Collector to Yokohama

Before you upgrade to Yokohama, review these pre- and post-upgrade tasks and complete the tasks as needed.


Release	Release notes
Xanadu	No updates for this release.
Yokohama	No updates for this release.

New features

Between your current release family and Yokohama, new features were introduced for Agent Client Collector.


Release	Release notes
Xanadu	Load the allow list only from a configuration file Enhance system security by loading the allow list from the file specified in the allow-list parameter of the configuration file while ignoring the allow lists that are bundled with the plugins. Configure agent log level from the instance Configure the agent log level from the ServiceNow instance without having to access the acc.yml configuration file. Ensure secure agent connections Ensure that your agent connections are secure by adding a self-signed certificate to your operating system's truststore, which verifies that the certificate is authentic. Update existing assets Update your Agent Client Collector (ACC) plugins to the latest version by removing your existing plugins before reinstalling. Use expanded Linux and Windows checks Enable enhanced check functionality by using the expanded Linux and Windows checks provided with the system. Upgrade Agent Client Collector for Kubernetes – Visibility Informers remotely Starting in version 3.6.3, upgrade Informer pods in Kubernetes clusters remotely from the ServiceNow instance to avoid dependence on your Kubernetes admin. Override Informer parameters from the Instance Starting in version 3.6.3, control CNO for Visibility Informer execution parameters from the ServiceNow instance to avoid dependence on your Kubernetes admin. Store Instance credentials in Microsoft Azure Vault when Informer uses Azure Kubernetes Service (AKS) Starting in version 3.6.3, if your organization uses AKS, you can store the secret in the Microsoft Azure Vault. The Informer then pulls the ServiceNow credentials for accessing your instance from the Azure Vault. Enable Informer to connect to the instance using OAuth2.0 authorization Starting in version 3.6.3, the Informer can use OAuth2.0 authorization to connect to the ServiceNow instance for enhanced security. Enable expanded processing for the MID server on Network Interface Controllers (NICs) during keepalive operation Starting in version 3.6.3, benefit from enhanced stability when running a keepalive operation by using the enhanced MID Server capability to configure the number of Network Interface Controllers (NICs) that can be monitored by a keepalive operation. Upgrade Agent Client Collector manually on a macOS system Starting in version 3.6.3, run the consolidated upgrade procedure manually for the Agent Client Collector in a macOS environment. Configure the Dynatrace connector instance Starting in version 3.6.3, Event Management supports collecting raw metric data collection using the Dynatrace metric connector Consolidate agent errors Starting in version 4.1.0, view errors for all agents on the Agent Error Messages page. Additionally, you can view errors per individual agent by selecting the agent and selecting the ACC Error Messages tab . Use Linux commands to enable additional system capabilities beyond your permission level Starting in version 4.1.0, use Linux commands to grant enhanced permissions, which are enabled once the installation `.exe` file is executed. These enhanced capabilities are provided securely, ensuring that there is no security risk to your environment. Use the new Windows event check for enhanced event details Starting in version 3.12.0, use the new Windows event check to collect and filter Windows event logs. Use the network port check to determine port availability Starting in version 3.12.0, use the Network port check to create events for all ports of a specified host address, which indicates whether each port is available or in use. Enjoy multi-architecture support for docker image Starting in version 3.9.0 (Informer version 2.3.0), the docker image supports both arm64 and amd64 architectures. Upgrading from the previous image to the new one will not cause any disruptions. However, the new image requires more storage space in your image repository than the previous one. Change the Informer's extensibility settings from the instance Starting in version 3.9.0 (Informer version 2.3.0), update the Informer's extensibility configuration directly from the Instance using the Additional resources ConfigMap parameter. By providing a JSON map with keys such as `resources`, `mappings`, and `mappings_oob`, you can instruct Cloud Native Operations for Visibility to retrieve additional information. If one of these keys exists and the system finds a change, it patches the ConfigMap and restarts the Informer. View the OpenShift version in the Cluster version field on the Kubernetes Cluster CI Starting in version 3.9.0 (Informer version 2.3.0), see the OpenShift version and the Kubernetes Cluster version in one place. OpenShift operates on top of Kubernetes, so there's an OpenShift version and a Kubernetes Cluster version. By installing the Informer with the --set openShift=true flag, the system adds the OpenShift version number to the cluster_version field on the Kubernetes Cluster CI in addition to the Kubernetes Cluster version.
Yokohama	Scan your resource directories for file attributes Starting in version 3.13.0, run a check to receive information on the directory file's integrity, size, space, response time, and age. Conserve MID Server resources by using MID-less installation for Agent Client Collector Starting in version 3.6.5, conserve MID Server resources for more persistent features by using the MID-less installation when installing Agent Client Collector. With this installation, you don't need a MID Server in your system architecture. Create tasks to address Agent Client Collector errors Starting in version 4.3.0, create tasks to resolve errors relating to the Agent Client Collector. Tasks are assigned to personnel who investigate the underlying issues and work to resolve the errors. Use a proxy server with MID-less installation Starting in version 4.3.0, enable using a proxy server when installing Agent Client Collector without a MID Server. Discovery MSSQL server components Starting in version 1.3.0, enable discovery of MSSQL components by running Discovery as a local system user. Java certification Discovery through file-based discovery Starting in version 1.3.0, discover java file information using Agent Client Collector for Visibility - Content (ACC-VC) file based discovery. File based discovery locates java files that are installed on the system but not running, enabling retrieval of data used for licensing and auditing. Enable high volume upgrade of agents Starting in version 4.3.0, enhance efficiency by performing high-volume upgrade of large numbers of Agent Client Collector installations at once. Block event creation for non-existent entities Starting in version 3.13.0, block the creation of events and alerts if the process monitoring and log files don't exist in their indicated location. Control how check results are sent Starting in version 3.6.5, configure the circumstances when check results are sent. Configure and receive notifications of agent key expiration Starting in version 3.6.5, receive notifications that indicate when an agent registration key is expiring. Monitor network host availability Starting in version 4.1.0, use a new check to verify network host availability. Identify software running on Linux and Windows devices Starting in version 4.1.0, identify the software that is running on your Linux and Windows servers and devices by using file-based Discovery. File-based Discovery enables you to maintain the records of your software licenses and helps you to evaluate any threats from unwanted files. Store ServiceNow instance credentials in the Google Cloud Secret Manager when the Informer uses Google Kubernetes Engine (GKE) If your organization uses Google Kubernetes Engine (GKE) you can store the secret in Google Cloud Secret Manager. The Kubernetes Visibility Agent Informer can then pull the ServiceNow credentials for accessing your instance from the Google Cloud Secret Manager. Use a custom CA to enable the Informer to communicate with the ServiceNow instance when using a custom root CA Mount a custom certificate authority into the Kubernetes Visibility Agent Informer pod to enable the Informer to communicate with the instance when a custom root CA is used.

Changes

Between your current release family and Yokohama, some changes were made to existing Agent Client Collector features.


Release	Release notes
Xanadu	Use the updated Windows event check Starting in version 3.12.0, the Windows event check `os.windows.check-event-log` has been renamed `os.windows.check-event-log-count` and has enhanced data gathering capabilities. Updated plugin dependency Starting in version 4.1.0, the Service Error Management plugin is dependent on the ACC-F scoped app. The plugin gets installed automatically when the customer installs the ACC-F scoped app from the ServiceNow store. New allow list parameter for checks running in shell execution mode Starting in version 4.1.0, when running a check in with execution mode (Exec Mode) set to shell, add the allow_shell parameter and set it to true for the allow list entry corresponding to the check.
Yokohama	Explore metrics with Metric Explorer independent of Agent Client Collector Monitoring Starting in version 4.1.0, view and monitor metric data with Metric Explorer, even if you have not installed Agent Client Collector Monitoring. [Placeholder link text to key acc-visibility-landing-page] Starting in version 1.1.0, ACC for Visibility has been renamed as Kubernetes Visibility Agent and consists only of what is currently CNO for Visibility. The term CNO for Visibility has been deprecated and replaced with Kubernetes Visibility Agent. All other ACC for Visibility functions are now part of Agent Client Collector for Visibility - Content.

Removed

Between your current release family and Yokohama, some Agent Client Collector features or functionality were removed.


Release	Release notes
Xanadu	No updates for this release.
Yokohama	No updates for this release.

Deprecations

Between your current release family and Yokohama, some Agent Client Collector features or functionality were deprecated.


Release	Release notes
Xanadu	No updates for this release.
Yokohama	No updates for this release.

Activation information

Review information on how to activate Agent Client Collector.


Release	Release notes
Xanadu	Agent Client Collector is available with activation of the Agent Client Collector Framework plugin (sn_agent) and the Agent Client Collector Monitoring plugin (sn_itmon) in an instance on which Event Management is installed.
Yokohama	Agent Client Collector is available with activation of the Agent Client Collector Framework plugin (sn_agent) and the Agent Client Collector Monitoring plugin (sn_itmon) in an instance on which Event Management is installed.

Additional requirements

If any additional requirements were introduced or changed for Agent Client Collector we have noted them here.


Release	Release notes
Xanadu	No updates for this release.
Yokohama	No updates for this release.

Browser requirements

If any specific browser requirements were introduced or changed for Agent Client Collector we have noted them here.


Release	Release notes
Xanadu	No updates for this release.
Yokohama	No updates for this release.

Accessibility information

Review details on accessibility information for Agent Client Collector, such as specific requirements or compliance levels.


Release	Release notes
Xanadu	No updates for this release.
Yokohama	No updates for this release.

Localization information

If there are specific localization considerations for Agent Client Collector we have noted them here.


Release	Release notes
Xanadu	No updates for this release.
Yokohama	No updates for this release.

Highlight information

If there are specific highlight considerations for Agent Client Collector we have noted them here.


Release	Release notes
Xanadu	Ensure secure agent connections by adding a self-signed certificate. Enhance check functionality by using expanded Linux and Windows checks, enabling you to gather additional information on your Linux and Windows servers. Upgrade the Cloud Native Operations for Visibility Informer from the ServiceNow instance. Store Instance credentials in the Microsoft Azure Vault when Informer uses Azure Kubernetes Engine (AKS). Enjoy multi-architecture support for docker image. See Agent Client Collector for more information.
Yokohama	Agent Client Collector for Visibility: Starting in version 1.1.0, ACC for Visibility has been renamed Agent Client Collector for Visibility - Content. CNO for Visibility has been extracted from Agent Client Collector for Visibility - Content and is now a separate application. Store instance credentials in the Google Cloud Secret Manager when the Kubernetes Visibility Agent Informer uses Google Kubernetes Engine (GKE). Use a custom CA to enable Kubernetes Visibility Agent Informer to communicate with the instance when using a custom root Certificate Authority (CA). Configure Agent Client Collector without a MID Server by ßusing MID-less configuration. See Agent Client Collector for more information.