telemetry-foundations

Name spans with the pattern `<verb>.<resource>` in lowercase dot-separated tokens, such as `get.order` or `publish.order.created`. Name metrics as `<domain>.<entity>.<measure>`, like `http.server.request.duration`, and prefer official OTel semantic conventions where they exist.

Treat PII as default-deny using the denylist in references/pii-denylist.md. Apply a redaction strategy before emitting: hash fields that must remain joinable (SHA-256), drop credentials and payment data entirely, or tokenize values resolvable only through an access-controlled store.

No, the vocabulary is declarative and vendor-agnostic. It defines names and shapes aligned with the OpenTelemetry data model and assumes OTLP as the wire protocol, leaving the choice of SDK, exporter, and backend to the implementing team.

Bound high-cardinality dimensions like user IDs and request IDs at the source, or move them to trace exemplars and log attributes instead of metric dimensions. Every attribute on a metric multiplies the time-series count, so keep dimensions bounded.

Use a parent-based sampler by default so child spans inherit the sampling decision and traces remain whole. Where tail-based sampling is available in a collector, bias policies toward keeping error traces and a representative sample of successful traces.