This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.
TrueSight App Visibility Agent
App Visibility Agent for .NET
App Visibility Agent for .NET - All versions App Visibility Agent for Java - All versions
From the TrueSight Presentation Server (TSPS) console, it is showing UNKNOWN APPLICATION under the application (Monitoring -> Application). Also the following critical events for the App Visibility Agent is seen in the TSPS console or TrueSight Infrastructure Management (TSIM) console:
UNKNOWN_APPLICATION application: Transaction latency on the <hostname>
Why is the App Visibility Agent for Java and/or App Visibility Agent for .NET reporting an “UNKNOWN APPLICATION”?
App Visibility agents are not installed on all the servers that are employed as the first backend tiers (usually a Web tier).
The application name for an automatically discovered application is based on requests that are received by the first backend tier, that is, the tier to which end-user clients directly connect. Automatic application discovery is supported only for end-user clients that use HTTP or HTTPS to connect to the first backend tier.
If the first backend tier communicates with subsequent tiers using an unsupported protocol, or an App Visibility agent is on the subsequent tier but not on the first tier, then the App Visibility agent on the subsequent tier cannot identify the application, and therefore names it UNKNOWN_APPLICATION.
Install App Visibility agents on all servers that are employed as the first backend tier (usually a Web tier), and monitor only HTTP or HTTPS requests to a Web tier.