1Z0-1111-25 Cheatsheet — OCI Observability (Metrics, Logs, Traces)

Use this for last‑mile review. Pair it with the Syllabus.

1) Pick the right signal first

2) Alert rules (high-yield)

• Alerts should be actionable and tied to a runbook.
• Prefer symptom alerts (SLO-style) over every internal metric (noise control).
• Use thresholds that reflect baselines; add time windows to avoid flapping.

3) Log hygiene checklist

• Don’t log secrets, tokens, PII.
• Redact sensitive fields.
• Set retention intentionally; protect logs from deletion/tampering (concept-level).
• Correlate logs using request IDs/trace IDs (concept-level).

4) Dashboard structure (exam-friendly)

• Golden signals: latency, traffic, errors, saturation (concept-level).
• Separate: “service health” dashboards from “deep dive” dashboards.
• Include deployment markers so regressions align with changes (concept-level).