- pnpm monorepo: apps/api (Fastify + SQLite + SSE), apps/web (React+Vite), packages/shared, packages/pi-adapter - Local auth (admin/webhook-runner roles) + Keycloak JWT ready - Multi-session chat with reliable history (user persisted before LLM, assistant persisted after stream) - Markdown knowledge base with /api/docs/search + /api/docs/:id - YAML webhook catalog with backend-only execution, retry/backoff, audit (webhook_runs), and per-user rate limit - Skills config (sre-on-call, blameless-postmortem, security-incident) injected into LLM system prompt - LLM provider failover chain (config/models.yml fallback + LLM_FALLBACK_CHAIN override) - Context-aware webhooks panel + backend id-mention safety net - Per-message stats (time/duration/tokens/model), Markdown+GFM render, code & table copy/download buttons - Vitest suite, end-to-end smoke test (scripts/smoke.mjs), per-session system prompt override - /metrics Prometheus endpoint + /api/metrics JSON, request-id correlation - dotenv with explicit repo-root path; envString/envNumber helpers (handles empty-string env) - Runbooks + SOPs under knowledge/ in English; README, docs, and INDEX.md in English
24 lines
461 B
Markdown
24 lines
461 B
Markdown
---
|
|
title: Log Reading SOP
|
|
tags: [logs, sops, troubleshooting, observability]
|
|
owner: sre
|
|
updated: 2026-06-05
|
|
---
|
|
|
|
# Log Reading SOP
|
|
|
|
## Goal
|
|
|
|
Retrieve the last N lines of a service log in under 30 seconds.
|
|
|
|
## Procedure
|
|
|
|
1. Identify the service and the log path.
|
|
2. Call the `log-tail` webhook with `service` and `lines`.
|
|
3. Look for error patterns (ERROR, CRITICAL, stack traces).
|
|
4. If there is a matching runbook, follow it.
|
|
|
|
## Related webhooks
|
|
|
|
- log-tail
|