gRPC Monitor
Monitor gRPC services using the standard grpc.health.v1 health check protocol.
What is gRPC Monitoring?
gRPC monitoring uses the standard gRPC health checking protocol (grpc.health.v1.Health) to verify your microservices are operational. It's designed for cloud-native architectures and Kubernetes environments.
Technical Details
The monitor calls the Check method of the grpc.health.v1.Health service with an optional service name. A SERVING response indicates the service is healthy. It supports both insecure and TLS-encrypted connections.
Standard Health Check
Uses the official grpc.health.v1 protocol for compatibility
Service-Specific Checks
Check health of specific services within a gRPC server
TLS Support
Secure connections with TLS encryption
Microservices Ready
Designed for cloud-native and Kubernetes environments
| Option | Type | Required | Default | Description |
|---|---|---|---|---|
host | string | Required | - | gRPC server hostname and port (e.g., api.example.com:443) |
service_name | string | Optional | - | Service name to check (optional, checks overall health if empty) |
grpc_use_tls | boolean | Optional | false | Whether to use TLS encryption |
grpc_skip_tls_verify | boolean | Optional | false | Skip TLS certificate verification (not recommended in production) |
Best Practice
Implement the standard grpc.health.v1.Health service in your gRPC servers. This enables both internal Kubernetes probes and external monitoring.
Start Monitoring Today
Upgrade to Business to unlock this enterprise monitoring feature.