marmulle/docsportal
1
0
Fork 0
forked from docs/docsportal
Code Pull Requests Activity

adding content to apimon data flow

Browse Source
This commit is contained in:
Hasko, Vladimir 2023-05-24 20:35:33 +00:00
parent 5648efa82b
commit 038cf0880d
3 changed files with 25 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
doc/source/internal/apimon_training/notifications.rst
View File

@ -13,8 +13,12 @@ Every stream contains topics based on the service type (if represented by
standalone Ansible playbook) and general apimon_endpoint_monitor topic which standalone Ansible playbook) and general apimon_endpoint_monitor topic which
contains alerts of GET queries towards all services. contains alerts of GET queries towards all services.
.. image:: training_images/zulip_notifications.png
If the error has been acknowledged on Alerta, the new notification message for If the error has been acknowledged on Alerta, the new notification message for
repeating error wont get posted again on Zulip. repeating error won't get posted again on Zulip.
Notifications contain further details which help to identify root cause faster Notifications contain further details which help to identify root cause faster
and more effectively. and more effectively.
@ -59,4 +63,3 @@ Th EpMon notification consists of several fields:
.. image:: training_images/zulip_notifications.png

2
doc/source/internal/apimon_training/training_images/apimon_data_flow.svg
View File

File diff suppressed because one or more lines are too long
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 324 KiB

After

Width:  |  Height:  |  Size: 321 KiB

19
doc/source/internal/apimon_training/workflow.rst
View File

@ -7,3 +7,22 @@ ApiMon Flow Process
.. image:: training_images/apimon_data_flow.svg .. image:: training_images/apimon_data_flow.svg
:target: training_images/apimon_data_flow.svg :target: training_images/apimon_data_flow.svg
:alt: apimon_data_flow :alt: apimon_data_flow
#. Service squad adds test scenario to github repository.
#. Scheduler fetches test scenarios from Github and add them to queue.
#. Executor plays Ansible test scenario playbooks. Up to 8 parallel threads are enabled
#. Test scenario which has finished is being removed from the thread and next
playbook in the queue is added to the free thread. The previous playbook is
added to the queue on the last position.
#. Test scenario statistics are stored in the Postgresql database.
#. Metrics from HTTP requests are collected by Statsd.
#. Collected metrics are stored in time-series database Graphite.
#. Grafana uses metrics and statistics databases as the data sources for the
dashboards. The dashboard with various panels show the real-time status of
the platform. Grafana supports also historical views and trends.
#. Breached thresholds as well as failed test scenarios result in generated
alerts on Alerta.
#. Notifications containing alert details are sent to Zulip
#. Every test scenario stores it's job output log into Swift object storage for further analysis and investigation.