Knowledge Base

​

How it works

1. Write entries in Markdown — architecture docs, runbooks, troubleshooting procedures
2. Enable or disable individual entries with a toggle
3. Foggy uses them automatically — enabled entries are sent to the agent as context before every investigation

​

Two categories

​

Example entries

## Checkout Service
- Language: Go
- Database: PostgreSQL (primary + read replica)
- Dependencies: payment-service, inventory-service, user-service
- Deployment: 3 replicas in production, 1 in staging
- Owner: Platform Team (#platform-team in Slack)

• Use when: DNS resolution fails or services can’t reach each other

## Steps
1. Check CoreDNS pods: kubectl get pods -n kube-system -l k8s-app=kube-dns
2. Check CoreDNS logs for errors
3. Verify service DNS: nslookup <service>.<namespace>.svc.cluster.local
4. Check if the issue is namespace-specific or cluster-wide
5. Escalate to: #platform-team

​

Writing effective entries

• One topic per entry — a focused “Payment Service Architecture” is more useful than a massive “Everything About Our System” doc
• Include escalation paths — add team names and Slack channels so Foggy can suggest who to contact
• Disable rather than delete — if an entry becomes outdated, toggle it off. Re-enable it when it’s relevant again.

​

Next steps