Examples
Runnable Samples
Use the repository samples and starter snippets to validate telemetry before instrumenting a production service.
How to use samples
Samples are for validating a complete telemetry path before changing a production service. Run one sample with the same project endpoint and ingestion key you plan to use, then confirm that Vight shows the expected service, traces, runtime signals, and logs.
Treat a sample run as a controlled baseline. If the sample appears in Vight but your service does not, the project settings are likely correct and the next investigation should focus on service startup order, identity values, filters, or runtime-specific setup.
Repository samples
samples/aspnetcore-basic
Minimal ASP.NET Core service with Vight.AspNetCore.
samples/aspnetcore-grpc
ASP.NET Core gRPC service with Vight instrumentation.
samples/microservices
Checkout, billing, and inventory services for multi-service traces.
Run the ASP.NET Core basic sample
export VIGHT_INGESTION_KEY=...
export VIGHT_OTLP_ENDPOINT=https://ingest.vight.dev
dotnet run --project samples/aspnetcore-basic/AspNetCoreBasic.csprojValidate locally
VIGHT_VALIDATE_SMOKE=1 bash scripts/validate.shUse this smoke path to verify that the sample emits telemetry before you deploy it. After the command runs, open Services and Traces with a broad time range before narrowing by environment or service name.