In the Operations Management console, you 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.
You can set the levels of events for application performance and availability:
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:
To modify thresholds for performance, perform the following actions:
Performance threshold options
Option | Description |
---|---|
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:
|
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) | Network time that is considered slow and users are impacted Default value: 500 ms |
Server (ms) | Server time that is considered slow Default value: 2000 ms |
Database (ms) | Database time that is considered slow Default value: 100 ms |
Availability Errors threshold options
Option | Description |
---|---|
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:
|
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, Default: 400-599 |
Click Save.
When your application setup and configuration is complete, you are ready to start Monitoring applications.
Configuring application discovery
Editing an application's synthetic settings
1 Comment
Sara Kamen