Getting started

Connect OpenTelemetry

Inkvo speaks OTLP natively over HTTP and gRPC. If your services already emit OpenTelemetry, you're a config block away. If they don't, instrument them once and every downstream tool benefits — not just Inkvo.

Two ways in

Most teams route through a collector (recommended): your services export to a local OTel Collector, and the collector fans out to Inkvo and anywhere else. Smaller setups export directly from the SDK.

Path	When to use	Endpoint
Collector (OTLP/HTTP)	You run a collector, or want one exporter to fan out	`https://ingest.inkvo.dev`
Collector (OTLP/gRPC)	High-volume trace pipelines	`ingest.inkvo.dev:4317`
Direct from SDK	One or two services, no collector	`https://ingest.inkvo.dev`

Direct from an SDK

Set the standard OTel environment variables — no Inkvo-specific SDK required.

environmentbash

OTEL_EXPORTER_OTLP_ENDPOINT=https://ingest.inkvo.dev
OTEL_EXPORTER_OTLP_HEADERS="authorization=ik_prod_b4f2…"
OTEL_SERVICE_NAME=payments-svc
OTEL_RESOURCE_ATTRIBUTES=deployment.environment=production

Set deployment.environment

This single resource attribute is how Inkvo separates prod from staging from dev — and how it picks the right tone for each. Always set it.

Tag your deploys

Narrative root-cause depends on knowing what changed. Send a deploy marker on every release so Inkvo can correlate a latency spike with the commit four minutes earlier.

ci/deploy.shbash

curl -X POST https://ingest.inkvo.dev/v1/deploys \
  -H "authorization: $INKVO_KEY" \
  -d '{"service":"payments-svc","sha":"3d9a1c","env":"production"}'