pattern-engineer-observabilitylisted

# pattern-engineer-observability Terse rule list for writing observability code. **OpenTelemetry is the only instrumentation API**; vendor SDKs (Datadog, New Relic, Sentry, Honeycomb, Splunk, Elastic) appear only as OTLP backends behind the Collector — never as imports in `src/`. ## When to activate Activate whenever you add/edit/remove a log statement, span, metric, or trace-context propagation; scaffold observability for a service; touch `OTEL_*` env vars or the SDK bootstrap; wire (or remove) auto-instrumentation; or reach for `print` / `console.log` to "see what's happening" in a service path. Skip for local one-off `print` debugging in throwaway scripts or pure log-aggregation tooling that doesn't touch the app code path. ## Project memory overlay After loading this skill, also check `$MAIN_ROOT/.claude/memory/patterns/pattern-engineer-observability.md` in the consuming project (resolve `MAIN_ROOT="$(dirname "$(git rev-parse --path-format=absolute --git-common-dir)")"`). If present, load it as an **additive overlay** to the rules below; if absent, skip silently. See `memory-convention` for the full contract (additivity, severity floor, conflict surfacing). ## Rules ### Instrumentation surface - **OpenTelemetry only.** No `dd-trace`, `newrelic`, `@sentry/node`, `elastic-apm-node`, `splunk-otel` as direct imports. - **No `print` / `console.log` / `console.error` / `fmt.Println` / `System.out.println`** in committed code. Use the OTel-emitting structured logger. -