Building ifnot200

There are many monitoring tools out there and plenty of status dashboards as well. Depending on the size of the project, it makes sense to setup observability platforms, scrape metrics, gather traces and have on call staff. Other projects, you can get away with the customer telling you something is down (some internal tools barely need 1 9 of uptime let alone 2). Small projects that do need some reliability need something else.

ifnot200 is a simple monitoring tool. You point it at a URL and if the return code isn't what is expected (usually 200) then we trigger an event. For most users that will be at least an alert (email, Slack, etc) but we can also trigger the ifno200 service running on the customers server.

The ifnot200 agent will execute whatever command has been provided. Has PHP crashed again? ifnot200 -c "systemctl restart php-fpm",

I'm keeping pricing simple just like our tooling, nothing kills a project faster than unneeded complexity.

It's early days for ifnot200 but it's already monitoring my own and my customers services.

As always, I appreciate any feedback or if you want to reach out, I'm @neuralsandwich on twitter and most other places.