ACC Visibility created all applications with the name "<class label from dictionary>@<hostname>", and with no identification information for the specific application instance, causing issues for IRE on instances also using Discovery - Known Error

ACC Visibility created all applications with the name " @ ", and with no identification information for the specific application instance, causing issues for IRE on instances also using Discovery Description ACC-V will gather information on running processes, and then using the ip-based discovery process classification records, make matches and create Application CIs. The naming convention is simply " @hostname", which is not in line with how Discovery names them in general, or how specific application patterns name them. This breaks the OOTB identification rules, which rely on unique names for many applications, plus other attributes such as Oracle SID, that ACC does not collect.

The symptoms are: - separate application CIs created by Discovery and ACC-V, for the same thing - a single CI is repeatedly updated for different processes on the same host, due to always using the same name for each process

This naming of the application CI is is different to how IP-based Discovery process classification, or Discovery Patterns would name the CI. If the name is not overridden by a application specific pattern, then Discovery defaults to @ " . If a Pattern is involved, the naming convention will be specific to that pattern. e.g. Oracle pattern will be " @ ", and the response for this is often to have unique names for multiple instances of the same software installed and running on the same host. If this is not done, as is the case with ACC currently, then you can end up with duplicate application CIs being created with different names, or the same single CI being updated multiple times for multiple different running processes.

Steps to Reproduce

Use both Discovery and ACC-V to create application CIs for the same host.

Workaround After carefully considering the severity and frequency of the issue, and the cost and risk of attempting a fix, it has been decided to address this issue as a future product enhancement.

The solution to this is to discover applications via ACC, by running the same Discovery Patterns as Discovery. As of June 2024, this is in controlled availability, and being tested by some customers. Keep an eye on the release notes:

Agent Client Collector for Visibility release notes Agent Client Collector Framework release notes