Production Readiness

A monitor must be more reliable than what it monitors. But the paradox is that reliability 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 informed decisions about monitoring your databases with Blip.

v1.x

Blip v1.x is production ready.

Metric Collectors

Domain	Readiness
aws.rds	Production
innodb	Production
repl	Production
repl.lag	Production
size.binlog	Production
size.database	Production
size.table	Production
status.global	Production
stmt.current	Production
tls	New
var.global	Production
wait.io.table	Stable

Sinks

Sink	Readiness
chronosphere	New
datadog	Production
log	Production
prom-pushgateway	New
retry	Stable
signalfx	Production

Cloud

Feature	Readiness
AWS IAM auth	Stable
AWS Secrets Manager	New

General

Feature	Readiness
API	Stable
Heartbeat	Stable
Monitor Loading Stop-loss	New
Plan Changing	New
Plan Error Policy	Stable
Plan File	Production
Plan Table	New
Prometheus emulation	New