Agent Client Collector

The Agent Client Collector Agent feature matrix displays the availability of Agent Client Collector features. The matrix displays data in a graph and a table.

The following table describes each diagnostic self-test that runs in the Agent Self Test Run (sn_agent_self_test_run) table.

Error codes generated during Agent Client Collector upgrades, with descriptions and resolution steps.

The Agent Client Collector Framework manages agent upgrades directly from the instance, with no manual action required on individual agent hosts.

Operating systems and package types supported for Agent Client Collector auto-upgrade, and the minimum agent version required.

System properties that control Agent Client Collector upgrade behavior, including the target version, rate limits, retry logic, and timeouts.

Agent Client Collector for Visibility (ACC-VC) domain usage discovery classifies the domains that users visit against a set of admin-defined domain signatures. It enables you to see which websites and services, such as AI tools, are being used across the endpoints in your environment.

To configure the Agent Client Collector to perform Apache HTTP server monitoring, set the following configurations in the Apache HTTP server application.

To configure the Agent Client Collector to perform Apache Tomcat monitoring, set the following configurations in the Apache Tomcat application.

Create a check definition to execute the osquery command on the Agent.

Create a check type to execute the osquery command on the Agent.

Call the AgentNowHandler.hasAgent API to determine if the CI is associated with a live agent. The API gets a sys_id of the CI and returns a true/false result.

Create a background script to send an osquery request. The osquery request enables data collection from your host's operating system.

Use the Agent Client Collector (ACC) API to create a flow that executes an osquery command on agents and processes the results. By leveraging the ACC API, you can automate the querying of agent data and streamline the processing of results, making it easier to monitor and manage system performance.

An Agent Client Collector (ACC) plugin is a script or group of scripts that extend the Agent Client Collector's capabilities. Plugins enhance monitoring by collecting metrics, performing specialized checks, and triggering events based on conditions, like monitoring an application's queue size when it reaches 60% or 80%. Plugins ensure scalable, customizable monitoring to adapt to evolving infrastructure or application needs.

Automatic selection of MID Servers ensures that each agent uses the most efficient available MID Server.

Agent Client Collector for Visibility (ACC-VC) browser extension discovery inventories browser extensions installed on the endpoints in your environment. When an admin-defined signature matches, ACC-VC classifies each extension into a category, such as AI Tools, Productivity, or Security.

Assess shadow IT and shadow AI risk in your organization by using browser extension metadata fetching in Agent Client Collector for Visibility (ACC-VC). This capability is an optional layer on top of browser extension discovery that collects each extension's metadata.

Group discovered browser extensions in your environment by business relevance.

Group discovered installed software packages in your environment by business relevance.

Agent Client Collector certificates verify the authenticity of your agents, servers, and users. Using Agent Client Collector certificates ensures the safety of your environment.

The Agent Client Collector is a ServiceNow agent installed on your Windows, Linux, and macOS devices to monitor your company’s infrastructure and installed applications.

Configuration data files store dynamic instance data, such as virtual machine details, that check definitions use during execution. This ensures that checks are executed with up-to-date and accurate information about the instance being monitored.

You configure the log levels that you want the Agent Client Collector logs to contain. All events that match or exceed the specified log level display in the Agent Client Collector logs.

Configure the websocket server on MID Servers to enable connections from agents to the MID Server. You can configure only one websocket server per MID Server.

Configure a websocket to enable the endpoint to provide web access from the MID Server to the Agent Client Collector (ACC).

Configure the Agent Client Collector with a MID Server to enable communication between network servers and the ServiceNow instance.

Configure MID-less Agent Client Collector to enable sending information through the cloud. Sending information through the cloud allows the MID Server to be used for more persistent resources.

Policies are attached to groups of related CIs. If you have a subgroup of related CIs, you can attach a new policy to the subgroup using a policy hierarchy, without creating the new policy from scratch.

When creating a check definition or check instance, you can configure the parameters you want to be secured when the agent executes the check. During check execution, the secured parameters are obfuscated, securing their information. Only credential information is obfuscated.

You can take checks from the github community and customize them for use in the Agent Client Collector (ACC), or you can compose your own scripts. Create a plugin with the customized Sensu check and install it on a ServiceNow instance.

Collect data by gathering essential information from an agent's host system before executing any checks or policies. This process ensures that the Agent Client Collector has accurate and up-to-date data on the infrastructure, processes, and applications running on the host.

Description of the properties that determine the behavior of Agent Client Collector data collection.

Agent Client Collector performs data collection based on the scoped apps that you've installed. Agent Client Collector Framework performs basic data collection, and Agent Client Collector for Visibility Content performs enhanced data collection.

Successful Agent Client Collector (ACC) implementations, especially involving large numbers of endpoints or servers, require careful deployment. When proceeding with a large-scale ACC deployment, follow the steps described in the deployment checklist.

Enabling automatic MID Server selection lets the agent perform a connectivity test against the list of available MID Servers. The agent then determines the best connection based on latency and number of currently connected agents. Automatic MID Server selection is disabled by default.

Group the domains that users visit in your environment by business relevance, such as AI tools, productivity applications, or security services.

Discover CIs in your environment by using Agent Client Collector for Visibility Content (ACC-VC) Discovery. ACC-VC works with both horizontal IP-based Discovery, and you can also use push-based Discovery.

To enable a ServiceNow instance to collect and evaluate metrics, you must create a distributed MID Server cluster, associate MID Servers with the cluster, and enable Metric Intelligence for your MID Server.

A financial institution needs to ensure that its data is accessible only to the departments that have authorization for the indicated data.

Optimizing data isolation and monitoring with domain separation ensures financial institutions protect sensitive information, improve operational efficiency, and maintain compliance by securely segregating departmental data.

A policy with a status of published has been passed through the MID Server and sent to the agent. To edit a published policy, you must enable editing.

Configure the Agent Client Collector to stream log data from Linux and Windows hosts to a ServiceNow instance without using guided setup.

Enable a load balancer to ensure that you have functional MID Servers. A load balancer distributes resources over multiple MID Servers to ensure that no single MID Server is overloaded.

To enable monitoring logs in a Linux environment, select the relevant policy and assign specific check parameters to the policy. When log monitoring is enabled and a specified string is discovered in the log being monitored, the system creates an event.

To enable monitoring logs in a Windows environment, select the relevant policy and assign specific check parameters to the policy. When log monitoring is enabled and a specified string is discovered in the log being monitored, the system creates an event.

If CPU consumption on your server is getting too high, you can manually turn off the Agent Client Collector data collection. This pauses all checks performed by the agent, except for the agent's keep alive messages.

When deploying the Agent Client Collector, perform deployment and management tasks on your endpoints.

Use the Monitoring HTTP Entry Points and Monitoring HTTP Entry Points Metrics policies that come with the ITOM Monitoring scoped app to monitor http and https entry points and entry points metrics. You can customize these policies as needed, or you can configure a new policy to monitor service entry points.

The Agent Client Collector gathers information on the health of the CI that the Agent is installed on, and the applications that run on the hosts. The Agent runs several checks and pushes the checks' results to the MID Server, where they are converted into events or metrics.

You can move a single or multiple Agent Client Collector policies from one ServiceNow instance to another by exporting the policy and then importing it into the target instance. Only published policies can be exported.

Discover file information in your system using Agent Client Collector for Visibility Content (ACC-VC) File-Based Discovery (FBD).

The following tables display the agent performance KPIs and its footprint on the host during URL monitoring data collection execution on different operation systems.

Agent Client Collector Framework provides default checks with the base system.

Description of the properties that determine the behavior of Agent Client Collector Framework configuration.

The Agent Client Collector Framework (ACC-F) use case demonstrates how a financial organization can use Agent Client Collector Framework to assist in IT asset discovery.

Specify the checks to be included in the list of checks that are enabled to run on the agent.

The Agent Client Collector Health Dashboard enables you to monitor the status of the agents in your system.

Description of the command line parameters used during MID-less Agent Client Collector installation.

Install MID-less Agent Client Collector manually on a Linux machine to enable sending data from the agent to the instance through the cloud. Sending information through the cloud allows the MID Server to be used for more persistent resources.

Install MID-less Agent Client Collector on a Linux machine to enable sending data from the agent to the instance through the cloud. Sending information through the cloud allows the MID Server to be used for more persistent resources.

Install MID-less Agent Client Collector manually on a macOS machine to enable sending data from the agent to the instance through the cloud. Sending information through the cloud allows the MID Server to be used for more persistent resources.

Install MID-less Agent Client Collector on a macOS machine to enable sending data from the agent to the instance through the cloud. Sending information through the cloud allows the MID Server to be used for more persistent resources.

Install MID-less Agent Client Collector on a Windows machine to enable sending data from the agent to the instance through the cloud. Sending information through the cloud allows the MID Server to be used for more persistent resources.

Install Agent Client Collector on a system that uses a Linux OS. Use a single-line command script, or follow the installation procedure to embed the agent in your own package distribution mechanism. The installation procedure provides consistency when using package distribution solutions.

Install Agent Client Collector on a system that uses macOS. Use a single-line command script, or follow a manual installation procedure if the agent is not connected to the instance or you want enhanced customization options.

Install Agent Client Collector manually on a machine that uses macOS when the agent is not connected to the instance or you want enhanced customization options.

Use an efficient single-line command script to install Agent Client Collector on a machine that uses macOS operating system. Use the manual installation procedure if the agent is not connected to the instance or you want enhanced customization options.

Perform a manual upgrade of your existing Agent Client Collector version on a system running a Linux OS. Use this procedure if the single-line command script is not connected to the instance or you want to use enhanced customization options.

Perform a manual upgrade of your existing Agent Client Collector version on a system running a Windows OS.

Install the Agent Client Collector on a Windows machine manually when you want to test the agent on a single system.

You can install the Agent Client Collector on any supported host machine. The Agent Client Collector connects to a MID Server using the HTTP/S protocol, and the connection remains active after being established. One MID Server may handle several agents simultaneously. A single agent works with one MID Server at a time and switches to a different MID Server when necessary to provide failover protection.

The Agent Client Collector (ACC) health instance scan suite includes checks that detect anomalies and issues on your instance. Use this reference to identify what each check does and when it applies.

Run the Run (ACC) health instance scan as a scheduled job to monitor the overall health of the instance receiving data from the Agent Client Collector.

The Agent Client Collector (ACC) health instance scan suite consists of checks that detect anomalies and other issues that might occur on your instance. These checks ensure the overall health and performance of the ACC, proactively identifying potential problems before they impact system operations.

Installing MID-less Agent Client Collector (ACC) enables you to send data from the agent to the instance through the cloud. Sending information through the cloud allows the MID Server to be used for more persistent resources.

The Agent Client Collector is an agent that is installed on infrastructure components. The Agent Client Collector is built on a Sensu framework which enables you to adopt and extend monitoring checks from the community. It executes commands on the machines it is installed on and sends output data to the ServiceNow instance via the MID Server. Events and metrics are stored in the relevant database.

You can limit the metrics you send from the MID Server to the instance, either by de-activating a specific CI or an entire CI type.

Uninstall the Agent Client Collector from a Linux machine manually if the command script is unavailable due to the specific agent not being connected to the instance.

Upgrade your existing Agent Client Collector version on a system running a Linux OS. Use this procedure if the single-line command script is not connected to the instance or you want to use enhanced customization options.

Agent Client Collector Log Analytics provides various default policies and checks.

Agent Client Collector Log Analytics (ACC-L) enables you to stream log data from Linux and Windows hosts to a ServiceNow instance, using the Agent Client Collector.

If Agent Client Collector logs get too large, they can drain system resources. To ensure system efficiency, configure parameters in the acc.yml file by which to rotate logs out of the system's storage (Windows default location = C:\ProgramData\ServiceNow\agent-client-collector\config\acc.yml. Linux default location = /etc/servicenow/agent-client-collector/acc.yml).

Agent Client Collector (ACC) logs play a critical role in monitoring the activity and performance of the agent. Logs offer valuable feedback that helps identify potential issues, especially when the agent's performance is suboptimal. By providing insights into areas of concern, these logs are essential for troubleshooting and resolving issues, ultimately improving the overall effectiveness of the agent.

The following table displays the available log levels which indicate the severity of Agent Client Collector events.

Perform a manual upgrade of your existing Agent Client Collector version on a system running a macOS. Manual upgrade is useful if the single-line command script isn’t connected to the instance or you want to use enhanced customization options.

Agent Client Collector checks require specific credentials and permissions to execute successfully. The following sections outline the application-level (DB grants, API roles) and OS-level access required for each check.

The following table describes Agent Client Collector resource consumption. We supply performance testing values to specific customers upon request.

Agent Client Collector Monitoring enables you to monitor your service availability, examine the health and performance of your environment, and ensure that your infrastructure and its applications are running properly.

Reference topics provide additional information about Agent Client Collector Monitoring checks and policies.

Enable Agent Client Collector monitoring on the MID Server by configuring the Agent Client Collector framework (ACC-F) and Metric Intelligence extensions in a single action. Enabling Agent Client Collector monitoring also enables monitoring on agents connected to the MID Server.

Lists the Agent Client Collector Monitoring system properties that control monitoring behavior.

The Agent Client Collector Monitoring (ACC-M) use case demonstrates how organizations can achieve unified monitoring across hybrid IT environments.

The settings you can customize when generating an Agent Onboarding installation plan. Toggle settings to activate and enable customization.

Use an efficient single-line command script to install Agent Client Collector on a machine that uses a Linux operating system. If a script is not connected to the instance or you want to use enhanced customization options, you might have to install Agent Client Collector manually.

Successful Agent Client Collector (ACC) implementations, especially involving large numbers of endpoints or servers, require careful planning. Before proceeding with a large-scale ACC deployment, follow the steps described in the planning checklist.

Description of the properties that determine the behavior of Agent Client Collector policy collection.

Successful Agent Client Collector (ACC) implementations, especially involving large numbers of endpoints or servers, require careful deployment. When proceeding with a large-scale ACC deployment, follow the steps described in the planning and deployment checklists.

Discover Java installation information in your system using Agent Client Collector for Visibility Content Process-Based Discovery (PBD).

Optimize the distribution of agents by allowing redistribution from one MID Server to another. Agents will always be connected to the MID Server with the fastest response time.

Reference topics provide additional information about Agent Client Collector.

Perform manual restart of an agent when the agent configuration file has been refreshed, or if the agent is unstable. You can perform manual restart only on agents installed in a Windows environment and for Linux-based agents that use systemd.

You can perform host data collection on demand, if you need to perform data collection before the job is scheduled to run.

When you customize or create an Agent Client Collector plugin, you can secure the plugin with either a third-party certificate or an internal secure certificate in the plugin's script. Official plugins are signed by an external certificate authority.

When deploying the Agent Client Collector, perform deployment and management tasks on your environment's servers.

When an agent meets the configured thresholds specified in the agent's acc.yml file, it enters CPU protection mode, either for an individual check or for all checks. Agents in CPU protection mode appear in the agent logs with the syntax Agent Protection.

When deploying the Agent Client Collector, there are components which are shared between servers and endpoints.

Create a self-signed certificate for an Agent Client Collector plugin. The following procedure gives an example of how to create an x509 certificate using OpenSSL. For other certificate types, consult OpenSSL documentation.

Agent Client Collector for Visibility (ACC-VC) classifies discovered software packages in your environment into categories. This categorization removes the need to tag software records manually and provides an accurate software inventory.

System requirements are the fundamental specifications and configuration needed to install and run Agent Client Collector (ACC) effectively.

When working with a check definition or check instance, you can test the check against its assigned agent to ensure that the check is configured properly.

Uninstall the Agent Client Collector from a Linux machine by running an efficient single-line command. If the script is not connected to the instance, you might have to uninstall Agent Client Collector manually.

Uninstall the Agent Client Collector from a macOS machine manually instead of using the single-line procedure when the specific agent is not connected to the instance.

Uninstall the Agent Client Collector from macOS machine by running an efficient single-line command. If the agent is connected to the instance, uninstall Agent Client Collector manually.

Uninstall the Agent Client Collector from a Windows machine by running an efficient single-line command. If the script is not connected to the instance, you might have to uninstall Agent Client Collector manually.

Uninstall the Agent Client Collector from a Windows machine manually instead of using the single-line procedure. Use the manual procedure if the command script is unavailable due to the specific agent not being connected to the instance.

By default, the list of MID servers connected to agents is updated once daily. If you have a dynamic environment that adds MID servers frequently, you may want to schedule updates more often, or execute the job on demand.

Administrators can assign user roles to grant access to the Agent Client Collector. The following standard roles for the Agent Client Collector Framework (ACC-F) are included in the ServiceNow system with the Agent Client Collector installed on it.

Secure parameters in Agent Client Collector (ACC) refers to securely passing sensitive data, such as user names, passwords, and API keys, during check execution. Sensitive data is not exposed in the command line. Parameters are passed to the script through standard input (STDIN), hiding them from logs or any process that might capture command-line arguments.

Portable applications are those applications that don’t need to be installed on the target system. Starting in ACC-VC version 2.3.0, push-based Discovery can detect portable applications, such as Firefox, VLC, Notepad++ etc, for Windows only.

CMDB owners need CIs to contain all domain system names (DNS) associated with their system. Starting in Agent Client Collector for Visibility Content (ACC-VC) version 2.3.0, ACC-VC can discover DNS name lists for Windows and Linux CIs.

Agent Client Collector for Visibility Content (ACC-VC) version 1.3.0 supports exclusion lists for IPs and Network Interface Controllers (NICs). A flexible mechanism filters out values for IPs and NICs when creating or updating the host CI and related items.

After installing the Agent Client Collector on a Linux system, validate the installation by ensuring it was completed properly.

Create a golden image to run on a VIrtual Desktop Infrastructure (VDI) machine. The golden image enables installing a virtual agent on VDI virtual machine, which generates data quicker than standard agents.

You can view the activity logs for an Agent Client Collector.

Deploy the Agent Client Collector on a virtual machine during mass deployment using the machine's base image. Mass deployment uses silent installation, which hides installation status.

Agent Client Collector for Visibility Content (ACC-VC) provides various checks and policies as well as a business rule.

The Agent Client Collector for Visibility Content (ACC-VC) use case demonstrates how a financial organization can perform effective discovery across on-premise and remote environments.

Install the Agent Client Collector on a Windows machine by downloading an installation file and using a wizard, or by using silent installation to automate agent installation and configuration. Manual installation enables you to test the agent on a single system, while silent installation enables you to deploy the agent at scale.

Install the Agent Client Collector on a Windows machine using silent installation when you want to deploy the agent at scale.

Options available in the acc.yml configuration file.

View the acc.yml Agent Client Collector configuration file without having to access the host server by retrieving the file from an agent.

Refine an existing log policy to focus on a subset of CIs or services by creating a child policy.

Description of the fields on the ACC data input configuration form.

Data inputs for streaming log messages to your ServiceNow instance using the Agent Client Collector are created automatically as part of the Agent Client Collector setup. Set up additional ACC data inputs manually as needed using the Health Log Analytics data input setup flow.

Modify a log path configuration in the log shipper check instance.

You can edit published Agent Client Collector log policies. For example, modify a default log policy if your organization always uses a specific non-default log path.

Configure Agent Client Collector Log Analytics on your ServiceNow instance using guided setup.

View all log shipper check alerts for Agent Client Collector Log Analytics (ACC-L) agents.

View all log shipper events with all severity levels for Agent Client Collector Log Analytics (ACC-L) agents.

Configure Agent Client Collector Log Analytics on your ServiceNow instance either with or without using guided setup.

In the ACC data input record, the Streaming Sources related list shows the streaming data of that data input's sources.

Make sure that your ACC data inputs are streaming data properly by identifying and resolving log streaming issues.

System properties that control how Agent Client Collector for Visibility Content (ACC-VC) runs Enhanced Discovery and installed software checks on Windows non-persistent virtual desktop infrastructure (NPVDI) endpoints.

Agent Client Collector for Visibility Content (ACC-VC) adjusts how its discovery and software checks run on Windows non-persistent virtual desktop infrastructure (NPVDI) endpoints, so that data collected during a short-lived session reaches your instance before the session ends.

Agent Client Collector for Visibility Content (ACC-VC) can discover software on Windows, Linux, and macOS endpoints that is not discoverable by traditional ACC-VC checks and policies. ACC-VC uses third-party package managers to track essential tools and development packages for software asset management (SAM) and IT asset management (ITAM).

System properties that control how Agent Client Collector for Visibility Content (ACC-VC) discovers, collects, and stores data on your instance.

The following table lists the metrics that are gathered as output from Active Directory checks. Entries indicated as Featured metrics are high-visibility metrics that are displayed in the Operator Workspace Metric tab after an alert is generated. These metrics provide the operator with additional information to help them further explore the specified issue.

Add a self-signed certificate to the truststore of your operating system (OS). By adding a certificate to the truststore, you can verify that the certificate is authentic and that your connections are secure.

The Agent Client Collector certificate is valid for two years and must be rotated before it expires to avoid issues with agent connectivity. When expiration is approaching, the agent initiates a certificate rotation request.

Plan and configure your Agent Client Collector implementation.

Review this information for details on OS query scripts, data collected, and definition of terms.

Reference topics provide additional information about mapping and fine-tuning application services using Agent Client Collector Framework lists and forms.

View an error analysis created by generative AI. Error analyses enable asking questions on a specific agent's error or error code.

After you complete agent onboarding, the system generates an installation plan. The following table describes each step in the plan and the commands or actions required.

Clear the plugin and configuration file cache folder and control plugin downloads. Clearing the cache folder removes unwanted plugins that have synced to the agent.

Agent Client Collector Monitoring provides various default checks and policies.

Configure an agent registration key so that you can deploy MID-less Agent Client Collector. Deploying MID-less Agent Client Collector enables you to use the MID Server for more persistent resources.

The following table lists and describes the Agent Client Collector statuses.

AI Proxy gives customers visibility and control over AI traffic leaving managed endpoints. It intercepts outbound calls to AI providers, attributes each call to the originating process, and streams structured events to the AI Control Tower (AICT) on your ServiceNow instance.

AI Control Tower (AICT) is an enterprise-grade governance control plane which provides centralized visibility, monitoring, and policy enforcement across all AI systems and platforms within an organization. AICT addresses the challenge of uncontrolled AI adoption by intercepting AI-related traffic at the network, device, or application layer and applying organization-wide security and data governance policies.

Configure an AI proxy server to monitor AI commands traveling from your Agent Client Collector (ACC) agent to the AI Control Tower (AICT).

Application patterns gather details on the applications that run on the Agent Client Collector (ACC) host. Application patterns are supported only for servers, and are triggered after the Agent Client Collector host Discovery is complete.

Reference information for the filtering rules and performance safeguards that apply when Agent Client Collector for Visibility Content scans ZIP and JAR archive files during File-Based Discovery.

Assign a proxy agent cluster to a policy when monitoring services external to the host server, such as URLs or external databases in the cloud. The agents in the cluster monitor all of the policy's CIs.

Agent Client Collector provides the following default checks and policies for AWS monitoring.

The following tables list and describe the metrics that are gathered as output from the specified AWS checks. Entries indicated as Featured metrics are high-visibility metrics that are displayed in the Operator Workspace Metric tab after an alert is generated. These metrics provide the operator with additional information to help them further explore the specified issue.

Agent Client Collector provides the following default checks and policies for Azure health monitoring.

Azure cloud metrics are gathered from Azure virtual machines (VMs) and Azure storage account policies. Collecting the cloud metrics enables you to monitor the performance of your Azure resources.

When creating a new policy for Azure cloud metrics, create a .json script to determine the metrics to be monitored. The format for the script appears below, followed by a table explaining the script contents.

The following tables list and describe the metrics that are gathered as output from Azure checks. Entries indicated as Featured metrics are high-visibility metrics that are displayed in the Operator Workspace Metric tab after an alert is generated. These metrics provide the operator with additional information to help them further explore the specified issue.

Agent Client Collector provides the following policies for Cassandra health monitoring. Policies come with the checks specified in the indicated table. Policies and checks are available for Linux only.

The following table lists the metrics that are gathered as output from Cassandra checks. Entries indicated as Featured metrics are high-visibility metrics that are displayed in the Operator Workspace Metric tab after an alert is generated. These metrics provide the operator with additional information to help them further explore the specified issue.

Create proxies for added security when upgrading MID-less agents via a Content Delivery Network (CDN). You add proxy servers to the sn_agent_proxy table on the ServiceNow instance.

The following table lists and describes the possible reasons for revoking an Agent Client Collector certificate to stop communication between the agent and ITOM cloud services.

The fields to be configured on the Check Definition page, when creating a check definition.

The Parameters tab definitions for the Command field on the check definition form.

Run a check command on your server or database to gather data from those devices. Depending on the check that is invoked, collected data may be monitoring data, visibility data, log data, or user metrics.

A check is a combination of a command and its configuration. The check is executed on the Agent Client Collector's devices to gather data from those devices.

Cloud Native Operations for Visibility (CNO for Visibility) has been renamed Agent Client Collector for Kubernetes – Visibility. The term Cloud Native Operations for Visibility has been deprecated.

Run data collection on an agent's host to discover the components that are running on the host.

Collect data on the host being monitored by an agent. Manually collecting host data ensures that the host's files are up to date.

Track website visits across your organization and gain visibility into web applications your users access using Agent Client Collector for Visibility Content (ACC-VC).

Configure the MID Servers with Agent Client Collector capabilities to enable the MID Servers to work with agents. Agents that have identical MID Server capabilities are eligible for automatic MID Server selection.

Use a single-line command to set up a MID-less Agent Client Collector. You can also use the single-line command to migrate agents configured with a MID Server to have a MID-less configuration.

Use a single-line command to set up an Agent Client Collector with a MID Server. You can also use the single-line command to migrate agents with MID-less configuration to be used with a MID Server.

Choose which Enhanced Discovery modules Agent Client Collector for Visibility Content (ACC-VC) skips on Windows non-persistent virtual desktop infrastructure (NPVDI) endpoints. Optionally, choose whether installed software scan results are cached within the same session.

Create a cluster of agents on multiple proxy servers to monitor services external to the host server. Creating a cluster of agents enables you to assign that cluster to multiple policies instead of having to assign the agents individually to every policy.

Configure an Agent Client Collector on a proxy server when monitoring services external to the host server, such as URLs or external databases in the cloud.

Set the system properties that control Agent Client Collector upgrade behavior, including the target version and rate limits for mass upgrades.

Add a proxy server entry so that agents behind a corporate proxy can download upgrade packages from the ServiceNow Content Delivery Network (CDN).

Configure the MID Servers that are ineligible for automatic MID Server selection with the agent. For example, you may want to block a MID Server from connecting to your agent due to firewall constraints.

Configure the HAProxy metrics stats page to enable monitoring your system devices by viewing HAProxy metrics.

Create a configuration setting rule that refines the level of anomaly detection processing and analysis that is applied to specific CIs and metrics. Set a processing level that reflects the importance of metrics at different stages of implementation, to reduce data load if needed.

Enable license key discovery and define the registry paths and values you want the Agent Client Collector for Visibility Content Windows agent to collect from managed endpoints.

Enable license key discovery to verify the legitimacy of your software installation. Set up support for a new vendor's license file format by creating a parser script and defining a matching rule.

Metric Intelligence uses data sources that can monitor hundreds of metrics for all CIs. Choose which details are important for each data source type and CI, then activate or deactivate the respective monitor type to control data processing.

Connect agents to a MID Server to enable Agent Client Collector Monitoring (ACC-M) functionality.

Connect agents to multiple MID Servers to enable Agent Client Collector Monitoring functionality. Multiple MID Servers can support each other with load balancing and domain separation.

By default, Osquery supports log rotation based on size. To enable it for SAM total usage metrics and to configure the log size and rotation, you need to add specific flags for Osqueryd service.

Configure portable software the Agent Client Collector for Visibility Content (ACC-VC) agent discovers by updating the config table. This ensures that only portable software that was configured is searched for and discovered.

Plan and configure your Agent Client Collector Monitoring implementation.

Create an Agent Client Collector configuration data file and associate it with check definitions so that you can view the information about your instance. You can also add or delete an attachment to the configuration data files, which are used by check definitions during check executions.

Create AICT policies to block personnel from using unauthorized AI tools. AICT polices are synchronized with the Agent Client Collector, which invokes the policies that run.

Create a check parameter to add a configurable input that customizes how a check runs, without changing the underlying script or command.

Configuration settings affect how metric data is processed. Configuration settings rules override the default metric processing behavior to determine the system actions when an anomaly is detected.

Create a custom filter rule in the Software Install Custom Filter table (samp_sw_install_custom_filter). Rules determine the criteria by which software is excluded from your Software Asset Management (SAM) workspace.

Custom plugins extend Agent Client Collector monitoring capabilities beyond the default plugins. You can create plugins for specific monitoring requirements or modify existing plugins.

Policies consist of the CIs monitored by the Agent Client Collector and the checks that run on those CIs. When creating a policy, you configure a filter which determines the CIs on which the checks are to run. For example, a policy to run checks on all Apache web servers. You can create new policies or edit the default policies.

Create a maintenance token to use when uninstalling an agent from a Windows device. Administrators require maintenance tokens to ensure that unauthorized employees can't perform an uninstall.

Create your own policies to enable Azure to collect the metrics for the resources that have policies that don’t come with the base system. The Azure Metrics Collector check brings the metrics to the agent through the Azure Metrics Batch API.

Configure a service filter so that the policy monitors only those services that match the filter.

Customize the Monitoring Technology Dashboard widgets in the Data Visualizations library so your dashboard displays information exactly as you want to see it.

Configure the amount of time (in seconds) by which the Zscaler remediation check verifies the Zscaler status. This amount of time indicates how often the system checks the Zscaler status after the remediation check runs.

The following tables describe the data collected during Agent Client Collector for Visibility Content file-based Discovery.

You can perform actions which enhance data collection from the hosts on which Agent Client Collector is running.

Define temporary variables by assigning values such as executable paths, config file paths, and so forth. Defining temporary variables ensures that runtime commands are successful.

The Agent Client Collector provides the following default checks and policies for Directory Scan monitoring.

Use application fingerprints to discover the Varnish CI, to enable running Varnish checks.

If any conkeyrefs are broken, re-add them from the doc/source/reuse/domain-separation/domain-separation-overview.dita file.In the short description, edit the first sentence to state whether domain separation is supported or not and add the application name. Keep the conkeyref at the end that describes domain separation.Domain separation is supported for Agent Client Collector (ACC) when deploying ACC with a MID Server. Domain separation enables you to separate data, processes, and administrative tasks into logical groupings called domains. You can control several aspects of this separation, including which users can see and access data.

Activate the built-in scheduled job to upgrade all eligible Agent Client Collector agents automatically in rate-limited batches.

Set configurations in the Apache HTTP server application to enable the Agent Client Collector to perform Apache Kafka HTTP server monitoring.

Configure an agent to enable it to work in a non-persistent virtual desktop infrastructure (NPVDI) environment. NPVDI agents are self-sufficient and start running checks immediately.

Enable running process-based discovery so that the Agent Client Collector for Visibility Content agent detects software running from directories outside your configured File-Based Discovery scan paths.

The event severity numbers correspond to actual severities on the Metric Anomaly Score to Event Severity Maps page.

Exclude specific directories from running process-based discovery so that processes running from those locations aren't recorded or included in File-Based Discovery scans.

Agent Client Collector Monitoring is built on a Sensu framework which enables you to adopt and extend monitoring checks from the community. Agent Client Collector Monitoring collects data on your company’s infrastructure and installed applications.

The Agent Client Collector Framework (ACC-F) is a powerful solution for monitoring the performance and health of infrastructure components by using agents installed on servers and devices. It collects and sends critical system data to ServiceNow for analysis, enabling proactive management and troubleshooting of Configuration Items (CIs).

AI provides generative AI features in Agent Client Collector Monitoring that help administrators diagnose agent errors and investigate agent behavior faster.

To update the Assigned To attribute of the Computer CI, you need to collect information from the logged in user.

Configure File-Based Discovery behavior using system properties that control scanning paths, performance throttling, and file filtering options.

Agent Client Collector File-Based Discovery (FBD) scans file systems on managed endpoints to discover installed software and track file inventories.

OS-level permission requirements for the file or directory check.

You can persist the type of users that populate the CMDB depending on your particular interests. Currently, local and system are supported for Windows, Linux, and macOS.

Configure the Google Cloud Platform (GCP) configuration data file to monitor metrics in your GCP environment.

The following table lists and describes the metrics that are gathered by the acc_grp_metrics_list.json configuration data file. The file is uploaded to a check definition or check instance, and the metrics in the file are monitored by the check for its agent.

Generate an allowlist for a selection of patterns, to configure the patterns permitted to run on an agent.

Agent Client Collector provides the following default checks and policies for Glassfish monitoring.

The following table lists the metrics that are gathered as output from GlassFish checks. Entries indicated as Featured metrics are high-visibility metrics that are displayed in the Operator Workspace Metric tab after an alert is generated. These metrics provide the operator with additional information to help them further explore the specified issue.

When installing an agent on a Windows host using a LocalService, LocalSystem, or gMSA account, you must run msi commands to enable the accounts.

The following table outlines the structure and modularity of the golden image mode for cloning agents, based on the operating system (OS) in use.

Credential and permission requirements for the HAProxy checks check-haproxy and metrics-check-haproxy.

Agent Client Collector provides the following default checks and policies for HAProxy monitoring.

The following table lists the metrics that are gathered as output from HAProxy checks. Entries indicated as Featured metrics are high-visibility metrics that are displayed in the Operator Workspace Metric tab after an alert is generated. These metrics provide the operator with additional information to help them further explore the specified issue.

Agent Client Collector data inputs stream log messages to your ServiceNow instance using the ServiceNow Agent Client Collector. The Agent Client Collector Log Analytics (ACC-L) application provides predefined log policies for collecting log data from the CIs monitored by the ACC.

Create an ACC log policy when no default policy exists for the CI you want Agent Client Collector to monitor.

When the Agent Client Collector Log Analytics (ACC-L) application discovers a CI that is not associated to an application service, it creates a dynamic CI Group. The application then associates the CI to the group.

Agent Client Collector setup automatically creates an ACC data input for streaming log messages to your ServiceNow instance. You can set up additional ACC data inputs manually as needed.

Agent Client Collector for Visibility Content (ACC-VC) requires installation of ServiceNow Agent Client Collector (ACC) on the target host. ACC is a derivative of Sensu-Go, an open-source software.

Agent Client Collector provides the following policies for HTTP health monitoring. Policies come with the checks specified in the tables below.