Monitoring and error analysis

Monitoring

We set up monitoring on the same tool we use for our own products — fewbase Infra Tracker, which we built and run ourselves.

• Uptime checks every 5 minutes, with escalating alert levels so a single blip doesn’t wake anyone up.
• SSL certificates: expiry, but also changes to the certificate chain or issuer that often come before an outage.
• Domain expiry, checked daily from the registry itself.
• Alerts in Telegram or email, plus a daily digest of everything that needs attention.
• Application-level signals where your stack supports them: error rates, slow endpoints, failed background jobs.

Error analysis

When something does go wrong, we work it through to the end:

1. Reproduce

We collect the logs, traces, crash reports and user reports and turn them into a reliable way to trigger the problem.

2. Root cause

We find the actual cause — not just the line that throws, but why the system got into that state.

3. Fix and guard

We fix it and add a test that would have caught it, so the same bug can’t quietly return with the next release.

4. Write-up

You get a short, blameless post-mortem: what happened, who was affected, what we changed, and what to watch for.

Good fit if you…

• learn about outages from customers or social media;
• have an error that “happens sometimes” and nobody has had time to chase down;
• let a certificate or a domain expire once and don’t want it to happen again;
• run several small sites or services and want one place to see if they’re all healthy.