Environment variables
Configuration
The Vight SDKs share the same service identity, routing, and ingest configuration.
Configuration model
Configuration has two jobs: it tells Vight where telemetry should be sent, and it gives every emitted signal the same service identity. Stable identity is what makes Services, Traces, Logs, Runtime, Releases, and Alerts line up during an investigation.
Set these values in the runtime environment before the SDK starts. Prefer deployment-managed secrets for ingestion keys and deployment-managed values for environment, version, and release identifiers.
Canonical environment variables
| Name | Required | Purpose |
|---|---|---|
| VIGHT_SERVICE_NAME | Yes | Logical service name shown in traces, services, logs, and metrics. |
| VIGHT_ENVIRONMENT | Recommended | Deployment environment such as production, staging, preview, or dev. |
| VIGHT_SERVICE_VERSION | Optional | Application version, package version, image tag, or release name. |
| VIGHT_DEPLOYMENT_ID | Optional | Deploy identifier used to compare behavior before and after releases. |
| VIGHT_INGESTION_KEY | Yes | Project ingestion key from Vight settings. |
| VIGHT_OTLP_ENDPOINT | Yes | Vight OTLP HTTP endpoint. Use the hosted ingest endpoint for production. |
| VIGHT_ORG_ID | Optional | Organization identifier for explicit telemetry routing. |
| VIGHT_PROJECT_ID | Optional | Project identifier for explicit telemetry routing. |
Production baseline
VIGHT_SERVICE_NAME=checkout-api
VIGHT_ENVIRONMENT=production
VIGHT_SERVICE_VERSION=1.0.0
VIGHT_DEPLOYMENT_ID=deploy_2026_06_24
VIGHT_INGESTION_KEY=...
VIGHT_OTLP_ENDPOINT=https://ingest.vight.dev
VIGHT_ORG_ID=...
VIGHT_PROJECT_ID=...Identity discipline
Changing a service name or environment splits history. Use stable names that match ownership, and use version or deployment values when you need release-level comparison instead of renaming the service.