ACC KeepAlive transactions can cause blank Agent CIs to be created - Known Error

ACC KeepAlive transactions can cause blank Agent CIs to be created Description As part of the ACC KeepAlive code, MID Servers running the ACC Endpoint extension regularly call REST Agent Client Collector API, updateClientTimestamp method, to keep the Agent records updated for name and IP address changes. This code uses the function updateAgentInfo in the MonitoringConfig script include, that assumes it can get and then update the sn_agent_cmdb_ci_agent CI record, based on the sys_id referenced in the sn_agent_ci_extended_info record. That does not check the record exists, or can be seen/got, before continuing to update it. That update causes the insert of a almost blank sn_agent_cmdb_ci_agent record, that may have just an ip or name filled in, in addition to any dictionary defaults.

This code should check it has a CI record before attempting to update it, and provide an error message if it cannot.

Normally this should not happen, but various causes for a CI record to to have been inserted in the first place (abort insert business rules, data policy, etc.), or to have been deleted since, or be hidden from the code (query business rule, domain separation, ACLs etc.), have been seen in several customers instances.

Steps to Reproduce

Keep alive where the sn_agent_cmdb_ci_agent record inside of sn_agent_ci_extended_info doesn't exist anymore.

Workaround This problem has been fixed as of ACC-F 3.4. If you are able to upgrade, review the Fixed In section to determine the latest version with a permanent fix your instance can be upgraded to.

After upgrade of the app in the instance, this situation should instead be addressed with a warning message: "MonitoringConfig: Agent Record not found from Agent Extended Info sysid:" being produced when the sn_agent_ci_extended_info's agent record doesn't exist. Delete the sn_agent_ci_extended_info with said sys_id.