Skip to content
Fluid Attacks Development Portal

Status

Public Oath

  1. The status page is available at status.fluidattacks.com.

Architecture

Architecture-light Architecture-dark

Architecture for service status monitoring is divided in two main components.

Website

  1. The website is status.fluidattacks.com.
  2. It is powered by Atlassian Statuspage.
  3. It is maintained manually as it does not have a Terraform provider.
  4. It shows the health status of Fluid Attacks components and third party dependencies to the general public.
  5. It sends notifications to email subscribers when disruptions occur.
  6. It allows to publish detailed information regarding incidents like root causes, mitigation strategies, etc. This task is performed by an assigned developer.

Automated checks

  1. Automated checks are powered by Checkly.
  2. They are managed as code using Terraform.
  3. There are several checks:
  4. When a check fails, developers receive an alert by SMS and Email, and an incident is automatically published on the Statuspage.

Contributing

Please read the contributing page first.

General

  1. To post an incident or manage Statuspage settings, you must be added as a team member and log in to the Statuspage hub.
  2. Statuspage team members can quickly post incidents by clicking on the Create incident button in the main screen’s center.
  3. Once the incident is created, the user can manage the incident through multiple options such as updates, states, components and more.
  4. When the incident is closed, the user can click the button Write postmortem next to the respective incident in the registry to provide further details about the incident to the subscribers.