---
sourceDocument: Zurich IT Operations Management
sourceDocumentLink: https://www.servicenow.com/docs/r/zurich/it-operations-management

 Release :

    - zurich

ft:locale :

    - en-US

ft:publication_title :

    - Zurich IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Using proxy agents in ACC

# Using proxy agents in Agent Client Collector {#ariaid-title1}

* Release version: Zurich
* 
* Updated July 31, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

You can use a proxy agent to monitor the health and performance of your configuration
items (CIs) even if the agent is in the cloud or any place that is external to your host
server.  
Proxy agents are used to monitor:

* URLs (to ensure that the URLs are available and accessible)
* Services that don't have a host server
* Closed services on which you can't configure an agent
* External databases in the cloud
{#proxy-agent__ul_bty_ctq_dwb}One agent can monitor multiple entities and their CIs.  
The following diagram shows the connection between a ServiceNow instance, the MID Server, and Agent Client Collector agents, as well as proxy agents that monitor CIs that are external to the agent. Figure 1. Proxy agent configuration   

You can configure the proxy agent to do a custom check when it is monitoring external entities.
To learn how to create custom checks, see [Create and edit checks](https://www.servicenow.com/docs/uf4nnYYQm4jxKoe_Y4~_Aw "You can select a check based on the type of entity (such as a server or an application) you want to monitor. You can view and edit the default checks or create new checks, as needed.").

You can create a cluster of proxy agents on multiple proxy servers to monitor the services that
are external to the host server. To learn how to create a proxy agent cluster, see [Create a proxy agent cluster](https://www.servicenow.com/docs/Y9j3gSX5hm5ZsUibDnHr8Q "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.").

Use a Proxy Auto-Configuration (PAC) file to dynamically determine the appropriate proxy server to use. PAC files provide flexible and automated proxy configuration, enabling the agent to use different
proxies for different destinations, connect directly to internal resources, implement complex proxy routing logic, and to automatically handle proxy failover. For details on the parameters used for PAC file configuration, see [Configuration file options](https://www.servicenow.com/docs/xqYsTst~Rs65MnMtc09caA "Options available in the acc.yml configuration file.").  
Following is a sample PAC file:

    function FindProxyForURL (url, host) {

       // Connect directly to internal hosts
       if (isPlainHostName(host) ||
          shExpMatch(host, "*.internal.company.com")) {
          return "DIRECT";
       }

       // use proxy for all other hosts
       return "PROXY proxy.company.com:8080:
    }

**Related concepts**   

* [Checks and policies](https://www.servicenow.com/docs/84noW2JD6OIc~wQw0HT~ZQ "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.")  
**Related reference**   

* [Agent Client Collector Monitoring default checks and policies](https://www.servicenow.com/docs/BPB_PIJvCdfmUC_FRj2MPg "Agent Client Collector Monitoring provides various default checks and policies.")