Page tree

As an application specialist, you want to monitor web applications that are critical to your organization and that require direct and immediate visibility. You set up the applications for monitoring so that the IT Operations can identify, diagnose, and help resolve issues before they impact your organization's end users.

To set up application monitoring, use the following guidelines:

Installing agents for automatically discovered applications

After your system administrator installs and configures the App Visibility server components and TrueSight Presentation Server, you install App Visibility agents for Java, or App Visibility agents for .NET, or both, on the application servers of your web application.

App Visibility agents for Java require you to update Java options according to the application server type, and to grant Java 2 permissions to the App Visibility agent. For details, see the Configuring App Visibility agents for Java after installation Open link topic.

After you install the agents, open the TrueSight console (the Administration > App Visibility Agents page) to verify that they are running.

App Visibility Agents page in the TrueSight console

For details, see Viewing App Visibility agent status and properties.




Installation resources for automatically discovered applications

App Visibility server components Open link

TrueSight Presentation Server Open link

App Visibility agents for Java Open link

App Visibility agents for .NET Open link




Examining automatically discovered applications

Soon after you install the App Visibility agents, data is displayed in the TrueSight console. Examine the automatically discovered applications through the Configuration > Applications page. For details, see the following topics:


Examine the discovered applications and events periodically to ensure that the data that is important and relevant to you and your applications is reflected in the results.

Consider the following needs of your environment and make adjustments as needed:

  • How many requests are run on the monitored server? How many of the requests have breaches or errors?
  • How many breaches are for memory or CPU (which send events more frequently)?

You might have the adjust the heap size or modify the database retention settings:

Modifying automatically discovered applications

You can make the following adjustments to automatically discovered applications to influence the data that you collect and see in the TrueSight console.

Modifying application discovery

Automatic application discovery is driven by the way end users access and request services from your business applications. End users access the web application through a URL, and App Visibility provides a way to name applications by identifying common URL construction and patterns.

You can configure application discovery so that you can group requests with a common purpose under one application name, and separate requests with different purposes accordingly. For details, see Configuring application discovery.

Modifying event thresholds

In the TrueSight console, you can configure performance and availability event thresholds based on service-level agreement (SLA) parameters to ensure that you meet your obligations for user satisfaction. You can also configure if you want to receive notification for performance and availability events. Threshold settings apply to all transactions in an automatically discovered application or application with end-user monitoring.

You can set the levels of events for application performance and availability:

  • Minor, indicating a possible problem
  • Critical, indicating that the problem requires immediate attention.

For details, see Configuring event thresholds (SLAs) for automatically discovered applications.

Tranaction tab of the Application Configuration page in the TrueSight console

Modifying agent policies

A policy defines how the App Visibility agent behaves and operates. While you can control some of the agent functionality by configuring event thresholds (SLAs), agent policies provide you with a way to fine tune or change data collection methods to better suit your environment.

Modify the agent policy to make the following adjustments:

  • Concealing sensitive data recorded by the App Visibility agents
  • Reducing the number of similar requests
  • Adjusting the percentage of sampled requests: Agent overhead
  • Collecting data for stack traces that exceeded thresholds
  • Persisting tagged transactions
  • Disabling end-user monitoring in App Visibility


Changes to any of the parameters in the policy files can have a sizable impact on the footprint of the App Visibility agent and on the App Visibility collector’s scalability and database size. BMC recommends consulting with App Visibility support before changing any of the parameter values.

For details, see Configuring an App Visibility agent policy to collect and monitor application information.

Creating manual applications

With BMC TrueSight Infrastructure Management, you can manually create applications in the TrueSight console by creating application models. Manual applications can include the following components:

  • Groups and devices that are synchronized from Infrastructure Management 
  • Devices that are synchronized from App Visibility Manager
  • Manually created groups
  • Application discovered by manually setting up end-user monitoring

The status of a manual application is based on the event conditions that are specified with the application nodes.

When you create an application, you add devices or groups to the application model. The devices or groups that you add are displayed as nodes model. You can connect the nodes and establish their hierarchy. When you click a node in the application model, details of the node are displayed in a configuration pane at the bottom of the page

For details, see Creating an application manually.


Installation resources for manual applications

Infrastructure Management components Open link

TrueSight Presentation Server Open link

Adding synthetic transaction monitoring to an application

You can monitor synthetic transactions to predict application health and user experience. Synthetic transaction monitoring enables you to manage the performance and reliability of your applications by executing complex business transactions and monitoring performance and functional behavior.

Install the BMC Synthetic Transaction Execution Adapter (TEA) Agent and Borland Silk Performer Software Development Kit on each server. Together, these components schedule and run your scripts, which contain one or more application transactions.

For details about configuring applications for synthetic transaction monitoring, see Synthetic transaction configuration workflow.

Installation resources for synthetic transaction monitoring

Transaction Execution Adapter (TEA) Agent Open link

Borland Silk Performer Software Development Kit documentation Open link

Setting up dashboards for application monitoring

After you install and configure all the application monitoring components and start collecting data, you can set up dashboards to provide end-to-end visibility for IT Operations operators. As the application specialist, you know which applications and which metrics you want to pay special attention. You can create dashboards Open link and share or copy Open link them with operators.

For example, you can create a dashboard for a single application, showing dashlets with information about the application's performance and availability. The dashboard can include one or more of the following dashlets:

You can also create a dashboard that shows the status of all your applications, which can include one or more of the following dashlets:


Oops, it seems that you need to place a table or a macro generating a table within the Table Filter macro.

The table is being loaded. Please wait for a bit ...

Dashlet templateDescriptionContent categoryPrerequisite product

Application Client Breakdown dashlet

Displays the average application end-to-end time or number of hits, by browser type or platform. You select one or all applications with App Visibility end-user monitoring and the specific metrics you want to display. You can see a breakdown of how end users are accessing your application and the average response time for each client.

Application MonitoringApp Visibility Manager

Application Health - Synthetic dashlet

Displays key performance indicators for applications with synthetic executions that are monitored by App Visibility Manager. You can see the following metrics:
  • Availability Errors
  • Latency Violations
  • Impacted Executions
  • Number of Executions
Application MonitoringApp Visibility Manager

Application Server Health dashlet

Displays key performance indicators for application servers that are monitored by App Visibility Manager. You select an application server on which an App Visibility agent for Java or .NET is installed. You can see the monitored applications that use this server, and graphs of the following metrics:

  • Number of hits
  • Percentage of latency violations and errors
  • Percentage of server CPU usage
  • Amount of server memory usage
Application MonitoringApp Visibility Manager

Application View dashlet

Monitors the health and performance of live traffic and synthetic executions of an application. You select an application monitored by App Visibility Manager and you can see the current status of each tier in the application. Select a tier to drill down to relevant data in the Application View.

Application Monitoring


App Visibility Manager

Applications dashlet

Displays the state of the applications that you select. You can select specific applications from a list, or select applications based on your specified criteria, such as severity and importance.

Application Monitoring App Visibility Manager or Infrastructure Management

Applications Overview - Synthetic dashlet

Displays a view of the performance of up to 15 applications with synthetic transactions. It displays a timeline of the applications' status. The status is based on the status of synthetic transactions

The following options are available.

  • Static—the dashlet displays data for up to 15 applications that you select.
  • Rule Based—the dashlet displays up to 15 applications that meet the criteria that you select.
  • Single application—If you select a single application in the dashboard Global Filter, the dashlet shows data for that application only.

Application Monitoring 

App Visibility Manager

Impacted Users or Executions dashlet

Displays the number of impacted real users compared to the total number of users over the last 24 hours.

To display impacted real users, you select an application with App Visibility real-user monitoring .

Note: Do not use the Impacted Executions option of the dashlet. The Impacted Executions option has been deprecated.

Application MonitoringApp Visibility Manager

Top Real Transactions dashlet

Displays the most impacted (by latency or by errors), or most used, real transactions for applications monitored by App Visibility Manager. You select the type of transaction data you want to monitor, and whether to monitor one application or all applications.

Application MonitoringApp Visibility Manager