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.
|
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.
|
Zurich |
Agent Client Collector Framework
- Upgrade MID-less agents
- 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.
- [Placeholder link text to key verify-agent-functionality]
- Starting in version 6.0.0, verify that an agent is functioning properly by performing a self-test on the agent.
- [Placeholder link text to key acc-workspace-dashboard]
- Starting in version 6.0.0, view a list of agents and their statuses on the ACC Workspace dashboard.
- Use improved debug logging
- Starting in version 6.0.0, benefit from enhanced debug logging by sending all debug statements to a log file
- Manage Agent Client Collector certificates
- 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.
- Perform high-volume Agent Client Collector upgrade in a macOS environment
- 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.
- Use an IMDSv2 endpoint for metadata discovery
- Starting in version 5.0, the IMDSv2 endpoint for metadata discovery is invoked when using Agent Client Collector in an AWS EC2 environment.
- Use enhanced errors and diagnostics to troubleshoot issues with servers and endpoints
- 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.
- Disable checks using heavy system resources while in CPU protection mode
- 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.
- Configuration data files size limit
- Starting in version 5.0, configuration data files have a maximum size of 10MB.
- Configure Agent Client Collector with proxy auto-configuration (PAC) files
- Starting in version 5.0, enable easier connection of Agent Client Collector to a proxy server by using a proxy auto-configuration (PAC) file.
|