gRPC API reference

HopMetric exposes a single gRPC service for ingestion. All calls are made over TLS to connect.api.hopmetric.net:443 using HTTP/2.

Service

Property	Value
Endpoint	`connect.api.hopmetric.net:443`
Service	`opentelemetry.proto.collector.trace.v1.TraceService`
Transport	gRPC over HTTP/2, TLS 1.2+
Auth	`x-api-key` metadata header

Methods

Export (client-streaming)

Streams batches of OTLP ResourceSpans, ResourceMetrics and ResourceLogs to the server. The server returns a partial-success summary per batch.

rpc Export(stream ExportRequest) returns (ExportResponse);

Check (unary)

Returns the serving status of the ingest pipeline for the authenticated key.

rpc Check(CheckRequest) returns (CheckResponse);

Example

grpcurl -H "x-api-key: $HOPMETRIC_API_KEY" \
  connect.api.hopmetric.net:443 \
  opentelemetry.proto.collector.trace.v1.TraceService/Check

The ingest path /opentelemetry.proto.collector.trace.v1.TraceService/ only accepts application/grpc. Browsers and HTTP/1.1 clients receive a gRPC status error, not HTML — this is expected for a gRPC endpoint.