Combined Agent Client Collector release notes for upgrades from Washington DC to Australia
On this page
Combined Agent Client Collector release notes for upgrades from Washington DC to Australia
Consolidated page of all release notes for Agent Client Collector from Washington DC to Australia.
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 Washington DC to Australia.
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 Australia
Before you upgrade to Australia, review these pre- and post-upgrade tasks and complete the tasks as needed.
<table class=“custom-rows”><thead><tr><th class=“filter”>
Release
</th><th>
Release notes
</th></tr></thead><tbody><tr><td>
Washington DC
</td><td>
No updates for this release.
</td></tr><tr><td>
Xanadu
</td><td>
No updates for this release.
</td></tr><tr><td>
Yokohama
</td><td>
No updates for this release.
</td></tr><tr><td>
Zurich
</td><td>
No updates for this release.
</td></tr><tr><td>
Australia
</td><td>
No updates for this release.
</td></tr></tbody> </table>## New features
Between your current release family and Australia, new features were introduced for Agent Client Collector.
<table class=“custom-rows”><thead><tr><th class=“filter”>
Release
</th><th>
Release notes
</th></tr></thead><tbody><tr><td>
Washington DC
</td><td>
Use agent-less System Center Operations Manager (SCOM) connectors for high-performance SCOM metric integration.
Run application patterns through the Agent Client Collector. Application patterns enable discovering details about applications running on an agent’s host.
Monitor the behavior of the Agent Client Collector application with the enhanced Policy Calculation and Framework Configuration system properties, including the enhancements to agent Discovery, automatic MID Server selection, and error message logging.
Provide the enhanced data collection in the Agent Client Collector application by communicating the instance data with the agent. The configuration data files are also sent to the agent’s associated MID Server.
Monitor MongoDB resources with additional metrics that relate to the metadata, memory, and disk space.
Continuously discover the resources in your Kubernetes clusters in Agent Client Collector for Visibility by using Cloud Native Operations (CNO) for Visibility. CNO for Visibility promptly reports changes in the resources to the instance and updates the Configuration Management Database (CMDB).
Retrieve the high-performance metrics for virtual resources in the cloud by using VMware.
Starting in version 3.6.2, configure the Cloud Native Operations for Visibility Informer to pull additional resources from Kubernetes clusters into the Configuration Management Database (CMDB), besides the resources it sends to the database by default.
Starting in version 3.6.2, configure if you want the CNO for Visibility Informer to create a cmdb_ci_linux_server CI for each Kubernetes node. By default, the Informer creates a cmdb_ci_linux_server CI for every Kubernetes node. If this CI is redundant or interferes with other flows in your organization, you can set the associated configuration parameter to false.
Starting in version 3.6.2, define include and exclude lists of Labels and Annotations in Kubernetes resources that the CNO for Visibility Informer pulls into the CMDB.
Starting in version 3.6.2, make the CNO for Visibility Informer populate the field in the cmdb_ci_kubernetes_cluster CI that shows the Kubernetes cluster version.
Starting in version 3.6.2, CNO for Visibility enables you to add custom Labels and Annotations to all your resources deployed in the Kubernetes cluster.
Starting in version 3.5.1, enhance your system’s security by verifying checks only with the allow-list from your global configurations. An allow-list from installed plugins is not used.
Starting in version 3.5.1, enhance security by adding a self-signed certificate to your OS’s trust store.
Starting in version 3.5.1, remove an agent’s plugin files by selecting Clear Assets on the UI, instead of removing the plugins manually.
Starting in version 3.5.1, Agent Client Collector supports additional Linux and Windows checks.
</td></tr><tr><td>
Xanadu
</td><td>
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 the agent log level from the ServiceNow instance without having to access the acc.yml configuration file.
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 your Agent Client Collector (ACC) plugins to the latest version by removing your existing plugins before reinstalling.
Enable enhanced check functionality by using the expanded Linux and Windows checks provided with the system.
Starting in version 3.6.3, upgrade Informer pods in Kubernetes clusters remotely from the ServiceNow instance to avoid dependence on your Kubernetes admin.
Starting in version 3.6.3, control CNO for Visibility Informer execution parameters from the ServiceNow instance to avoid dependence on your Kubernetes admin.
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.
Starting in version 3.6.3, the Informer can use OAuth2.0 authorization to connect to the ServiceNow instance for enhanced security.
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.
Starting in version 3.6.3, run the consolidated upgrade procedure manually for the Agent Client Collector in a macOS environment.
Starting in version 3.6.3, Event Management supports collecting raw metric data collection using the Dynatrace metric connector
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 .
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.
Starting in version 3.12.0, use the new Windows event check to collect and filter Windows event logs.
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.
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.
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.
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.
</td></tr><tr><td>
Yokohama
</td><td>
Starting in version 3.13.0, run a check to receive information on the directory file’s integrity, size, space, response time, and age.
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.
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.
Starting in version 4.3.0, enable using a proxy server when installing Agent Client Collector without a MID Server.
Starting in version 1.3.0, enable discovery of MSSQL components by running Discovery as a local system user.
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.
Starting in version 4.3.0, enhance efficiency by performing high-volume upgrade of large numbers of Agent Client Collector installations at once.
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.
Starting in version 3.6.5, configure the circumstances when check results are sent.
Starting in version 3.6.5, receive notifications that indicate when an agent registration key is expiring.
Starting in version 4.1.0, use a new check to verify network host availability.
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.
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.
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.
</td></tr><tr><td>
Zurich
</td><td>
Agent Client Collector Framework
Starting in version 6.0.0, perform selective and high-volume upgrades on ACC agents when not using a MID Server by using products such as DEX and ACC-VC.
Starting in version 6.0.0, verify that an agent is functioning properly by performing a self-test on the agent.
Starting in version 6.0.0, view a list of agents and their statuses on the ACC Workspace dashboard.
Starting in version 6.0.0, benefit from enhanced debug logging by sending all debug statements to a log file
Starting in version 5.0, configure a schedule by which to rotate Agent Client Collector certificates which enable communication between agents and ITOM Cloud Services. Rotating certificates ensures that when a certificate expires, a new certificate is in place.
Starting in version 5.0, upgrade large numbers of Agent Client Collector agents at a time that are running on macOS. This extends the existing high-volume upgrade capabilities available for Windows and Linux in the 4.3.0 release.
Starting in version 5.0, the IMDSv2 endpoint for metadata discovery is invoked when using Agent Client Collector in an AWS EC2 environment.
Starting in version 5.0, view errors that occur before or after the registration process when Agent Client Collector connects to the instance. This provides enhanced debugging capabilities by enabling you to view issues in the instance, without requiring direct access to the agent logs.
Starting in version 5.0, disable only those checks that are causing high CPU usage while in CPU protection mode. It is still possible to disable all checks and completely stop data collection while in CPU protection mode.
In a Windows environment, Agent Client Collector has improved the accuracy of how check CPU usage is monitored.
Starting in version 5.0, configuration data files have a maximum size of 10MB.
Starting in version 5.0, enable easier connection of Agent Client Collector to a proxy server by using a proxy auto-configuration (PAC) file.
Agent Client Collector Monitoring
Starting in version 3.15.0, GCP checks provide added support to configure metrics through a configuration file in JSON format.
Starting in version 3.15.0, monitor Linux events using Linux event checks.
Agent Client Collector for Visibility - Content
Starting in version 1.5.0, use ACC-VC to discover MSSQL components in your environment.
Starting in version 1.5.0, gather software information with ACC-VC using software identification (SWID) tags on an agent and a ServiceNow® instance.
Starting in version 1.3.0, use the Agent Client Collector for Visibility - Content to discover TLS/SSL certificates used by the ports running on the server’s configuration items (CIs). Certificate Inventory and Management uses the certificate data to manage the TLS/SSL certificate life cycle.
Starting in version 1.3.0, use File-based Discovery in a macOS environment.
Starting in version 1.3.0, collect data more efficiently by invoking non-osqueryd data collection.
</td></tr><tr><td>
Australia
</td><td>
No updates for this release.
</td></tr></tbody> </table>## Changes
Between your current release family and Australia, some changes were made to existing Agent Client Collector features.
<table class=“custom-rows”><thead><tr><th class=“filter”>
Release
</th><th>
Release notes
</th></tr></thead><tbody><tr><td>
Washington DC
</td><td>
-
Automatic MID Server selection
-
Receive additional MID Server information to be used as alternative points of communication during automatic MID Server selection.
-
Automatic MID Server selection is off by default.
-
Configure manual thresholds for generating metric alerts using the Metric Rules feature instead of the Static Thresholds UI.
Use Azure checks and policies to retrieve high-performance metrics for the virtual resources in the cloud.
-
Monitoring Technology Dashboards
-
Filter metrics by the selected configuration item (CI) in the AWS and GCP Monitoring Technology Dashboards.
-
Use the updated Monitoring Technology Dashboard for Azure. The dashboard contains additional tabs which provide more information on your Azure infrastructure.
-
Viewing Monitoring Technology Dashboards requires the dashboard_admin role in addition to the existing agent_client_collector_admin role.
-
Delete the agent records that have been disconnected or inactive for more than 30 days by using the Autoflush form.
SNMP checks work by default with v3.
Starting in version 3.5.1, configure the agent log level through the ServiceNow® instance, without needing to access the acc.yml configuration file.
Starting in version 3.5.1, utilize the updated minimum host system requirements when installing Agent Client Collector Monitoring.
Starting in version 3.5.1, import global.ACCInstanceScanUtil to enable using the Instance scan feature, as described in the KB1630132 knowledge base article.
</td></tr><tr><td>
Xanadu
</td><td>
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.
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.
</td></tr><tr><td>
Yokohama
</td><td>
Starting in version 4.1.0, view and monitor metric data with Metric Explorer, even if you have not installed Agent Client Collector Monitoring.
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.
</td></tr><tr><td>
Zurich
</td><td>
No updates for this release.
</td></tr><tr><td>
Australia
</td><td>
No updates for this release.
</td></tr></tbody> </table>## Removed
Between your current release family and Australia, some Agent Client Collector features or functionality were removed.
<table class=“custom-rows”><thead><tr><th class=“filter”>
Release
</th><th>
Release notes
</th></tr></thead><tbody><tr><td>
Washington DC
</td><td>
No updates for this release.
</td></tr><tr><td>
Xanadu
</td><td>
No updates for this release.
</td></tr><tr><td>
Yokohama
</td><td>
No updates for this release.
</td></tr><tr><td>
Zurich
</td><td>
No updates for this release.
</td></tr><tr><td>
Australia
</td><td>
No updates for this release.
</td></tr></tbody> </table>## Deprecations
Between your current release family and Australia, some Agent Client Collector features or functionality were deprecated.
<table class=“custom-rows”><thead><tr><th class=“filter”>
Release
</th><th>
Release notes
</th></tr></thead><tbody><tr><td>
Washington DC
</td><td>
No updates for this release.
</td></tr><tr><td>
Xanadu
</td><td>
No updates for this release.
</td></tr><tr><td>
Yokohama
</td><td>
No updates for this release.
</td></tr><tr><td>
Zurich
</td><td>
Agent Client Collector Security Incident Response is no longer supported. For details on replacement options, see the Deprecation guidance for Agent Client Collector Security Incident Response [KB2249776] article in the Now Support Knowledge Base.
</td></tr><tr><td>
Australia
</td><td>
No updates for this release.
</td></tr></tbody> </table>## Activation information
Review information on how to activate Agent Client Collector.
<table class=“custom-rows”><thead><tr><th class=“filter”>
Release
</th><th>
Release notes
</th></tr></thead><tbody><tr><td>
Washington DC
</td><td>
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.
</td></tr><tr><td>
Xanadu
</td><td>
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.
</td></tr><tr><td>
Yokohama
</td><td>
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.
</td></tr><tr><td>
Zurich
</td><td>
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.
</td></tr><tr><td>
Australia
</td><td>
No updates for this release.
</td></tr></tbody> </table>## Additional requirements
If any additional requirements were introduced or changed for Agent Client Collector we have noted them here.
<table class=“custom-rows”><thead><tr><th class=“filter”>
Release
</th><th>
Release notes
</th></tr></thead><tbody><tr><td>
Washington DC
</td><td>
No updates for this release.
</td></tr><tr><td>
Xanadu
</td><td>
No updates for this release.
</td></tr><tr><td>
Yokohama
</td><td>
No updates for this release.
</td></tr><tr><td>
Zurich
</td><td>
No updates for this release.
</td></tr><tr><td>
Australia
</td><td>
No updates for this release.
</td></tr></tbody> </table>## Browser requirements
If any specific browser requirements were introduced or changed for Agent Client Collector we have noted them here.
<table class=“custom-rows”><thead><tr><th class=“filter”>
Release
</th><th>
Release notes
</th></tr></thead><tbody><tr><td>
Washington DC
</td><td>
No updates for this release.
</td></tr><tr><td>
Xanadu
</td><td>
No updates for this release.
</td></tr><tr><td>
Yokohama
</td><td>
No updates for this release.
</td></tr><tr><td>
Zurich
</td><td>
No updates for this release.
</td></tr><tr><td>
Australia
</td><td>
No updates for this release.
</td></tr></tbody> </table>## Accessibility information
Review details on accessibility information for Agent Client Collector, such as specific requirements or compliance levels.
<table class=“custom-rows”><thead><tr><th class=“filter”>
Release
</th><th>
Release notes
</th></tr></thead><tbody><tr><td>
Washington DC
</td><td>
No updates for this release.
</td></tr><tr><td>
Xanadu
</td><td>
No updates for this release.
</td></tr><tr><td>
Yokohama
</td><td>
No updates for this release.
</td></tr><tr><td>
Zurich
</td><td>
No updates for this release.
</td></tr><tr><td>
Australia
</td><td>
No updates for this release.
</td></tr></tbody> </table>## Localization information
If there are specific localization considerations for Agent Client Collector we have noted them here.
<table class=“custom-rows”><thead><tr><th class=“filter”>
Release
</th><th>
Release notes
</th></tr></thead><tbody><tr><td>
Washington DC
</td><td>
No updates for this release.
</td></tr><tr><td>
Xanadu
</td><td>
No updates for this release.
</td></tr><tr><td>
Yokohama
</td><td>
No updates for this release.
</td></tr><tr><td>
Zurich
</td><td>
No updates for this release.
</td></tr><tr><td>
Australia
</td><td>
No updates for this release.
</td></tr></tbody> </table>## Highlight information
If there are specific highlight considerations for Agent Client Collector we have noted them here.
<table class=“custom-rows”><thead><tr><th class=“filter”>
Release
</th><th>
Release notes
</th></tr></thead><tbody><tr><td>
Washington DC
</td><td>
-
Use the enhanced system properties for agent Discovery, automatic MID Server selection, and error message logging to monitor the Agent Client Collector policies and framework configuration.
-
Use the configuration data files to provide the data from an instance directly to an agent.
-
Retrieve the metrics for Azure policies in the cloud.
See Agent Client Collector for more information.
</td></tr><tr><td>
Xanadu
</td><td>
-
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.
</td></tr><tr><td>
Yokohama
</td><td>
-
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.
</td></tr><tr><td>
Zurich
</td><td>
-
Discover TLS/SSL certificates using Agent Client Collector for Visibility - Content certificate Discovery.
-
Enhance data collection by disabling only those checks with high resource usage, allowing data collection to continue for other checks.
-
Improve troubleshooting capabilities by viewing errors that occur before and after the registration process in the ServiceNow instance.
-
Use file-based Discovery in a macOS environment.
See Agent Client Collector for more information.
</td></tr><tr><td>
Australia
</td><td>
No updates for this release.
</td></tr></tbody> </table>Parent Topic:Products combined by family
Keep exploring.
Find another answer, or bring this documentation into your own tools.