SaaS Pro Max
Sign inStart free
Sign in

Uptime monitoring and application metrics

Know when an application is unavailable, slow or behaving differently. SaaS Pro Max combines worker-run uptime checks, SDK metrics and browser performance measurements with the error and trace context you need to investigate an incident.

Start freeRead the setup guide
Uptime and latency · last 30 daysDemonstration data
p95 response time by day
Datep95 ms
Aug 5, 2026184 ms
Aug 6, 2026179 ms
Aug 7, 2026188 ms
Aug 8, 2026176 ms
Aug 9, 2026168 ms
Aug 10, 2026165 ms
Aug 11, 2026191 ms
Aug 12, 2026186 ms
Aug 13, 2026194 ms
Aug 14, 2026205 ms
Aug 15, 2026231 ms
Aug 16, 2026212 ms
Aug 17, 2026188 ms
Aug 18, 2026183 ms
Aug 19, 2026179 ms
Aug 20, 2026176 ms
Aug 21, 2026182 ms
Aug 22, 2026188 ms
Aug 23, 2026174 ms
Aug 24, 2026169 ms
Aug 25, 2026181 ms
Aug 26, 2026186 ms
Aug 27, 2026192 ms
Aug 28, 2026187 ms
Aug 29, 2026183 ms
Aug 30, 2026172 ms
Aug 31, 2026168 ms
Sep 1, 2026179 ms
Sep 2, 2026184 ms
Sep 3, 2026181 ms
Uptime99.97%Healthy60s checks from the worker
  • healthysaaspro.devGET /142 ms
  • healthyIngestPOST /api/v1/ingest38 ms
  • warningWorker heartbeatspm.worker.job.durationqueue 41

Measure availability and real user performance

Configure uptime monitors for your services and review the results alongside browser Core Web Vitals. Synthetic checks tell you what a scheduled probe observed; browser measurements describe the visits that sent telemetry. Keeping both views together helps separate an unavailable endpoint from a slow user experience.

Ask a precise operational question

Send counters, gauges, histograms and timers from your SDKs. Track a queue's depth, a job's duration or the distribution of request latency. Filter by bounded labels such as service, region or route, then use the appropriate aggregate for the question instead of treating every metric as a simple average.

Turn a signal into an investigation

Alert rules open incidents and route notifications through configured channels. Connect on-call routing and SLOs when your workflow needs them. Errors, OpenTelemetry traces and structured logs live in the same application, giving operators places to investigate why an alert fired and which release or service was involved.

Put it to work.

Start with one application and verify the data you send.

  1. Enable the Metrics module and create a monitor for an endpoint you operate.
  2. Add SDK measurements or an OpenTelemetry exporter, using stable technical labels.
  3. Configure an alert and a notification channel, then verify the delivery and incident workflow.

A successful probe describes that check's time and location, not every user's experience. Notification delivery depends on channel configuration. Use bounded labels; customer IDs and unbounded request paths create unsuitable metric cardinality.

Module availability and retention vary by plan. Compare plans and limits.