forked from docs/internal-documentation
Compare commits
2 Commits
main
...
describe_s
| Author | SHA1 | Date | |
|---|---|---|---|
| 032e37c905 | |||
| e2e47c51fc |
@ -5,7 +5,7 @@ ApiMon Flow Process
|
||||
|
||||
|
||||
.. image:: training_images/apimon_data_flow.svg
|
||||
:target: /_images/apimon_data_flow.svg
|
||||
:target: training_images/apimon_data_flow.svg
|
||||
:alt: apimon_data_flow
|
||||
|
||||
|
||||
|
||||
Binary file not shown.
|
Before Width: | Height: | Size: 1.0 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 25 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 668 B |
Binary file not shown.
|
Before Width: | Height: | Size: 29 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 42 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 37 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 48 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 19 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 8.1 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 3.6 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 66 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 2.7 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 1.3 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 616 B |
Binary file not shown.
|
Before Width: | Height: | Size: 21 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 607 B |
Binary file not shown.
|
Before Width: | Height: | Size: 1.2 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 545 B |
@ -1,9 +0,0 @@
|
||||
######################
|
||||
SDMoD Overview
|
||||
######################
|
||||
|
||||
.. toctree::
|
||||
:maxdepth: 1
|
||||
|
||||
look_and_feel_before/index
|
||||
look_and_feel_after/index
|
||||
@ -1,10 +0,0 @@
|
||||
How to get a SDMoD login
|
||||
=======================================
|
||||
|
||||
In general, you can login via your keycloak generated user or your GitHub user.
|
||||
|
||||
In case you need to get access, please raise a ticket via "Internal Incident" towards Ecosystem squad:
|
||||
|
||||
https://jira.tsi-dev.otc-service.com/servicedesk/customer/portal/4
|
||||
|
||||
Master Component must be: ECOSYSTEM - Ecosystem
|
||||
@ -1,14 +0,0 @@
|
||||
===========================
|
||||
Look&Feel after login
|
||||
===========================
|
||||
|
||||
.. toctree::
|
||||
:maxdepth: 1
|
||||
|
||||
get_sdmod_login
|
||||
new_incident
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
@ -1,12 +0,0 @@
|
||||
Look&feel before login
|
||||
######################
|
||||
|
||||
.. toctree::
|
||||
:maxdepth: 1
|
||||
|
||||
look_and_feel_before
|
||||
regions_switch
|
||||
status_services
|
||||
menu/index
|
||||
|
||||
|
||||
@ -1,10 +0,0 @@
|
||||
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
|
||||
:alt: Look&Feel
|
||||
|
||||
There are various options, which will be explained in the next chapters.
|
||||
@ -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,13 +0,0 @@
|
||||
Event History
|
||||
---------------------------------------
|
||||
|
||||
The event history shows all past events, sorted by months.
|
||||
|
||||
A direct link exists:
|
||||
https://status.otc-service.com/history
|
||||
|
||||
An example is:
|
||||
|
||||
.. image:: ../../images/event_history.png
|
||||
:target: /internal-documentation/_images/event_history.png
|
||||
:alt: Event History
|
||||
@ -1,11 +0,0 @@
|
||||
######################
|
||||
The menu
|
||||
######################
|
||||
|
||||
.. toctree::
|
||||
:maxdepth: 1
|
||||
|
||||
menu
|
||||
event_history
|
||||
component_availability
|
||||
user_manual
|
||||
@ -1,68 +0,0 @@
|
||||
The menu
|
||||
---------------------------------------
|
||||
|
||||
.. image:: ../../images/menu.png
|
||||
:target: /internal-documentation/_images/menu.png
|
||||
:alt: The menu
|
||||
|
||||
The menu includes:
|
||||
|
||||
+---------------------------------+------------------------------------------------------------------------------+
|
||||
| Event History | The event history shows up all past events - even if minor, major issues, |
|
||||
| | outages, or maintenances. |
|
||||
+---------------------------------+------------------------------------------------------------------------------+
|
||||
| Component Availability | The component availability shows the availability of a service in the |
|
||||
| | previous months and is the basis for SLA calculation. |
|
||||
+---------------------------------+------------------------------------------------------------------------------+
|
||||
| User Manual | Link to the actual version of the user manual. |
|
||||
+---------------------------------+------------------------------------------------------------------------------+
|
||||
|
||||
|
||||
----------
|
||||
|
||||
|
||||
Event history
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
The event history shows all past events, sorted by months.
|
||||
|
||||
A direct link exists:
|
||||
https://status.otc-service.com/history
|
||||
|
||||
An example is:
|
||||
|
||||
.. image:: ../../images/event_history.png
|
||||
:target: /internal-documentation/_images/event_history.png
|
||||
:alt: Event History
|
||||
|
||||
|
||||
----------
|
||||
|
||||
|
||||
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 | |
|
||||
+-------------------------------------------------------------+------------------------------------------------------------------------------+
|
||||
|
||||
|
||||
----------
|
||||
|
||||
|
||||
User Manual
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
The user manual can also be reached directly via the following link:
|
||||
https://docs.otc.t-systems.com/status-dashboard/index.html
|
||||
@ -1,6 +0,0 @@
|
||||
User manual
|
||||
---------------------------------------
|
||||
|
||||
The user manual can also be reached directly via the following link:
|
||||
|
||||
https://docs.otc.t-systems.com/status-dashboard/index.html
|
||||
@ -1,8 +0,0 @@
|
||||
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
|
||||
@ -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 |
|
||||
+--------------------------------------------------------+------------------------------------------------------------------------------+
|
||||
|
||||
@ -6,4 +6,3 @@ Status Dashboard Internal Documentation
|
||||
:maxdepth: 2
|
||||
|
||||
sd2_training/index
|
||||
SDMoD/index
|
||||
|
||||
@ -14,9 +14,6 @@ Prerequistes for new demands
|
||||
- Functional testing must be completed by QA engineer in the service squad
|
||||
- Regression testing must exist and reports must be available
|
||||
|
||||
.. warning::
|
||||
Ecosystem Squad is not relying on pre-PROD nor checking features on pre-PROD therefore make sure that demanded feature has been released to PROD already.
|
||||
|
||||
Once the prerequistes are met and issue is created on github repository, Ecosystem squad needs several days or weeks based on the complexity of the new demand to accomplish the task.
|
||||
|
||||
To avoid delays caused by not enough resources, the new demands should be identified and addressed upfront during PIP planning by the service squads or product management.
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user