Public Oath

Architecture

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. AutoAutomated checks are powered by Checkly.
2. They are managed as code using Terraform.
3. There are several checks:
1. Platform: an authenticated GraphQL query to Fluid Attacks’ platform API that verifies the response body.
2. Agent: an authenticated GraphQL query to Fluid Attacks’ platform API that verifies the response body from the Agent.
3. Web: a web-browser-based check that verifies the home page is loading.
4. Docs: a web-browser-based check that verifies the documentation is loading.
4. When a check fails, developers receive an alert by SMS and Email, and an incident is automatically published on the Statuspage.
   

Contributing

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.

Tip

To expand the information about incident management, please refer to the Incidents section.

Tip

Have an idea to simplify our architecture or noticed docs that could use some love? Don't hesitate to open an issue or submit improvements.