Page tree
Skip to end of metadata
Go to start of metadata

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 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.
Monitored server metrics

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

The level determines when the system detects a Minor or Critical event on the transaction, and when the system displays the event in the Application View. 

This topic presents the following sections:

Before you begin

Before you can configure event thresholds for

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. Define 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 thresholds for parts of the transaction.

    Performance threshold options

    OptionDescription
    Minor Level (%)

    The percentage of transactions that exceed one or more performance thresholds, which generates a minor event

    Default value: 5%

    Critical Level (%)

    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 level:

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

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

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

    Default value: 3500 ms

    Network (ms)

    (Automatically discovered applications) Network time that is considered slow and users are impacted

    Default value: 500 ms

    Server (ms)

    (Automatically discovered applications) Server time that is considered slow

    Default value: 2000 ms

    Database (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. Define 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 Level (%)

    The percentage of transactions that have errors, which generates a minor event

    Default value: 5%

    Critical Level (%)

    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 level:

    • Never
    • When minor or critical level is breached (Default) 
    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

Managing and monitoring events

 

 

1 Comment

  1.