Checkly
Last updated: Oct 30, 2026
Rationale
Checkly is the monitoring-as-code (MAC) tool of Fluid Attacks for check-based tracking of its products. It is a very important part of the continuous monitoring strategy of Fluid Attacks. With Checkly, Fluid Attacks can define and manage periodic tests for each of its components, and it always knows their state.
These are the primary reasons why Fluid Attacks selected it and not other alternatives:
- It gives a global network of testing locations. Thus, you can simulate user interactions from many geographical locations.
- It supports browser checks in a true browser. Thus, Fluid Attacks can test its web applications in a way that is very similar to user interactions.
- You can configure and manage all the monitoring setup and tests with Terraform.
- It gives dedicated API testing.
- It gives detailed metrics and information about the performance of the products of Fluid Attacks. Thus, it helps to find trends and areas to make better.
- It gives a public dashboard that shows the health and performance metrics of the components of Fluid Attacks. This feature helps transparency and communication.
- It has many integrations. Thus, Fluid Attacks can connect different parts of the stack to track failures, tell customers about the state of its components, and solve problems quickly.
- It lets you implement an advanced retry strategy to decrease false positives during monitoring.
Alternatives
Fluid Attacks examined these alternatives, but it did not select them for these reasons:
- Atatus Synthetic Monitoring: You cannot configure checks and tests with Terraform. Also, you cannot change the checks much, and they do not give good support for integrations with other services or tools.
- BetterStack: It does not have checks that interact directly with the browser. You cannot run the tests in more than one browser, and you cannot run the checks in parallel.
- DataDog: Its monitoring functions do not give more value than Checkly. Thus, if you use this tool only for this purpose, it is more expensive than its alternatives.
Usage
Fluid Attacks uses Checkly for these tasks:
- To set and run browser checks for its docs, platform, and website
- To set and run API checks for its API and the CI Gate
- To set and manage check groups
- To define retry strategies that prevent false positive check failures
- To make automatic incidents on its Statuspage when a check fails
- To set and show the public dashboard of the health of its components
- To tell the staff about each check failure through many channels
Fluid Attacks does not use Checkly for these tasks:
- Heartbeats: This is a new Checkly feature, and the team did not test it at this time.
- Maintenance Window: Because of the deployment frequency and workflow of Fluid Attacks, maintenance periods are not necessary.