A monitor must be more reliable than what it monitors. But the paradox is that reliablity is only achieved through extensive real-world usage. Consequently, Blip is released with features at different levels of readiness:
New
Feature is new and not widely tested in the real world. Expect bugs. Ready for early adopters.
Stable
Feature seems stable in the real world, but it’s still considered new. There might be bugs. Ready for pre-production testing and burn-in.
Production
Feature has been running in the real world for several months. Bugs are not expected. Ready for production.
Feature readiness is documented here to help you make informmed decisions about monitoring your databases with Blip.