Configuring event thresholds (SLAs) for automatically discovered applications

In the TrueSight console, you, as the application specialist, 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 whether to receive notification for performance and availability events. Threshold settings apply to each transaction entry point in an automatically discovered application or an application with end-user monitoring.

You can set the event thresholds for application performance and availability:

  • Set a Minor threshold to indicate a possible problem
  • Set a Critical threshold to indicate that the problem requires immediate attention
Monitored server metrics

In addition to application performance metrics, App Visibility monitors application server metrics, to help you understand factors that impact application performance and availability.

The thresholds determine when the system detects a Minor or Critical event on each transaction entry point: when the system displays the event in the TrueSight console and when notifications are sent. 

This topic presents the following sections:

Before you begin

Before you can configure event thresholds for automatically discovered applications, ensure the following:



The following video (2:55) shows you how to configure SLA thresholds for automatically discovered applications or an application with end-user monitoring.

Note

The video demonstrates version 10.5 and also applies to the current version.

https://youtu.be/VPEji3G1Esk



To configure performance and availability event thresholds

  1. From the TrueSight console navigation pane, select Configuration > Applications.
  2. Click the name of an automatically discovered application, or an application with end-use monitoring, for which you want to adjust the event thresholds.
  3. From the Application Configuration action menu, select Edit Application.
  4. Click the Transaction tab to set the event thresholds.
  5. To modify thresholds for performance, perform the following actions:

    1. For each transaction entry point, set the percentage of transactions with latency issues to trigger events.
    2. Select the severity at which the system sends notification about the event.
    3. Set the latency values for parts of the transaction.

    Performance threshold options

    OptionDescription
    Minor Threshold (%)

    For each transaction entry point, the percentage of transactions that exceed one or more performance thresholds, which generates a minor event

    Default value: 5%

    Critical Threshold (%)

    For each transaction entry point, the percentage of transactions that exceed one or more performance thresholds, which generates a critical event

    Default value: 10%

    Send Notification

    Determines if notification is sent, and if so, at what event severity:

    • Never
    • When minor or critical threshold is breached (Default)
    • When critical threshold is breached
    E2E Latency (ms)

    End-to-end time at which a user transaction is considered slow and users are impacted

    The E2E latency value must be greater than or equal to the largest latency value of Network, Server, or Database.

    Default value: 3500 ms

    Network Latency (ms)

    (Automatically discovered applications) Network time between the client and server that is considered slow and users are impacted

    Default value: 500 ms

    Server Latency (ms)

    (Automatically discovered applications) Server time, including the web server and application server, that is considered slow

    Default value: 2000 ms

    Database Latency (ms)

    (Automatically discovered applications) Database time that is considered slow

    Default value: 100 ms

  6. To modify thresholds for availability errors, perform the following actions:
    1. For each transaction entry point, set the percentage of transactions with errors to trigger events.
    2. Select the severity at which the system sends notification about the event.
    3. Set the HTTP Status Codes numbers, or number range, for which errors are monitored.

    Availability Errors threshold options

    OptionDescription
    Minor Threshold (%)

    For each transaction entry point, the percentage of transactions that have errors, which generates a minor event

    Default value: 5%

    Critical Threshold (%)

    For each transaction entry point, the percentage of transactions that have errors, which generates a critical event

    Default value: 10%

    Send Notification

    Determines if notification is sent, and if so, at what event severity:

    • Never
    • When minor or critical threshold is breached (Default)
    • When critical threshold is breached
    HTTP Status Codes

    Code numbers for the HTTP errors that you want to monitor

    Enter number ranges, individual codes, or both, separated by a comma, for example, 400-450,500-550,308

    Default: 400-599

  7. Click Save.

Where to go from here

When your application setup and configuration is complete, you are ready to start Monitoring applications.

Related topics

Configuring application discovery

Editing an application's synthetic settings

Monitoring and managing events from the TrueSight console

Was this page helpful? Yes No Submitting... Thank you

Comments