docsportal/doc/source/internal/sd2_training/status_dashboard_frontend.rst

Status Dashboard 2 Frontend

The web based frontend of the SD2 provides public (and internal, after authentication) status information of OTC cloud services across all configured regions. It supports these features:

• Displays the service health through five service status.
• Authentication by OpenID connect (which in turn is connected to the OTC LDAP directory).
• Several service are grouped into categories.
• Regions - several services are existing in regions.
• Incidents - entry about issues affecting certain regions and certain services.
• Support of all OTC environments
• Incident data is available through an API.
• RSS notification (for the OTC mobile app and other integrations).
• SLA view of the services.
• Incident history.

Two Status Dashboard portals are available:

• public status dashboard: https://status.cloudmon.eco.tsi-dev.otc-service.com/
• hybrid status dashboard: https://status-ch2.cloudmon.eco.tsi-dev.otc-service.com/

Service Health View

From the architecture POV Status Dashboard is a Flask based web server serving API and rendering web content with a PostgreSQL database. The project source is available at https://github.com/stackmon/status-dashboard

Configuration of the status dashboard frontend is located at github: https://github.com/opentelekomcloud-infra/stackmon-config/blob/main/sdb_prod/catalog.yaml The catalog.yaml file contains definitions of the service name, service type, service categories and regions.

Example of AutoScaling service entry in SD catalog:

- attributes:
    category: Compute
    region: EU-DE
    type: as
  name: Auto Scaling
- attributes:
    category: Compute
    region: EU-NL
    type: as
  name: Auto Scaling

SLA view

SLA view https://status.cloudmon.eco.tsi-dev.otc-service.com/sla is calculated only from the "outage" service health status and provide 6 months SLA history of each service.

Details how to work with incidents are described on the incidents <sd2_incidents> page.