15 lines
1.7 KiB
Markdown
15 lines
1.7 KiB
Markdown
# Monitoring-Alert-Serverity-Definition_686073660
|
|
## Introduction
|
|
|
|
This document describes the current Alert serverity level definitions.
|
|
|
|
## Serverity Definition:
|
|
|
|
| | Serverity | Descrption | Example |
|
|
| --- | --- | --- | --- |
|
|
| | Critical | Critical issues that demand immediate attention. These incidents have a severe and widespread impact on services, leading to complete service outages or critical business functions being unavailable. | - Total service outage affecting all users. - Data loss with no immediate recovery option. |
|
|
| | High | High-priority issues requiring prompt attention. These incidents have a significant impact on operations but might not be as severe as S0. They need urgent resolution to minimize the impact on users and business processes. | - Major service degradation affecting a large subset of users. - Critical features experiencing issues. |
|
|
| S2 | Medium | Medium-priority issues that need attention, but may not require immediate action. These incidents have a noticeable impact on operations, but workarounds may be available. | - Partial service degradation affecting specific features or user groups. - Performance degradation impacting user experience. |
|
|
| S3 | Low | Low-priority issues that have minimal impact on operations. These incidents are typically non-critical and can be addressed in a scheduled manner. | - Minor bugs or cosmetic issues. - Non-urgent feature requests. |
|
|
| S4 | Information | Informational items or events that do not require immediate action. These may include notifications, alerts, or reports that provide insights into the system's health or performance. | - System usage statistics or trends. - Informational alerts for proactive monitoring. |
|