Nest Engineering Docs
Handler

Operations

Deployments, SLOs, and monitoring for Handler

Deployments

  • Build from services/handler/Dockerfile.
  • The container runs granian against services.handler.main:app.
  • Default listen port is 8080 and honors the PORT environment variable.

Startup behavior

  • Loads HANDLER_SENTRY_DSN (optional) from Secret Manager.
  • Initializes Spanner client and warms the pool + index metadata.
  • Warms ezyVet proxy secrets cache.
  • Resolves PartnerCreds base URL via service discovery when unset.

Monitoring and alerts

  • Sentry is enabled when HANDLER_SENTRY_DSN is available.
  • Cloud Tasks headers are tagged in Sentry for traceability.
  • Pipeline name tags (pipeline.name) are set per request.

SLOs and SLIs

  • TBD. Define latency and error targets for pipeline execution.

Scaling and performance

  • Pipelines run with an execution timeout (PIPELINE_MAX_RUNTIME_SECONDS).
  • Long-running retries are escalated after TASK_ESCALATION_SECONDS.
  • Spanner writes use batch write chunking to remain under mutation limits.

Last updated on

Local development

Run, debug, and test Handler locally

Runbooks

Operational playbooks for Handler