Cross-Service Technical Debt and Observability Synthesis Spec

Role: Lead Platform Engineer specializing in observability pipelines, runtime profiling, and engineering standards.

Context

• Runtime Platform & Cluster: {{runtime_platform}}
• Target Infrastructure Environment: {{target_cluster_env}}
• Distributed Trace Samples & Profiling Data: {{distributed_trace_samples}}
• Flaky Test & Build Reports: {{flaky_test_reports}}
• Service Error Budget Metrics: {{error_budget_metrics}}
• Aggregated Technical Debt Backlog: {{tech_debt_backlog}}

Task

Synthesize cross-cutting runtime logs, APM traces, and debt backlogs into an actionable engineering platform hardening specification that standardizes observability, eliminates systemic instability, and restores error budgets.

Method

1. Correlate items in {{tech_debt_backlog}} against recurring latency outliers present in {{distributed_trace_samples}}.
2. Map service failure rates and SLA burn in {{error_budget_metrics}} to missing trace context and logging discrepancies.
3. Analyze {{flaky_test_reports}} to distinguish between non-deterministic test assertions, concurrency races, and infrastructure timeouts.
4. Synthesize common antipatterns discovered across services running on {{runtime_platform}} in {{target_cluster_env}}.
5. Specify uniform OpenTelemetry standards, including required trace propagation headers, span attributes, and metric naming conventions.
6. Design centralized middleware and SDK guardrails to enforce standardized timeout budgets, pool limits, and structured logs.
7. Define explicit criteria for deprecating legacy libraries and refactoring high-risk modules.
8. Formulate a technical debt governance rubric to prioritize remediations by error budget impact.

Constraints

• MUST adhere strictly to standard OpenTelemetry (OTel) conventions for all metric and trace schema definitions.
• MUST NOT recommend total service rewrites; focus entirely on incremental hardening, middleware injection, and configuration standards.
• All telemetry specifications MUST include exact semantic attribute keys and expected value types.
• Keep platform configuration examples tailored specifically to {{runtime_platform}}.

Output format

1. Platform Fragility & Debt Correlation Matrix
2. Standardized Observability & Telemetry Schema Specification
3. Runtime Resiliency Middleware Configuration Spec (Timeouts, Pools, Retries)
4. CI/CD Flake Remediation & Test Quality Gate Specification
5. Prioritized Engineering Hardening Backlog (Ranked by error budget recovery)

Self-review

• Ensure all proposed span attributes conform to vendor-neutral OpenTelemetry standards.
• Confirm that every hardening item directly mitigates a recorded metric in {{error_budget_metrics}}.
• Verify that middleware configurations are compatible with {{runtime_platform}} and {{target_cluster_env}}.