probed.devDashboard

gRPC Monitors

A gRPC monitor calls the standard gRPC health checking service. The target must implement that protocol; this check does not invoke arbitrary application RPC methods.

Configuration

Choose gRPC, enter the host and port, and optionally select the service name whose health should be checked. An empty service name asks for overall server health.

Choose the connection mode offered by the editor: TLS, plaintext, or TLS without certificate verification. Use verified TLS for production endpoints. Disabling certificate verification means a successful check does not validate the server certificate.

Configure request metadata when your health service requires it, then select the schedule, locations, timeout, and optional degraded threshold. A non-serving health response is a failure even if the connection itself succeeds.