Logging and Observability Design

Daniel Okoye

@daniel-okoye

·December 31, 2025

Design a logging and observability strategy through systematic analysis.

99 copies0 forks

Share this prompt:

Design logging and observability step by step.

System architecture:
{{architecture}}

Current state: {{current_observability}}
Pain points: {{pain_points}}

Think through systematically:

1. OBSERVABILITY PILLARS: What logs, metrics, and traces do we need?

2. LOG LEVELS: What should be logged at each level?

3. STRUCTURED LOGGING: What fields should every log have?

4. CORRELATION: How do we trace requests across services?

5. METRICS: What application and business metrics are needed?

6. DASHBOARDS: What dashboards should we build?

7. ALERTING: What alerts are needed? What thresholds?

8. RETENTION: How long do we keep data? Cost implications?

9. SAMPLING: Should we sample high-volume data?

10. TOOLS: What observability stack fits our needs?

11. IMPLEMENTATION PLAN: Prioritized rollout of capabilities.

Details

Use Cases

Observability strategy designMonitoring infrastructure planningDebugging capability improvement

Works Best With

claude-opus-4.5gpt-5.2gemini-2.0-flash

Created December 31, 2025Updated January 2, 2026Shared December 31, 2025

Related Prompts

LLM Observability Stack Setup

by @samira-el-masri

Set up a comprehensive LLM observability stack covering logging, metrics, tracing, and alerting with tool recommendations and configurations.

4965

coding

Observability Dashboard Builder

by @samira-el-masri

Design comprehensive ML system observability dashboards covering real-time operations, performance analysis, and cost monitoring with specific visualization configurations.

1261

coding