Pegasii: Monitoring and Alerting as Code

Hello YC!

Pegasii aims to make it dead simple to add Monitoring and Alerting (MnA) to your projects. Configuration is done by way of YAML files, easily checked into version control and applied much like other "as code" tooling. It'll be free to host on your own (Pegasii is a single binary), and of course we plan on providing a hosted version for a subscription fee. Regardless of where you host or how large your monitoring needs grow, you'll be able to use the same config files everywhere, allowing Pegasii to aid your product with minimal friction as it grows from a single developer to many teams.

I'm building Pegasii to address shortcomings that I've encountered in the past. When I worked at a popular restaurant reservation company we had MnA defined across several tools. One tool did use files that could be versioned and checked-in, but at the end of the day it was a bunch of fragile hand-escaped SQL queries and curl commands wrapped in Bash scripts. The other tools were defined in various GUIs, such as Grafana and Kibana, and it was difficult to know which rules were defined where. Change management and auditing just didn't exist. Changes to teams occasionally resulted in incidents with unmonitored inboxes getting the alerts. Pegasii aleviates these issues by having entirely declarative monitors defined in a central location.

On a few instances I've worked at smaller companies where MnA consisted of a single Pingdom account (or they had no MnA at all). While convenient for checking website uptime, it's just not going to trigger an alert for important business metrics like low user signup rate or if a certain API endpoint misbehaves. Small companies that don't care about change management will probably rely on the Pegasii dashboard - which will export config files once the company is ready. The simple interface of Pegasii will hopefully encourage earlier MnA implementation during a project's lifetime.

Pegasii is still under development and a public beta is in the works. If you would like to be a part of the public beta then please drop your email address in the signup form on the webpage. I'll also be checking out your replies - I'd love to know what you love and hate about your existing solution.