carlos / platform Public

Push alerts: error spikes, failed wakes, email failures Feature Request open

carlos logs, carlos errors, carlos email status and carlos analytics are all pull. Somebody has to think to look.

Things ips has found only by looking:

  • an instance's first wake after a restart failing instance not healthy within 30s;
  • mail that stopped (the only proof mail works is somebody running carlos email test by hand);
  • an error group that started with a release.

Asking for alerts an owner subscribes to, by email or by webhook, for:

  • a new error group, or a spike in an existing one;
  • a failed wake, or an instance unhealthy for longer than N;
  • sending failures and bounce rates;
  • a certificate or domain falling out of health.

Related: #39 (per-app liveness in the aggregate feed).

--- Filed from the ips repository (Turnkey's insolvency practice system, built on rastrillo v0.26.0 and deployed on CARLOS), where this was worked around. Paths without a repository prefix are in ips.