rhaas3/internal-documentation
1
0
Fork 0
forked from docs/internal-documentation
Code Pull Requests Activity
internal-documentation/doc/source/status_dashboard/sd2_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 Blame History

SD2 Data Flow Process

sd2_data_flow

  1. Service squad adds new data entries in GitHub repository for EpMon (service URL queries), adjusting flag and health metrics if required, and adds a service entry in the SD catalog.
  2. Cloudmon fetches public configuration from GitHub and internal configuration (credentials, certs, keys, ...) from a local repository place to generate the final configuration.
  3. EpMon plugin is executed and triggers HTTP requests as defined by the configuration.
  4. Metrics resulting by the HTTP requests are collected by Statsd.
  5. Collected metrics are stored in the time series database Graphite.
  6. The Metric Processor evaluates HTTP metrics from Graphite TSDB and generates new flag and health metrics based on defined rules and thresholds in configuration.
  7. Status Dashboard changes service health semaphore based on the resulting health metrics from the Metric Procesor.
  8. Grafana uses metrics and statistics databases as the data sources for the dashboards. The dashboard with various panels shows the real-time status of the platform. Grafana supports also historical views and trends.