forked from docs/internal-documentation
Compare commits
1 Commits
| Author | SHA1 | Date | |
|---|---|---|---|
| a581cbaf92 |
|
Before Width: | Height: | Size: 66 KiB After Width: | Height: | Size: 66 KiB |
@ -5,5 +5,5 @@ SDMoD Overview
|
||||
.. toctree::
|
||||
:maxdepth: 1
|
||||
|
||||
look_and_feel_before/index
|
||||
look_and_feel_after/index
|
||||
look&feel_before/index
|
||||
look&feel_after/index
|
||||
@ -4,7 +4,7 @@ Create a new incident
|
||||
After the login, the menu bar looks like the following:
|
||||
|
||||
.. image:: ../images/menu2.png
|
||||
:target: /internal-documentation/_images/menu2.png
|
||||
:target: /_images/menu2.png
|
||||
:alt: Menu after login
|
||||
|
||||
There is an additional option, which is called “Open new incident”
|
||||
@ -12,7 +12,7 @@ There is an additional option, which is called “Open new incident”
|
||||
If you click on it, the following view will appear:
|
||||
|
||||
.. image:: ../images/inc1.png
|
||||
:target: /internal-documentation/_images/inc1.png
|
||||
:target: /_images/inc1.png
|
||||
:alt: Overview New incident
|
||||
|
||||
|
||||
@ -81,7 +81,7 @@ Explanation of additional fields and options for Incident Impact “Scheduled Ma
|
||||
For a maintenance, the view looks like as follows:
|
||||
|
||||
.. image:: ../images/inc2.png
|
||||
:target: /internal-documentation/_images/inc2.png
|
||||
:target: /_images/inc2.png
|
||||
:alt: New Incident - details
|
||||
|
||||
In addition to the ones explained above, you have the following fields:
|
||||
@ -108,13 +108,13 @@ How to adjust a minor/major incident or an outage?
|
||||
An incident will look like as follows:
|
||||
|
||||
.. image:: ../images/public_inc1.png
|
||||
:target: /internal-documentation/_images/public_inc1.png
|
||||
:target: /_images/public_inc1.png
|
||||
:alt: published Incident
|
||||
|
||||
By clicking the title (in the example above “Service Impact on ECS”, you can edit/update the incident. The view will look like as follows:
|
||||
|
||||
.. image:: ../images/inc3.png
|
||||
:target: /internal-documentation/_images/inc3.png
|
||||
:target: /_images/inc3.png
|
||||
:alt: Adjust Incident
|
||||
|
||||
|
||||
@ -153,7 +153,7 @@ Go to the Menu, Event History and select the corresponding Incident.
|
||||
|
||||
|
||||
.. image:: ../images/inc4.png
|
||||
:target: /internal-documentation/_images/inc4.png
|
||||
:target: /_images/inc4.png
|
||||
:alt: Adjust Incident
|
||||
|
||||
|
||||
@ -171,7 +171,7 @@ In case an issue will come back, for example, you can reopen the incident.
|
||||
The Message will also be back on status dashboard and look like as follows:
|
||||
|
||||
.. image:: ../images/inc5.png
|
||||
:target: /internal-documentation/_images/inc5.png
|
||||
:target: /_images/inc5.png
|
||||
:alt: Reopen Incident
|
||||
|
||||
Incident changed: (end date has been changed)
|
||||
@ -181,11 +181,11 @@ In case a minor or major issue occured and was triggered by the system, the end
|
||||
**Example:** A minor incident occured during the night and the SDMoD do take care of it during the next business hours, the end date can be adjusted accordingly.
|
||||
|
||||
.. image:: ../images/inc6.png
|
||||
:target: /internal-documentation/_images/inc6.png
|
||||
:target: /_images/inc6.png
|
||||
:alt: Adjust end date of an inc
|
||||
|
||||
This will also be mentioned in the change log of the incident publicly:
|
||||
|
||||
.. image:: ../images/inc_change.png
|
||||
:target: /internal-documentation/_images/inc_change.png
|
||||
:alt: Changelog Incident
|
||||
:target: /_images/inc_change.png
|
||||
:alt: Changelog Incident
|
||||
@ -4,9 +4,9 @@ Look&feel before login
|
||||
.. toctree::
|
||||
:maxdepth: 1
|
||||
|
||||
look_and_feel_before
|
||||
look&feel_before
|
||||
regions_switch
|
||||
status_services
|
||||
menu/index
|
||||
|
||||
|
||||
|
||||
@ -3,8 +3,8 @@ The look & feel before login
|
||||
|
||||
Before logging-in, the screen will look like as follows:
|
||||
|
||||
.. image:: ../images/look_and_feel_before.png
|
||||
:target: /internal-documentation/_images/look_and_feel_before.png
|
||||
.. image:: ../images/look&feel_before.png
|
||||
:target: /_images/look&feel_before.png
|
||||
:alt: Look&Feel
|
||||
|
||||
There are various options, which will be explained in the next chapters.
|
||||
@ -0,0 +1,17 @@
|
||||
Component Availability
|
||||
---------------------------------------
|
||||
|
||||
The component availability shows the availability of each service each month.
|
||||
The services are categorized and split between eu-de and eu-nl.
|
||||
|
||||
The availability page is also directly reachable via https://status.otc-service.com/availability
|
||||
|
||||
The component availability is impacted by the following status:
|
||||
|
||||
+--------------------------------------+------------------------------------------------------------------------------+
|
||||
| Icon | Explanation |
|
||||
+======================================+==============================================================================+
|
||||
| .. image:: ../../images/outage.png | see explanation :ref:`Status of Services <status_services>` |
|
||||
| :target: /_images/outage.png | |
|
||||
| :alt: Outage | |
|
||||
+--------------------------------------+------------------------------------------------------------------------------+
|
||||
@ -9,5 +9,5 @@ https://status.otc-service.com/history
|
||||
An example is:
|
||||
|
||||
.. image:: ../../images/event_history.png
|
||||
:target: /internal-documentation/_images/event_history.png
|
||||
:alt: Event History
|
||||
:target: /_images/event_history.png
|
||||
:alt: Event History
|
||||
@ -49,13 +49,13 @@ The availability page is also directly reachable via https://status.otc-service.
|
||||
|
||||
The component availability is impacted by the following status:
|
||||
|
||||
+-------------------------------------------------------------+------------------------------------------------------------------------------+
|
||||
| Icon | Explanation |
|
||||
+=============================================================+==============================================================================+
|
||||
| .. image:: ../../images/outage.png | see explanation :ref:`Status of Services <status_services>` |
|
||||
| :target: /internal-documentation/_images/outage.png | |
|
||||
| :alt: Outage | |
|
||||
+-------------------------------------------------------------+------------------------------------------------------------------------------+
|
||||
+--------------------------------------+------------------------------------------------------------------------------+
|
||||
| Icon | Explanation |
|
||||
+======================================+==============================================================================+
|
||||
| .. image:: ../../images/outage.png | see explanation :ref:`Status of Services <status_services>` |
|
||||
| :target: /_images/outage.png | |
|
||||
| :alt: Outage | |
|
||||
+--------------------------------------+------------------------------------------------------------------------------+
|
||||
|
||||
|
||||
----------
|
||||
@ -4,5 +4,5 @@ Switch between regions
|
||||
Clients can easily switch between the services and check their availability by clicking the region:
|
||||
|
||||
.. image:: ../images/region_switch.png
|
||||
:target: /internal-documentation/_images/region_switch.png
|
||||
:alt: Switch regions
|
||||
:target: /_images/region_switch.png
|
||||
:alt: Switch regions
|
||||
@ -0,0 +1,41 @@
|
||||
.. _status_services:
|
||||
|
||||
Status of services
|
||||
------------------
|
||||
|
||||
The services can vary between the following status:
|
||||
|
||||
|
||||
+--------------------------------------+------------------------------------------------------------------------------+
|
||||
| Icon | Explanation |
|
||||
+======================================+==============================================================================+
|
||||
| .. image:: ../images/green.png | - All services are running fine |
|
||||
| :target: /_imags/green.png | |
|
||||
| :alt: Operational | |
|
||||
+--------------------------------------+------------------------------------------------------------------------------+
|
||||
| .. image:: ../images/blue.png | - A maintenance is planned or ongoing for a service |
|
||||
| :target: /_imags/blue.png | - A maintenance is triggered by the SDMoD |
|
||||
| :alt: Maintenance | |
|
||||
+--------------------------------------+------------------------------------------------------------------------------+
|
||||
| .. image:: ../images/yellow.png | - A minor issue occurred. The service is available but may have restrictions |
|
||||
| :target: /_imags/yellow.png | or slow response. |
|
||||
| :alt: Minor Issue | - A minor issue can either be triggered by the system autoamtically or |
|
||||
| | by SDMoD |
|
||||
| | |
|
||||
| | |
|
||||
+--------------------------------------+------------------------------------------------------------------------------+
|
||||
| .. image:: ../images/red.png | - A major issue occurred. The service may be available, but the |
|
||||
| :target: /_imags/red.png | responsiveness is affected and may lead to interruptions on customer side. |
|
||||
| :alt: Major Issue | - A major issue can either be triggered by the system autoamtically or by |
|
||||
| | SDMoD |
|
||||
| | |
|
||||
| | |
|
||||
| | |
|
||||
+--------------------------------------+------------------------------------------------------------------------------+
|
||||
| .. image:: ../images/outage.png | - A service is not available anymore at all. |
|
||||
| :target: /_imags/outage.png | - An outage can **only** be triggered by SDMoD. This will never happen |
|
||||
| :alt: Outage | automatically by the system |
|
||||
| | - **Only** outages are SLA relevant and do have impact to the component |
|
||||
| | availability |
|
||||
+--------------------------------------+------------------------------------------------------------------------------+
|
||||
|
||||
@ -1,17 +0,0 @@
|
||||
Component Availability
|
||||
---------------------------------------
|
||||
|
||||
The component availability shows the availability of each service each month.
|
||||
The services are categorized and split between eu-de and eu-nl.
|
||||
|
||||
The availability page is also directly reachable via https://status.otc-service.com/availability
|
||||
|
||||
The component availability is impacted by the following status:
|
||||
|
||||
+-------------------------------------------------------------+------------------------------------------------------------------------------+
|
||||
| Icon | Explanation |
|
||||
+=============================================================+==============================================================================+
|
||||
| .. image:: ../../images/outage.png | see explanation :ref:`Status of Services <status_services>` |
|
||||
| :target: /internal-documentation/_images/outage.png | |
|
||||
| :alt: Outage | |
|
||||
+-------------------------------------------------------------+------------------------------------------------------------------------------+
|
||||
@ -1,41 +0,0 @@
|
||||
.. _status_services:
|
||||
|
||||
Status of services
|
||||
------------------
|
||||
|
||||
The services can vary between the following status:
|
||||
|
||||
|
||||
+--------------------------------------------------------+------------------------------------------------------------------------------+
|
||||
| Icon | Explanation |
|
||||
+========================================================+==============================================================================+
|
||||
| .. image:: ../images/green.png | - All services are running fine |
|
||||
| :target: /internal-documentation/_images/green.png | |
|
||||
| :alt: Operational | |
|
||||
+--------------------------------------------------------+------------------------------------------------------------------------------+
|
||||
| .. image:: ../images/blue.png | - A maintenance is planned or ongoing for a service |
|
||||
| :target: /internal-documentation/_images/blue.png | - A maintenance is triggered by the SDMoD |
|
||||
| :alt: Maintenance | |
|
||||
+--------------------------------------------------------+------------------------------------------------------------------------------+
|
||||
| .. image:: ../images/yellow.png | - A minor issue occurred. The service is available but may have restrictions |
|
||||
| :target: /internal-documentation/_images/yellow.png | or slow response. |
|
||||
| :alt: Minor Issue | - A minor issue can either be triggered by the system autoamtically or |
|
||||
| | by SDMoD |
|
||||
| | |
|
||||
| | |
|
||||
+--------------------------------------------------------+------------------------------------------------------------------------------+
|
||||
| .. image:: ../images/red.png | - A major issue occurred. The service may be available, but the |
|
||||
| :target: /internal-documentation/_images/red.png | responsiveness is affected and may lead to interruptions on customer side. |
|
||||
| :alt: Major Issue | - A major issue can either be triggered by the system autoamtically or by |
|
||||
| | SDMoD |
|
||||
| | |
|
||||
| | |
|
||||
| | |
|
||||
+--------------------------------------------------------+------------------------------------------------------------------------------+
|
||||
| .. image:: ../images/outage.png | - A service is not available anymore at all. |
|
||||
| :target: /internal-documentation/_images/outage.png | - An outage can **only** be triggered by SDMoD. This will never happen |
|
||||
| :alt: Outage | automatically by the system |
|
||||
| | - **Only** outages are SLA relevant and do have impact to the component |
|
||||
| | availability |
|
||||
+--------------------------------------------------------+------------------------------------------------------------------------------+
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user