code-check-observability-coverage

To find missing logging and error handling in new server endpoints, run an observability coverage audit on changed code. It detects logging gaps, swallowed errors, and missing correlation IDs, producing a severity-ranked findings report with file and line references.

To check if PII is leaking into application logs, audit changed code for observability coverage gaps. The audit specifically scans for PII leakage in logs within modified server entry points and background jobs, reporting findings by severity.

Yes, the observability audit detects the repo's existing logger and error reporter. It provides read-only, logger-aware guidance that matches your current setup without auto-instrumenting or modifying your code.

The best way to review observability coverage for background jobs is to run a change-scoped audit. It focuses on newly added or modified critical paths, identifying missing latency metrics, structured logging gaps, and error reporting issues.

Avoid automated instrumentation when you need a safe, read-only assessment first. This audit produces a severity-ranked findings report of observability gaps without auto-instrumenting, guiding manual follow-up work on critical paths and error flows.