From 5031338e921e66a2ade35c490ba510169b8f7655 Mon Sep 17 00:00:00 2001 From: "Hasko, Vladimir" Date: Mon, 29 Apr 2024 19:47:21 +0000 Subject: [PATCH] Update 'doc/source/status_dashboard/sd2_training/incidents.rst' --- doc/source/status_dashboard/sd2_training/incidents.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/source/status_dashboard/sd2_training/incidents.rst b/doc/source/status_dashboard/sd2_training/incidents.rst index 3aa4ce2..5690ba4 100644 --- a/doc/source/status_dashboard/sd2_training/incidents.rst +++ b/doc/source/status_dashboard/sd2_training/incidents.rst @@ -21,7 +21,7 @@ The following states of the service can be shown on SD2: - Major Issue - brown "cross" mark icon - Service Outage - red "cross" mark icon -These 5 states can be set manually for specific service(s) during incident creation but only 2 states (Minor issue and Service Outage) are set automatically by the Metric Processor health metrics. +These 5 states can be set manually for specific service(s) during incident creation but only 2 states (Minor issue and Major issue) are set automatically by the Metric Processor health metrics. Incidents are visualized in the respective color scheme on the top of the SD page. Also it's possible to navigate to the related incident via clicking on the service state icon next to the service. Once the service health status is changed and incident is created there's no automated clean-up of the incident and incident must be handledl by respective SIM. Only after incident is closed the service changes its state back to "green" Operation state.