All monitor types
Protocol

gRPC monitoring

Health-check a gRPC service, or call a specific unary method — with service discovery to build the request.

Every gRPC monitor runs on the same spine as the rest of PulseTrace — probed from each region you pick, scored on every check, and streamed into one timeline where incidents open on their own, anomalies surface without a threshold to guess, and reports are generated for you. Point it at a target, choose an interval, and it's watched.

What each check verifies

  • grpc.health.v1.Health check, or a unary RPC to a chosen method
  • Service/method discovery to scaffold the request body
  • Per-call latency and status

The panel on the right is the real create-monitor screen — it fills itself in with a gRPC example, exactly what you'd type.

When to use it

For gRPC services: internal microservices exposed through a gateway, public gRPC APIs, anything with server reflection. It discovers services via reflection, calls a unary method with the request you provide and asserts on the response — real functional coverage, not a TCP connect.

What an alert looks like

orders.OrderService/GetOrder is DOWN — UNAVAILABLE from us-east, eu-west; deadline exceeded after 3 s.

Plan availability

Every plan, including Free.

Compare plans →

Questions about gRPC monitoring

Does it need reflection enabled?
Reflection makes setup one click (PulseTrace discovers services and methods). Without it, you can still call a method by providing the request JSON and the full method name.
Is TLS supported?
Yes — plaintext or TLS, with the certificate checked the same way the TLS monitor does.