Skip to main content
Version: Next

Overview

Once your server is written, the work shifts from building features to running them. This section covers what you need after deployment: seeing what the server is doing, proving to a host that it is healthy, securing the traffic it accepts, and finding out when something breaks.

Everything here works the same whether you deploy to Serverpod Cloud or host it yourself, though the two differ in how much is set up for you.

What each page covers​

  • Logging: what the server records for every call, where those records go, and how to keep the log tables from growing without bound.
  • Health checks: the HTTP endpoints a host calls to decide whether your server is alive and ready for traffic, plus the metrics Serverpod collects about itself.
  • Security and TLS: how traffic to your server is encrypted, and when you need to configure that yourself.
  • Exception monitoring: reporting exceptions to a monitoring service as they happen. This one is an experimental API.
  • Configuration: the config files and environment variables every setting on these pages is read from.
  • Sessions: the object that produces most of what ends up in your logs.
  • Caching: storing values in server memory or Redis.
  • Run code on shutdown: cleanup work when the server stops.
  • Insights: the companion app for reading logs and metrics.