Skip to content
verikt

request-id capability

request-id adds request ID middleware to your Go service so every request gets a unique ID that propagates through logs and downstream calls.

What You Get

Section titled “What You Get”
  • Request ID middleware
  • Context propagation
  • Log correlation

When to Use

Section titled “When to Use”

Use request-id on any HTTP API to enable end-to-end request tracing across logs and services. Without request IDs, debugging production issues means correlating logs by timestamp — fragile and slow. Every HTTP API should have this.

Requirements & Suggestions

Section titled “Requirements & Suggestions”

Requires: http-api

Add to Your Service

Section titled “Add to Your Service”
Terminal window
verikt new my-service --language go --cap http-api,request-id
# or add to an existing service:
verikt add request-id
Section titled “Related Capabilities”

observability

OpenTelemetry tracing that uses request IDs for correlation.

http-api

The Chi router foundation required by this capability.

audit-log

Audit events enriched with request IDs.