DumbMonit
IntegrationsWebsites and web servers
gRPC service
Calls the standard gRPC health check (grpc.health.v1): catches a service that is up but reports itself unhealthy.
Product descriptions are in English, as in the product. The page labels follow your language.
What DumbMonit watches
Typical use. Microservice, etcd: the standard gRPC health check
Examples
- A gRPC microservice
- etcd
- A service behind Envoy or a service mesh
- Any server that registers grpc.health.v1
How it connects
No account needed.
Default port: 50051
Setup steps: Monitor a gRPC service
Check that the server registers the standard health service (grpc.health.v1.Health): most gRPC frameworks have a one-line helper for it.
In DumbMonit, enter the server with its port, for example grpc.home.lan:50051.
Tick Encrypted connection (TLS) for a server that requires it; the port then defaults to 443.
Optional: name a Service, to check its own health instead of the whole server's.
Heads-up. The check only sees what the health service reports: a server that always answers SERVING proves nothing about the methods behind it.