Combined Agent Client Collector release notes for upgrades from Vancouver to Washington DC

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 Vancouver to Washington DC.

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 Washington DC

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


Release	Release notes
Vancouver	No updates for this release.
Washington DC	No updates for this release.

New features

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


Release	Release notes
Vancouver	Using the new Windows event log check Use Linux and Microsoft Exchange checks to monitor the health and performance of your system. Metric Intelligence improvements Use anomaly labels to reduce the number of false-positive anomaly alerts in Metric Intelligence. Metric Intelligence Advanced Promotion Engine Reduce the number of false-positive anomaly alerts by setting rules to determine which alerts to promote to IT alerts. Consolidate your promoted alerts into a single alert. By using alert grouping, you can reduce the number of anomaly alerts that your system receives. Discover the resources in your Kubernetes clusters continuously Starting in version 3.9.2, use Cloud Native Operations (CNO) for Visibility to discover the resources in your Kubernetes clusters continuously as an alternative to pattern-based discovery. Discover the resources in Kubernetes clusters deployed in on-premises and Cloud environments in near real-time without the need to enter any credentials in your ServiceNow instance. Ensure that the changes in the resources are promptly reported to the instance and updated in the Configuration Management Database (CMDB). Viewing additional platforms on the Monitoring Technology Dashboard Use the Monitoring Technology Dashboard to monitor for: AWS services GCP services VMware vSphere services Using metric connector enhancements Starting in version 3.9.0, use agent-less System Center Operations Manager (SCOM) connectors for high-performance SCOM metric integration. Application patterns for the Agent Client Collector Run application patterns through the Agent Client Collector. Application patterns enable discovering details about applications running on an agent’s host. Support for macOS endpoints Use Agent Client Collector for Visibility to support the macOS Ventura operating system. Using regular expressions in the allow list Enable complex character combinations in an allow list command string by using the use_regex parameter. Executing check commands in execv mode Enhance your security during checks by using the `execv` execution mode. Using third-party components Use the latest Sensu and osquery components with the configuration options in the acc.yml file. Enhanced system properties Starting in version 3.3.1, monitor the behavior of the Agent Client Collector policies and framework configuration with the Policy Calculation and Framework Configuration system properties. Configuration data files added to checks Starting in version 3.3.1, provide enhanced data collection in the Agent Client Collector by communicating the instance data with the agent. The configuration data files are also sent to the agent’s associated MID Server. MongoDB checks Starting in version 3.9.2, monitor the MongoDB resources with additional metrics.
Washington DC	Using metric connector enhancements Use agent-less System Center Operations Manager (SCOM) connectors for high-performance SCOM metric integration. Application patterns for the Agent Client Collector Run application patterns through the Agent Client Collector. Application patterns enable discovering details about applications running on an agent’s host. Enhanced system properties 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. Configuration data files added to checks 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. Mongo DB checks Monitor MongoDB resources with additional metrics that relate to the metadata, memory, and disk space. Continuously discover the resources in your Kubernetes clusters 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). Retrieving the metrics for cloud resources Retrieve the high-performance metrics for virtual resources in the cloud by using VMware. Pull additional resources from Kubernetes clusters into the CMDB 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. Create a cmdb_ci_linux_server CI for each Kubernetes node 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. Define include and exclude lists of Labels and Annotations 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. Display the Kubernetes cluster version in 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. Add custom Labels and Annotations to Kubernetes resources 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. Secure check verification through the allow-list 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. Add a self-signed certificate to your operating system's truststore Starting in version 3.5.1, enhance security by adding a self-signed certificate to your OS's trust store. Clear agent assets 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. New Linux and Windows checks supported Starting in version 3.5.1, Agent Client Collector supports additional Linux and Windows checks.

Changes

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


Release	Release notes
Vancouver	Automatic loading of the allow list after check execution When executing a check, the allow list loads automatically. You don't need to restart the agent. Automatic MID Server selection Starting in version 3.3.1: 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. Retrieving metrics for cloud resources Starting in version 3.3.1, use Azure checks and policies to retrieve metrics for virtual resources in the cloud. Monitoring Technology Dashboards Starting in version 3.3.1: Filter metrics by selected 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. Metric rules Starting in version 3.9.0, configure manual thresholds for generating metric alerts using the Metric Rules feature instead of the Static Thresholds UI. SNMP checks Starting in version 3.9.2, SNMP checks work by default with v3.
Washington DC	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. Metric rules Configure manual thresholds for generating metric alerts using the Metric Rules feature instead of the Static Thresholds UI. Retrieving the metrics for cloud resources 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. Agent table cleaner Delete the agent records that have been disconnected or inactive for more than 30 days by using the Autoflush form. SNMP checks SNMP checks work by default with v3. Set the agent log level Starting in version 3.5.1, configure the agent log level through the ServiceNow® instance, without needing to access the acc.yml configuration file. Host system requirements for Agent Client Collector Monitoring Starting in version 3.5.1, utilize the updated minimum host system requirements when installing Agent Client Collector Monitoring. Import a script include to enable using the Instance scan Starting in version 3.5.1, import global.ACCInstanceScanUtil to enable using the Instance scan feature, as described in the KB1630132 knowledge base article.

Removed

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


Release	Release notes
Vancouver	AWS and Azure connectors are not supported in Metric Intelligence. Starting in version 3.3.1, the Azure Monitoring Technology Dashboard has been deprecated with the update of the Azure policies.
Washington DC	No updates for this release.

Deprecations

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


Release	Release notes
Vancouver	No updates for this release.
Washington DC	No updates for this release.

Activation information

Review information on how to activate Agent Client Collector.


Release	Release notes
Vancouver	Agent Client Collector is available with the 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.
Washington DC	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
Vancouver	No updates for this release.
Washington DC	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
Vancouver	No updates for this release.
Washington DC	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
Vancouver	No updates for this release.
Washington DC	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
Vancouver	No updates for this release.
Washington DC	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
Vancouver	Organize your monitored components by viewing the dashboards for each monitored technology. Monitor the health and performance of your system with the Windows log monitoring checks. Get faster recovery times for your anomaly alerts. See Agent Client Collector for more information.
Washington DC	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.