oracle-dba-monitoring-alertinglisted

# Oracle DBA - Monitoring & Alerting Read-only health/availability/space/lag monitors plus the small set of reversible configuration tasks that stand monitoring up (threshold tuning, OEM agent deploy, metric-extension setup, ITSM ticketing) for Oracle 19c and 23ai (EE; single_instance and Data Guard; on-prem). **Everything self-executing is T1 (observe)** — the checks emit machine-parseable `KEYVAL`/metric lines and threshold *findings*, they never mutate the database — **or T2 (reversible, dry-run-default).** Every deep diagnosis and remediation (role transition, FRA reclaim, listener/RAC restart) is **T3** and lives only in `references/runbooks.md`; it prints commands for a human and never self-executes. In-DB work routes through the SQLcl MCP saved connection `dba_ai_conn` (`sqlcl-mcp`); each check's host wrapper (`.sh`/`.ps1`) is the scheduler/alerting shell around its `sql/<check>.sql`. Host-only collectors (alert log via ADRCI, listener via `lsnrctl`, RAC via `crsctl`/`srvctl`, host CPU/mem/IO) cannot go through SQLcl MCP and do the work in the script (`script`). ## Scope & risk map Skill log segment = `monitoring` (T3 runbooks log under `monitoring` too). Idempotent? — all checks are read-only (re-runnable by nature); T2 setters detect "already at desired" and no-op. | Task | Level | Tier | Mechanism (script / sql / runbook path) | Idempotent? | |------|-------|------|------------------------------------------|-------------| | Database up/down monitoring | L1 | T1