Agent Client Collector (Visibility) connect and send data to multiple instances

xbr
Tera Contributor

‎01-20-2025 06:17 AM

Hello community, 

so i am asking myself the question if it is possible to somehow send data collected by an Agent (ACC-V) from the same machine to different ServiceNow instances (Dev, Test, Prod). The data does not need to be sent to each different instance at the same time. But as quickly as the developed system may allow it.

I have two thoughts. 
The first one is to install two or more different agents (ACCs) on the same machine and through configuration (acc.yml) send the data to different instances. But i could not find anything about it, yet.
I think this would not be possible using, for example, the .msi installer. But maybe through a silent cmd installation and a few added commands?
Therefore my first question is, how would it be possible to install more then one ACC on the same machine? 

Are there any important arguments against that?

My second thought is to somehow manipulate the acc.yml on the machine, change the neccesary parameters and restart the ACC service to send the data to another MID Server and therefore to another instance.
This article describes what needs to be changed in order to change the agents instance. 
https://www.servicenow.com/community/itom-articles/moving-a-server-s-agent-client-collector-to-a-new...

 

Any thoughts about this idea? 
Ideas, hints, criticism or the elimination of logical errors will be much appreciated.

Thank you in advance. 

Labels:
0 Helpfuls
  • 957 Views
1 REPLY 1

Community Alums
Not applicable

‎01-20-2025 08:13 PM

Hi @xbr ,

An ACC install on a single host cannot be used with multiple ServiceNow instances. For example Agent Client Collector for Monitoring cannot cannot have metrics updated in both production and development instances from the same host at the same time.

There is a limit of a single install of ACC per host server. That ACC can only talk to MID Servers of a single instance.

For testing ACC-related features, dedicated test servers would be needed, or production ACC installs temporarily re-installed for a sub-production instance.

It is possible to edit the acc.yml configuration file with a URL for a MID Server of a different instance, and update the API key to match.

 

Official KB.

 

 

0 Helpfuls