|   PDF Documentation   |   PowerPacks   |   Release Notes   |   ScienceLogic Support   |   Contact Documentation


Monitoring Application Health

Download this manual as a PDF file

The Applications page was removed from the 8.14.0 release. All features on previous versions of this page are considered Beta and experimental.

This section describes how to use SL1 to monitor application health for your devices.

Application Health requires either the SL1 Extended architecture (for devices that use SL1 agents) or SL1 Maps on the Database Server, which is also called Maps on CDB (for devices that do not use SL1 agents). The "Extended" architecture uses a Central Database appliance and multiple storage and data nodes. For more information, see the Installation section. The "Maps on CDB" architecture uses the SL1 Maps images bundle installed on the Central Database appliance. For more information, see the Maps section.

Navigation tips for the SL1 user interface:

This section includes the following topics:

What is an Application?

An application is a collection of one or more devices running a similar set of software or processes. You can monitor the application health of that set of devices in SL1 to ensure that the software running on those devices is performing the actions the software is supposed to be performing. If you are using the SL1 agent or an agent-related PowerPack to collect data, you can monitor the system processes for a dynamic list of devices.

An application is made up of one or more application components and a status policy:

To navigate to the Applications page, click the Applications icon ():

Monitoring Application Availability, Health, and Risk

On the Applications page you can monitor the availability, health, and risk of your applications and application components. These three values display in the following format and order:

  1. Availability: Displays whether an application can be used. An application is considered unavailable if SL1 is not able to collect data from the application, or if the application is usable or not usable. A value of 0 means an application is unavailable, and a value of 1 means an application is available. Availability uses the following icons:

Image Availabilty icons

  1. Health: Displays a "severity" icon that represents a numerical value between 0 and 100, which indicates the current status of an application to show if its health is worsening or improving. In most cases, a higher value is preferred. Health uses the following icons by default:

Image of Health icons

  1. Risk: Displays a percentage value between 0 and 100 that indicates how close an application is to being in an undesirable state. In most cases, the safest possible risk value is 0%, while the worst risk value is 100%. Risk uses the following settings by default:

These values are computed in this order because SL1 uses Availability values to compute Health while SL1 uses both Availability and Health values to compute Risk.

The Application Investigator Page

When you select an application or an application component from the Applications page (), the Application Investigator page appears:

The Tabs on the Application Investigator Page

The Application Investigator page contains three tabs:

To view Root Cause Analysis information for a specific application component on an Application Investigator page, click the Actions icon () on the tile for that component. If the Root Cause Analysis option is enabled, you can review data related to troubleshooting for that component. For more information, see Using the Root Cause Analysis Feature.

The Info Drop-down on the Application Investigator Page

The Info drop-down at the top of the Application Investigator page displays the following: 

Click the Edit button to edit the content on all three tabs and to edit the fields on the Info drop-down. You can also edit the application or application component name and the icon associated with the application or component. Click Save to save your changes.