All features
gRPC monitoring

gRPC monitoring with the standard health check

An open port doesn't mean a gRPC service works. A gRPC check calls the standard health service, grpc.health.v1, the same one Kubernetes and load balancers use, and is up only when the server answers SERVING.

The real answer, not an open port

A server that's wedged or reports NOT_SERVING because its database is down fails the check, even though the port still accepts connections.

One service or the whole server

Leave the service empty to check the server as a whole, or name one, like shop.v1.Cart, to watch it on its own.

Errors that say what to fix

Alerts tell UNIMPLEMENTED from NOT_FOUND from a proxy that doesn't pass gRPC through, and hint when the TLS setting doesn't match the server.

Certificate expiry included

The certificate's expiry is read from each TLS check, with warnings 14, 7 and 1 day before, like on a website.

What is gRPC monitoring?

gRPC services don't serve web pages, so a website check can't see them, and a TCP check only proves the port is open. A gRPC monitor calls the standard health service, grpc.health.v1.Health/Check, on a schedule. If the server answers SERVING within 10 seconds, it's up. Anything else, from NOT_SERVING to a connection that never opens, is down and alerts your team.

It's the same health service that Kubernetes probes, Envoy and cloud load balancers can use, so if your servers already register it there's nothing to add.

Checking one service or the whole server

Leave the service name empty to ask about the server as a whole. If one server hosts several services and reports each on its own, enter the full name, like shop.v1.Cart, and the monitor only goes down when that service does. Names are case-sensitive and include the package.

For servers behind authentication, add metadata such as authorization: Bearer … and it's sent with every call. Public endpoints use TLS; tick plaintext for a server that speaks HTTP/2 without it.

Errors that point at the fix

When a check fails, the alert names the reason in plain words: the server doesn't have the health service (UNIMPLEMENTED), it doesn't know the service you named (NOT_FOUND), it says NOT_SERVING, it wants credentials, or a proxy in front answered with HTTP 502 or a web page instead of passing gRPC through. When the TLS setting doesn't match the server, the alert says which way to change it.

A failed check is retried and confirmed from other regions before it counts, so a dropped connection doesn't page anyone. The certificate's expiry is read from each TLS check, with warnings before it runs out.

How to set it up

  1. 1Make sure the server registers the health service; most gRPC libraries include it in a line or two.
  2. 2Click Add monitor and choose gRPC.
  3. 3Enter the host and port, like api.example.com:443. Optionally add a service name, and metadata such as an authorization token.
  4. 4Tick plaintext only if the server has no TLS. Pick how often to check and save.

The details

Calls
grpc.health.v1.Health/Check, over HTTP/2 with TLS, or plaintext (h2c)
Counts as up
The health service answers SERVING within 10 seconds
Counts as down
NOT_SERVING or UNKNOWN, any gRPC error, a non-gRPC reply, a TLS or connection failure, or a private address
Metadata
Up to 20 entries, such as authorization, sent with each call
Check interval
5 min to 1 hour on Free; 1 min on Starter; 30 s to 1 hour on Pro
Plan
All plans, including Free

Questions

What if my server doesn't have the health service?
The check fails with UNIMPLEMENTED. Adding it is a few lines in Go, Python, Java, .NET and Node; until then, a TCP port check is the fallback.
Do I need to upload my .proto files or turn on reflection?
No. The health service's messages are standard, so the check needs nothing from your server but the health service itself.
Does it work behind a load balancer or Cloudflare?
Yes, as long as it passes gRPC through over HTTP/2. If a proxy answers instead, the alert says it got HTTP 502 or an HTML page rather than a gRPC reply.
Can I check a gRPC server on my private network?
No. Checks run from the public internet and private addresses are blocked. Use Kubernetes' built-in gRPC probes inside the cluster.

Set up gRPC monitoring in under a minute

Included on the Free plan. No card needed.

Create a free account