Operations tools

Recommended

• Use OpenTelemetry to instrument your code

  Recommended Open source

  Add traces, metrics and log context to your code with the OpenTelemetry API and SDK, and send them over OTLP to any backend.

• Use Prometheus for metrics

  Recommended Open source

  Store and query numeric metrics with Prometheus, and alert on them with its rules and Alertmanager.

• Use Grafana for dashboards

  Recommended Open source

  Build dashboards in Grafana, with each dashboard saved as JSON in the repository.

• Use JSON logs and Loki to store them

  Recommended Open source

  Write one JSON object per log line to standard output, and ship the lines to Loki or another store that searches by label.

• Use GlitchTip for error tracking

  Recommended Open source

  Send every unhandled server and browser error to GlitchTip through the Sentry SDKs, tagged with the release. Fix new errors before the next deploy.

• Use Uptime Kuma on another provider for uptime checks

  Recommended Open source

  Check your public addresses from outside with Uptime Kuma, run at a different provider from the app.

• Use PagerDuty for paging and keep schedules as code

  Recommended Paid

  Page people through PagerDuty, and keep its schedules, escalation policies and services in Terraform in your repository.

• Use pg_dump and pgBackRest for Postgres backups

  Recommended Open source

  Take a nightly pg_dump of every Postgres database, and add pgBackRest for point-in-time recovery once losing a day of data costs too much.

Optional

• Use Sentry only for features GlitchTip lacks

  Optional Source available

  Move from GlitchTip to Sentry only when you need a Sentry feature GlitchTip lacks, and name that feature in a decision record.

Avoid

• Avoid paging tools that are shutting down

  Avoid

  Do not start on Opsgenie or the open source Grafana OnCall, and move off them before they stop.