Self monitoring is not working as expected if it's done for multiple domains in domain-separated environment - Known Error

Self monitoring is not working as expected if it's done for multiple domains in domain-separated environment Description Event management self-health monitoring events for ACC agent status messages fail to bind to the correct CI if the event node, the agent is placed to a domain that is a sibling to the domain branch configured on the evt_mgmt.domain_self_monitoring system property. If moving the agent under the same domain branch the binding works without a hitch. The system log output with evt_mgmt.log_debug=true supports this. The domain structure is split in two under a common parent, one branch for regular customers and another one for other customers, so they need to remain separated.

When investigating on live events it get noticed the event processing details looked like it's trying to look in the wrong places so I attempted to create a custom event rule to override the CI binding to look directly in the sn_agent_cmdb_ci_agent table but no luck. The event processing information shows a successful bind when the agent is in the changed domain and a failed bind when it is its original domain.

Steps to Reproduce

Setup EM in a domain-separated environment with at least two adjacent domain branches under a common parent Configure the self-health monitoring sysprop for one domain branch Place at least one ACC agent under the other domain branch Inject agent status events from that agent and observe the CI binding fail Workaround This problem is currently under review and targeted to be fixed in a future release. Subscribe to this Known Error article to receive notifications when more information will be available.