marmulle/internal-documentation
1
0
Fork 0
forked from docs/internal-documentation
Code Pull Requests Activity
internal-documentation/doc/source/apimon/apimon_training/workflow.rst
tischrei 0618989a8a hc_ops 
Reviewed-by: Gode, Sebastian <sebastian.gode@t-systems.com>
Co-authored-by: tischrei <tino.schreiber@t-systems.com>
Co-committed-by: tischrei <tino.schreiber@t-systems.com>
2024-02-22 14:55:55 +00:00

1.3 KiB
Raw Permalink Blame History

ApiMon Flow Process

apimon_data_flow

  1. Service squad adds test scenario to github repository.
  2. Scheduler fetches test scenarios from Github and add them to queue.
  3. Executor plays Ansible test scenario playbooks. Up to 8 parallel threads are enabled
  4. 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.
  5. Test scenario statistics are stored in the Postgresql database.
  6. Metrics from HTTP requests are collected by Statsd.
  7. Collected metrics are stored in time-series database Graphite.
  8. 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.
  9. Breached thresholds as well as failed test scenarios result in generated alerts on Alerta.
  10. Notifications containing alert details are sent to Zulip
  11. Every test scenario stores it's job output log into Swift object storage for further analysis and investigation.