Agent Client Collector Queries

[MDAQUIBK]

Hi All ,

We have recently set up the Agent Client Collector (ACC) in our instance, and the agents are up and running. I have a few observations and queries where I need your assistance:

Observations:

1. Discovery Source for Software Installation Records:

   • We are using ACC-V for software installation records. Ideally, when these records are created or updated via ACC-V, the discovery source should be listed as "ACC-Visibility" or "ACC". However, the discovery source is currently displayed as "Service-Now". Could you please confirm if this is the expected behaviour, or should the discovery source be "ACC-Visibility"?

2. On-Demand Checks for Software Installation Records:

   • According to ACC policies, checks are scheduled to run every 24 hours. We have noticed that software installation records are missing for some servers. Is there a way to run these checks on demand for installed software? We have the "Collect Host Data" option, but it only performs basic checks like those in enhanced discovery. Please advise if there is a way to run more comprehensive checks on demand.

3. Configuration of MID Server Clusters:

   • We are transitioning from a proof of concept (POC) in a lower instance to the production environment, which requires a MID server cluster. Currently, we have only one MID server in the non-production environment. For the production setup, will we need to use multiple IP addresses for the agents during installation, or is there a specific way to manage multiple MID servers within the cluster? Essentially, I am seeking guidance on handling multiple MID servers when using a MID server cluster.

Please help me understanding the urgent queries @Allen Andreas 

Regards,

Aquib

[pratik0306]

Hi @MDAQUIBK

1.  I just checked in 1 of my instance, i can see the same- Discovery source is servicenow for software installations.

2. Not sure about this. There is a OOB setting and i guess only option will be to modify that.

3. If you are referring to using MID server in a cluster for ACC then there is a documentation available in servicenow docs and guidelines on how it should be setup.

[SN Arch Guy]

Are you using agentless discovery for the same CI? If so, check the value of the system property sn_agent.disco_disable_ci_clobber_of_agentless_disco per Using push-based Discovery and horizontal IP-based Discovery together.