DeferPanic provides next generation monitoring for software engineers.
While we are specifically targeting the go language currently we want
to be open towards others in the future.
The real mission is to eradicate the concept of reactive monitoring
and move towards a more proactive holistic view of a company's
Our target audience is other software engineers and the companies they
work for. This can be a small agency of 1-2 people all the way up to
an enterprise company with tens of thousands of employees.
While the majority of our audience is highly technical we want the
ability to appeal towards a non-technical userbase. We want to take
something that is highly technical and wrap it up in a package that is
intuitive and easy to understand and imparts lots of meaningful
Problems of existing monitoring systems:
* they require someone with lots of domain knowledge
* they require someone with lots of app specific knowledge
* they focus on the effects of a problem - not the problem itself
(ex: running out of memory vs. why it's happening)
These are the problems we are trying to solve.
Since our main audience are software engineers and they spend a lot of
time looking at dark screens with code in them - that's why our
current design reflects that. However, we are ok with whatever it
takes to communicate effectively the vision.
A quick note on the name - 'defer' and 'panic' are both keywords in
the go programming language. They are a play on words. Defer usually
entails cleaning something up and panic basically means all hope is
lost. So if you 'defer panic' you are basically saying something
really bad has happened but we are going to work around it regardless.