14 lines
765 B
Markdown
14 lines
765 B
Markdown
# Observability-as-a-Service (Engineering Monitoring)
|
|
|
|
## Problem
|
|
Logs are overwhelming. You only notice issues when the system is already down.
|
|
|
|
## Instructions
|
|
1. **Aggregator:** Set up a lightweight log forwarder (like Vector or Promtail) to push logs to a central database (Postgres or Elasticsearch).
|
|
2. **Analytics:** Implement a background script that polls for error spikes or latency anomalies.
|
|
3. **RAG Context:** Inject your architecture documentation (READMEs, design docs) into the agent's context so it understands *what* service is doing *what*.
|
|
4. **Actionable Alerts:** When an anomaly occurs, use the agent to analyze the logs *in context* and provide a summary + suggested fix.
|
|
|
|
## Goal
|
|
Move from "Log Monitoring" to "Intelligent System Health".
|