rhaas3/internal-documentation
1
0
Fork 0
forked from docs/internal-documentation
Code Pull Requests Activity

fixing image references

Browse Source 
Reviewed-by: otcbot <otcbot@t-systems.com>
Co-authored-by: Hasko, Vladimir <vladimir.hasko@t-systems.com>
Co-committed-by: Hasko, Vladimir <vladimir.hasko@t-systems.com>
This commit is contained in:
Hasko, Vladimir 2024-10-10 07:39:28 +00:00 committed by zuul
parent ac578d1baa
commit 3bd7da070b
6 changed files with 29 additions and 29 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
doc/source/status_dashboard/SDMoD/look&feel_after/new_incident.rst
View File

@ -4,7 +4,7 @@ Create a new incident
After the login, the menu bar looks like the following:
.. image:: ../images/menu2.png
:target: /_images/menu2.png
:target: /internal-documentation/_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: /_images/inc1.png
:target: /internal-documentation/_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: /_images/inc2.png
:target: /internal-documentation/_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: /_images/public_inc1.png
:target: /internal-documentation/_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: /_images/inc3.png
:target: /internal-documentation/_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: /_images/inc4.png
:target: /internal-documentation/_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: /_images/inc5.png
:target: /internal-documentation/_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: /_images/inc6.png
:target: /internal-documentation/_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: /_images/inc_change.png
:alt: Changelog Incident
:target: /internal-documentation/_images/inc_change.png
:alt: Changelog Incident

2
doc/source/status_dashboard/SDMoD/look&feel_before/look&feel_before.rst
View File

@ -4,7 +4,7 @@ The look & feel before login
Before logging-in, the screen will look like as follows:
.. image:: ../images/look&feel_before.png
:target: /_images/look&feel_before.png
:target: /internal-documentataion/_images/look&feel_before.png
:alt: Look&Feel
There are various options, which will be explained in the next chapters.

14
doc/source/status_dashboard/SDMoD/look&feel_before/menu/component_availability.rst
View File

@ -8,10 +8,10 @@ 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: /_images/outage.png | |
| :alt: Outage | |
+--------------------------------------+------------------------------------------------------------------------------+
+-------------------------------------------------------------+------------------------------------------------------------------------------+
| Icon | Explanation |
+=============================================================+==============================================================================+
| .. image:: ../../images/outage.png | see explanation :ref:`Status of Services <status_services>` |
| :target: /internal-documentation/_images/outage.png | |
| :alt: Outage | |
+-------------------------------------------------------------+------------------------------------------------------------------------------+

4
doc/source/status_dashboard/SDMoD/look&feel_before/menu/event_history.rst
View File

@ -9,5 +9,5 @@ https://status.otc-service.com/history
An example is:
.. image:: ../../images/event_history.png
:target: /_images/event_history.png
:alt: Event History
:target: /internal-documentation/_images/event_history.png
:alt: Event History

14
doc/source/status_dashboard/SDMoD/look&feel_before/menu/menu.rst
View File

@ -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: /_images/outage.png | |
| :alt: Outage | |
+--------------------------------------+------------------------------------------------------------------------------+
+-------------------------------------------------------------+------------------------------------------------------------------------------+
| Icon | Explanation |
+=============================================================+==============================================================================+
| .. image:: ../../images/outage.png | see explanation :ref:`Status of Services <status_services>` |
| :target: /internal-documentation/_images/outage.png | |
| :alt: Outage | |
+-------------------------------------------------------------+------------------------------------------------------------------------------+
----------

4
doc/source/status_dashboard/SDMoD/look&feel_before/regions_switch.rst
View File

@ -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: /_images/region_switch.png
:alt: Switch regions
:target: /internal-documentation/_images/region_switch.png
:alt: Switch regions