OpenTelemetry with VerOps — overview
How VerOps ingests OpenTelemetry traces, metrics and logs, the endpoint, and how telemetry becomes entities you can see.
What this is
VerOps speaks OpenTelemetry natively. Any OpenTelemetry SDK or Collector can send traces, metrics and logs straight into VerOps over OTLP — no proprietary agent required. This section is the contract: where to send data, how to authenticate, and — most importantly — which resource attributes turn your telemetry into the Servers, Containers and Services you see in the product.
The ingest endpoint
VerOps ingests OTLP over HTTP at the standard signal paths, behind TLS:
| Signal | URL |
|---|---|
| Traces | https://ingest.verops.io/v1/traces |
| Metrics | https://ingest.verops.io/v1/metrics |
| Logs | https://ingest.verops.io/v1/logs |
Most tools only need the base URL — https://ingest.verops.io — and append the signal path themselves. Both protobuf and JSON encodings are accepted.
Use HTTP, not gRPC. The public edge only exposes OTLP/HTTP on/v1/*. The Collector's gRPC port is not published on the internet, so set your exporter tohttp/protobuf. gRPC is fine only between your apps and a Collector you run yourself.
Authentication
Every request carries an API key in the Authorization header:
Authorization: Bearer ta_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxThe key identifies your organization (tenant) — you never send an org id or tenant attribute. Create a key under Settings → API Keys (see Quickstart). The key is shown once; store it as a secret.
From telemetry to entities
Once data is flowing, VerOps groups it into the entities you navigate by, using standard OpenTelemetry resource attributes:
| Set this resource attribute | …and VerOps shows it as |
|---|---|
service.name | A Service (APM / traces) |
host.name | A Server (Infrastructure → Servers) |
container.name | A Container (Infrastructure → Containers) |
k8s.* | Kubernetes context (namespace, pod, deployment, node) |
This mapping is the single most important thing to get right — it's covered in depth in Resource attributes & the VerOps entity model. Data with none of these attributes is still ingested and queryable in the Data Explorer, but it won't appear as a Server/Container/Service.
Where your data shows up
- Traces → the service map, APM, and trace search.
- Metrics → Metrics Explorer, dashboards, and — when the right resource attributes are present — the Infrastructure Servers and Containers tabs.
- Logs → log search and correlation with traces.
Next steps
- Quickstart — get a key and send data in five minutes.
- Resource attributes & the VerOps entity model — the attribute contract.
- Collector recipes — copy-paste configs for hosts, containers, Kubernetes and apps.
- Troubleshooting ingestion — "it returns 200 but I don't see it".