Platform services

Monitoring

The Monitoring service keeps a constant watch on everything you ship. It runs scheduled health checks against your deployments and reports each result back to Dreambase, so issues surface before you feel them.

What it does

This is the service behind Dreambase's promise of around-the-clock reliability. On a schedule, the Dreambase API dispatches a HEALTH_CHECK event for each deployment to the Monitoring service. The service pings the deployment's URL, measures the outcome, and reports the status code, response time, and a human-readable message back to Dreambase — which updates the deployment's health in the app.

Built on NestJS

Monitoring is a NestJS application. Its ping module exposes a single webhook and responds immediately, performing the actual check in the background so the webhook stays fast.

Integration

The Monitoring service is powered by a single integration:

Endpoint

POST/ping/webhook
Run a health check & report the result

How a check works

  1. Dreambase sends a HEALTH_CHECK event containing the target url (which may be an environment-variable reference), an optional timeoutSeconds (default 10), and the service, deployment, and environment context.
  2. The service resolves any environment reference in the URL by calling back into the Dreambase API with its scoped token.
  3. It pings the resolved URL, honoring the timeout, and records the status, HTTP status code, and response time.
  4. It reports the result back to Dreambase, which updates the deployment's health and metrics.

Events it handles

  • WEBHOOK_CHALLENGE — echo the challenge to verify the endpoint.
  • HEALTH_CHECK— ping a deployment's URL and report its status, status code, and response time.

Health you can see at a glance

Results from the Monitoring service feed the health indicators on every deploymentin the app, so the same signal that drives alerting also drives the dashboards you watch. This is the “watched around the clock” layer described on dreambase.dev.