23 lines
1001 B
Markdown
23 lines
1001 B
Markdown
|
# dbis_core — when to implement (Redis, Prometheus, PagerDuty)
|
||
|
|
|
||
|
|
**Purpose:** Runbook/checklist so full scope is clear; no new code in this plan.
|
||
|
|
**See also:** NOT_IMPLEMENTED_FULL_SCOPE section 5, dbis_core submodule.
|
||
|
|
|
||
|
|
## Redis
|
||
|
|
|
||
|
|
When: Required only if caching (or session/state) is needed. Current: Optional; already wired when REDIS_URL is set. Action: Enable when a service is configured to use Redis; document in dbis_core or runbook.
|
||
|
|
|
||
|
|
## Prometheus
|
||
|
|
|
||
|
|
When: Implement push or scrape when the monitoring stack is deployed. Action: Add metrics endpoints or scrape config when monitoring stack is up; document in dbis_core or ops runbook.
|
||
|
|
|
||
|
|
## PagerDuty
|
||
|
|
|
||
|
|
When: Implement when on-call and incident routing are required. Action: Wire alerts to PagerDuty; document in runbook.
|
||
|
|
|
||
|
|
## Deal-execution integration tests
|
||
|
|
|
||
|
|
Current: Skipped with ticket (per GAPS). Action: Re-enable and fix when CI/env and dependencies are ready; update GAPS and PLACEHOLDERS when done.
|
||
|
|
|
||
|
|
No new code in this doc; checklist only.
|