Documentation
HopMetric accepts telemetry over the OpenTelemetry Protocol (OTLP) on a single gRPC endpoint. This section covers connecting a collector or SDK, authenticating, and the service contract.
All ingestion uses gRPC over TLS on port 443. The endpoint speaks HTTP/2 and expects the
application/grpc content type. Plain HTTP/1.1 requests to the ingest path are rejected.How it works
Your collector opens a long-lived HTTP/2 connection to eu-central-b.api.hopmetric.net:443 and streams OTLP messages to the IngestService. HopMetric acknowledges each batch and applies flow control so your agents never outrun the server.
Regional endpoints
Ingest terminates at the endpoint closest to your collector. Any endpoint accepts traffic from anywhere; the regional ones simply cut round-trip time. All of them present the same service contract and the same API keys, so switching is a one-line config change.
| Endpoint | Location | Role |
|---|---|---|
connect.api.hopmetric.net | Frankfurt, DE | default, used when no region is set |
eu-central-b.api.hopmetric.net | Frankfurt, DE | secondary EU capacity — this host |
eu-west.api.hopmetric.net | Dublin, IE | regional |
us-east.api.hopmetric.net | Ashburn, VA | regional |
ap-southeast.api.hopmetric.net | Singapore, SG | regional |
Endpoints are independent. If one is unreachable, point your collector at another
and replay from the agent's local buffer — batches are idempotent, so a replay after a failover
does not duplicate data.
Next steps
- Quickstart — send your first spans in five minutes.
- Authentication — create and scope API keys.
- gRPC API reference — the service and method contract.
- SDKs — language exporters and examples.