#monitoring.

You are an SRE and observability engineer. Design a comprehensive observability stack for [system type, e.g., "a microservices platform with 20+ services handling 50k req/min"]. Requirements: metrics, logs, traces, and alerting. Design decisions to cover: 1) Metrics — Prometheus vs Datadog vs CloudWatch (recommend one for this scale with cost analysis), 2) Logging — structured logging standards, ELK vs Loki vs Datadog Logs (trade-offs for this volume), 3) Distributed Tracing — OpenTelemetry instrumentation strategy, Jaeger vs Tempo vs X-Ray, 4) Dashboards — Grafana dashboard design: what to show in a Golden Signals dashboard (Latency, Traffic, Errors, Saturation), 5) Alerting Strategy — the RIGHT alerts to set (avoid alert fatigue): SLO-based alerting vs threshold alerting, PagerDuty/OpsGenie integration, 6) Cost controls — estimated cost at this scale and how to reduce cardinality. Language/framework: [describe]. Current blind spots: [describe what you cannot see today].

Act as a Project Problem Solver. I will provide a list of current project issues: [Issue List]. 1. Categorize each issue (Technical, Human Resource, Financial, Stakeholder). 2. Assign a 'Severity' (Low, Medium, High). 3. Propose an 'Owner' for each issue. 4. Suggest a 'Resolution Action' for the top 3 most severe issues. 5. Identify which issues should be escalated to the Project Sponsor.

Act as a Project Accountant. I will provide the total budget: [$Budget] and the spend to date: [$Spend] over [Number] months. 1. Calculate the 'Monthly Burn Rate'. 2. Calculate the 'Runway' (how many months of budget are left). 3. Project the 'Expected Total Spend' at the current rate. 4. Identify if the project will finish over or under budget. 5. Suggest 3 cost-saving measures if the burn rate is too high.