---
title: Monitoring Serverless (Lambda and friends)
description: Serverless means no servers to watch — and a few new things that can go wrong. Here's what to monitor when your code runs as functions: cold starts, duration, errors and throttles.
canonical: https://watchfor.io/blog/monitoring-serverless
---

[All posts](/blog) [Monitoring](/blog/category/monitoring) Feb 06, 2026 · 3 min read · WatchFor Team

# Monitoring Serverless (Lambda and friends)

Serverless means no servers to watch — and a few new things that can go wrong. Here's what to monitor when your code runs as functions: cold starts, duration, errors and throttles.

"Serverless" is a lovely promise: write a function, deploy it, and the platform runs and scales it for you — no servers to patch or watch. But "no servers to monitor" doesn't mean "nothing to monitor." It means the things to monitor change.

Functions have their own failure modes — cold starts, timeouts, throttling — and the usual server metrics (CPU, disk) don't apply. Here's what to watch instead.

## What's different about serverless

Traditional server Serverless function

Long-running process Spun up per request, then gone

Watch CPU/memory/disk Watch duration, invocations, errors

You manage capacity The platform scales it

Predictable warm state Cold starts when scaling up

Because functions are ephemeral, you can't "log into the box." You monitor the invocations and what the platform reports.

## The signals to watch

### Cold starts

When a function hasn't run recently (or is scaling up), the platform must initialise a fresh instance — a cold start — adding latency to that invocation. Too many cold starts mean a sluggish, inconsistent experience. Watch how often they happen and how much they add to [latency](/blog/latency-percentiles-p99).

### Duration (and timeouts)

Functions have a maximum duration ; exceed it and the invocation is killed. Watch execution time — especially the [p95/p99](/blog/latency-percentiles-p99) — and how close it runs to the timeout limit. A function creeping toward its limit is an outage waiting to happen.

### Errors and throttles

Signal Meaning

Error rate Functions failing (bugs, bad input, dependency failures)

Throttles The platform rejecting invocations past a concurrency limit

Invocation count Demand — and a proxy for cost

Throttling is the sneaky one: hit your concurrency limit and the platform starts rejecting requests, even though nothing is "broken." Watch for it.

### Cost

Serverless bills per invocation and duration, so a runaway loop or a traffic spike shows up directly on the bill. Monitoring invocation volume doubles as cost control.

## The blind spots to cover

Serverless monitoring has two gaps worth closing:

- The platform's own metrics lag and aggregate. They're useful but not always real-time per request. Pair them with [tracing](/blog/observability-vs-monitoring) for request-level insight.

- "Is the endpoint actually working for users?" Platform metrics can look fine while an API Gateway misconfig, a permissions error, or a cold-start storm degrades the real experience. So keep external [uptime/API checks](/blog/api-monitoring-guide) on your function-backed endpoints — synthetic checks from [multiple locations](/blog/global-monitoring-locations) are the ground truth.

## The bottom line

Watch Why

Cold starts Latency spikes when scaling up.

Duration Approaching the timeout = failures coming.

Errors & throttles Bugs, and rejected invocations at the concurrency limit.

Cost / invocations Runaway usage shows up on the bill.

External checks Confirm the endpoint works for real users.

Serverless removes the servers, not the need to watch. Track cold starts, duration, errors and throttles from the platform — then anchor it all with external checks on the endpoints your users actually hit.

Related: [API monitoring](/blog/api-monitoring-guide), [latency percentiles](/blog/latency-percentiles-p99), [observability vs monitoring](/blog/observability-vs-monitoring).

[#monitoring](/blog/tag/monitoring)[#serverless](/blog/tag/serverless)[#performance](/blog/tag/performance)

## Start monitoring your services today

WatchFor checks HTTP, DNS, SSL, ping, email and 20+ more — from around the world, with alerts to Slack, Discord, email and beyond.

[Learn more](/docs/monitors)[Start free](/auth/sign-up)

Share this article

---

Canonical page: https://watchfor.io/blog/monitoring-serverless · Site guide: https://watchfor.io/llms.txt