Observability
Log pipelines that stay searchable
Structure logs for investigations without drowning storage budgets.
4 weeks · 19h · Cohort · BRL 1.725 (informational)
Program narrative
Design ingestion, retention, and field naming so responders find needles without paying for haystacks forever.
What ships inside
- Field naming convention pack
- Retention tiering model
- Sampling for debug logs
- PII scrub checklist
- Structured vs unstructured tradeoff grid
- Investigation query cookbook
- Cost guardrail worksheet
Outcomes we expect you to demo
- Propose a retention tier with stakeholder sign-off
- Normalize fields for three high-churn services
- Run a cost review with before/after estimates
Mentor on point
Otávio Mendes
Observability mentor who still carries scars from noisy JSON blobs.
FAQ — including what we skip
We nod to SIEM routing but focus on engineering-owned pipelines.
Experience notes
“Investigation query cookbook is now pinned in our war room channel.”
— Tatiane · Sysadmin · Telco internal cloud · 5/5