Editing application thresholds and configuration details

You can edit various aspects of an application, depending on how it came into the TrueSight console:

• For manually created applications, you can edit application details and the application model.
  
  • If synthetic transaction monitoring is enabled on the manually created application, you can edit Execution Plans and event thresholds for service-level agreements (SLAs).
  • If end-user monitoring is manually set up, you can edit event thresholds for SLAs
• For automatically generated applications, you can edit application importance and event thresholds for SLAs.

You can also activate and  edit, or deactivate synthetic transaction monitoring for manually created or automatically generated applications.

This topic presents the following sections:

Before you begin

To perform these procedures, you must have Application Administration -level access.

To edit application details

You can edit the name and description of a manually created application. You can change the level of importance and synthetic transaction monitoring for any application.

1. From the TrueSight console navigation pane, select Configuration > Applications.
2. On the Application Management page, click the row action menu icon next to the application you want to edit and select Edit.

3. On the Edit Application page, edit the following details:

   • For a manually created application, edit the name, description, or level of importance. You can also turn on or off synthetic monitoring.

   • For an automatically discovered application, edit the level of importance. You can also turn on or off synthetic monitoring.

   Note

   You cannot edit the Type and Status Computation Model fields.

4. Click Save at the bottom of the page.

To delete an application

You can delete an application so that it no longer is displayed in the TrueSight console. For example, if you change application discovery rules and an application is displayed that you no longer need, you can delete the application from TrueSight console. Likewise, if you uninstall App Visibility agents to stop monitoring an application, you can delete the application from the console.

1. From the TrueSight console navigation pane, select Configuration > Applications.
2. On the Application Management page, click the row action menu icon next to the application you want to edit and select Delete.
3. Confirm the deletion.

If the application is still active, it is displayed in the console, again, after the next heartbeat.

Editing a manually created application model

You can edit a manually created application model and add new devices or groups to the model. The new devices or groups that you add are displayed in the form of nodes in the application model. You can also change the hierarchy of existing nodes in the model. When you click a node in the application model, details of the node are displayed at the bottom of the page as shown in the following figure:

To add devices or groups to a manually created application model

This procedure describes how to add a device or a group to an application model.

1. Click the Configure Devices or the Configure Groups option.
2. In the Search for Devices or Add Groups box, enter the name of the device that you want to add or click Search to view all the devices or groups that you can add. Devices or groups that are already a part of the application model are indicated by a check box against their name.
3. Click OK.

To connect nodes in the application model

The nodes in application models are dependent on one another. When you create a model, you determine the dependency and whether the event status is propagated—that is, whether the status of a "lower" node influences the status of a "higher" node, and, ultimately, the status of the application. If you do not connect the nodes, or if events are not propagated, then the node status has no impact on the status of the application.

In an automatically created model, the nodes are automatically dependent and events are automatically propagated.

1. Select a device or group you want as a parent of another node.
2. In the node configuration pane below the model, select or clear child nodes under the Add/Remove Dependent Node(s) list.
3. If you want the event status of the child node to be reflected in the parent node, ensure that Enable Status Propagation is selected (it is selected by default). Otherwise, the status of the device is not reflected in the parent node.

4. If you select a group, you can select Enable the Group to be a Cluster, and then enter a value from 1 to 100 to calculate a quorum.

    Click here to see examples of the quorum algorithm.

   The CLUSTER option for Status Computation uses the QUORUM impact function, which is described as follows:
   
   When you create a quorum type of StatusModel, you can specify a percentage, called the quorum percentage. The quorum value is given by the quorum slot of the BMC_STATUS_COMPUTATION instance.
   
   The impact_status is the highest propagated_status that a quorum percentage of provider agrees on.
   
   An easy computation of the quorum status can be performed as follows:

   • There are n providers with propagated_status different from NONE: let i be the lowest integer that is greater than or equal to quorum* n /100.
   • Consider the array of propagated_status ordered from highest to lowest status.
   • The impact_status is the status corresponding to the element i of this array.

   Example

   
   CASE A website 1 (quorum-based component status computation)
   host1
   host2
   Example A1

   QUORUM=50, host1=OK, host2=IMPACTED

   
   50*2/100 = 1 => i = 1
   array = [IMPACTED, OK]
   The percentage of hosts that are not AVAILABLE is 50%, which breaches the quorum threshold, so the status of website 1 is IMPACTED.
   Example A2

   QUORUM=51, host1=OK, host2=IMPACTED 

   
   1 < 51*2/100 < 2 => q = 2
   array = [IMPACTED, OK]
   The percentage of hosts that are not OK is 50%, which does not breach the quorum threshold, so the status of website 1 is OK.
   Example A3

   QUORUM=51, host1=MINOR, host2=IMPACTED

   
   1 < 51*2/100 < 2 => q=2
   array = [IMPACTED, MINOR]
   There is indeed at least 51% of the providers (actually 100%) that state a severity at least MINOR, so the status of website 1 = MINOR
   CASE B website 2 (quorum-driven, impact-based component status computation)
   host1
   host2
   host3
   host4
   Example B1

   quorum_percent=30, host1=OK, host2=OK, host3=OK, host4=Minor

   
   1<30*4/100<2=>q=2
   array = [MINOR, OK, OK, OK]
   The percent of hosts that are not UNAVAILABLE is 25%, which is less than 30%, so the status of website2 is OK.
   Example B2

   quorum_percent=30, host1=OK, host2=OK, host3=UNAVAILABLE, host4=MINOR

   
   1 < 30*4/100 < 2 => q = 2
   array = [UNAVAILABLE, MINOR, OK, OK]
   There is at least 30% (actually 50%) of the providers that state a severity of at least MINOR, so the status of website 2 is MINOR.
   Example B3

   quorum_percent=60, host1=MINOR, host2=OK, host3=UNAVAILABLE, host4=UNAVAILABLE

   
   2 < 60*4/100 < 3 => q=3
   array = [UNAVAILABLE, UNAVAILABLE, MINOR, OK]
   There is at least 60% (actually 75%) of the providers that state a severity at least MINOR, so the status of website 2 = MINOR

5. Click Done and then click Save.

The device or group is now a part of the application model with its own child and parent nodes.

To delete a node from an application

If a device or group was deleted from the its source (from Infrastructure Management or from a group created in the console), an unknown node is displayed in a manually created application model. You can delete the node from the model.

This procedure describes how to delete a device or a group from an application model.

1. Select the device or group that you want to delete.
2. In the node configuration pane below the model, click Delete Node.
3. Confirm the deletion.
4. Click Done and then click Save.

Editing event thresholds for SLAs on automatically generated applications

You can edit an automatically generated application to set Minor and Critical thresholds to comply with service-level agreements (SLAs).

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

Editing synthetic transaction configurations

You can edit synthetic transaction configurations for automatically-generated and manually-generated generated applications. You can edit all of the settings such as SLAs, blackout periods, and Execution Plans.

For information, see Editing an application's synthetic settings.