MONITORINGBY REQUEST

Know what broke before your users tell you.

The monitoring stack every one of our services runs on: metrics, logs and traces with dashboards and alerts, error tracking with release and source maps, and uptime checks from outside. Alerts are written once and cover every new service automatically.

Runs at monitoring.datacrash.io

What it does

/01

Metrics, logs and traces

Prometheus, Loki and Tempo behind Grafana dashboards, with every service and node collected from day one.

/02

Alerts that mean something

Rules written generically, so a new service or node is covered without a copy-pasted alert, routed to the people who act on them.

/03

Error tracking

Exceptions from servers and browsers grouped per route and release, with source maps, in a self-hosted, Sentry-compatible tracker.

/04

Uptime from outside

Health checks against the public addresses, so a service that is down, and therefore reports nothing, still raises an alarm.

/05

Backups that are checked

Backup jobs are watched for success and freshness of the data they copy, not only for having run.

/06

Single sign-on

Dashboards and the error tracker sign in through the same passkey SSO as everything else.

Who it is for

  • ↳Teams without an observability stack yet
  • ↳Anyone paying per seat or per event for tools they barely use

Start

Tell us what you need; we answer with a plan.

Write to info@datacrash.io. We reply with what we can do, how long it takes and what it costs.