obs-logs
The answer is in the logs — find error spikes, read them over time, correlate one request across services, compare before/after a deploy. Backends: Splunk (SPL), Loki (LogQL), and Cloud Logging on GCP — the reference teaches the dialect. Triggers: 'search the logs', 'why are there 500s', 'write a log query', 'follow this correlation id'. Ownership map only: obs-metrics owns metrics, obs-dashboards owns dashboard design, grafana owns Grafana operations, and obs-alerting owns alert design. Deciding what a live page means or what to do next belongs to incident-investigation, which routes query work here.
Pinned to revision 8d7ecda1ebc6, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/obs-logs/SKILL.md
- skills/obs-logs/references/gcp-logging.md
- skills/obs-logs/references/indexes.md
- skills/obs-logs/references/logql.md
- skills/obs-logs/references/query-catalog.md
- skills/obs-logs/references/spl.md
Every link opens the file at its source, pinned to the revision this page describes.