Data Monitoring / Alerting & Observability Design
Observability: Log metric trace correlation
Operators cannot connect a latency alert to the requests that caused it. Compare service identity, time ranges and correlation identifiers across signals.
Environment and inputs: Platform-neutral monitoring design with Prometheus and OpenTelemetry examples; syntax and signal availability depend on the deployed stack.
Failure scenario
Operators cannot connect a latency alert to the requests that caused it. Confirm the cause before choosing a fix.
Evidence to collect
Compare service identity, time ranges and correlation identifiers across signals. Record the time, affected scope and a healthy comparison interval.
Fix the confirmed cause
Standardize correlation fields and retain links from aggregate symptoms to bounded detailed evidence. Write the expected result first. Change one relevant setting at a time.
Check the result and hand over
Repeat the check for log metric trace correlation using the same scope and a representative interval. Check that the symptom is resolved, expected records are present and downstream results are correct. If coverage, correctness or latency worsens, restore the recorded configuration through the agreed rollback process.
Scope and precautions
Prefer read-only access and limit queries to the relevant period or dataset. This example has not been tested on your systems. Test changes in an approved environment. Keep credentials and sensitive data out of shared evidence.