table of contents Table of contents
Docs / Traces open telemetry / Importing traces / HTTP vs grpc protocols
BETA

HTTP vs gRPC OpenTelemetry protocols

On this page

Checkly’s OTel ingestion endpoint supports both HTTP and gRPC protocols. The gRPC protocol is the “native” protocol for OTel, but in 2020 an alternative HTTP protocol was introduced due to some of the downsides gRPC has:

  • gRPC tends to come with bigger dependencies in your code base.
  • gRPC uses HTTP/2 as its transport layer, which might not be 100% supported in your network infra. Think firewalls, proxies and load balancers.

However, for larger payload and higher throughput scenarios, gRPC is the way to go. It’s more efficient and has a smaller connection overhead.

Different SDKs and languages have different levels of support for gRPC and HTTP. For example, the HTTP protocol is the default for Node.js, but gRPC is the default for Go. In all cases, we recommend using the default protocol for your language and SDK.

next Troubleshooting missing or orphan spans

Last updated on November 5, 2024. You can contribute to this documentation by editing this page on Github