Page tree

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

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

Warning

If you set the Synthetic field to OFF, all synthetic configurations for the application, including all execution plans, are deleted.

This topic presents the following sections:

Before you begin

To perform these procedures, you must have Application Administration Open link -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.

Tip

Use application discovery rules to control which applications are displayed, thereby reducing agent overhead by ignoring applications at the agent level.

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.

    Unable to render {include} The included page could not be found.

  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.

Note

If you recreate a deleted device or group, and you use the same name, the existing node is not restored. You must delete the previous node and add the new one.

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.

Related topics

Viewing managed applications

Creating an application manually

Manually setting up active end-user monitoring