Public source validation / validate (push) Failing after 3m8s
26 lines
1.1 KiB
Markdown
26 lines
1.1 KiB
Markdown
# Configuration examples
|
|
|
|
Files in this directory are **schemas/examples**, not production secrets.
|
|
|
|
- `metrics/catalog.example.json`: initial semantic metric definitions.
|
|
- `dashboards/default-overview.example.json`: system overview template.
|
|
- `alerts/default-rules.example.json`: conservative baseline rules.
|
|
- `probes/probe.example.json`: disabled probe example.
|
|
|
|
Codex must:
|
|
- validate them against schemas;
|
|
- convert them to implementation-owned seed/migration mechanisms;
|
|
- version changes;
|
|
- never overwrite a user's customized dashboard/rule silently;
|
|
- never insert real credentials.
|
|
|
|
## Contract mapping
|
|
|
|
- `metrics/catalog.example.json` → `specs/metric-catalog.schema.json`
|
|
- `dashboards/default-overview.example.json` → `specs/dashboard.schema.json`
|
|
- `alerts/default-rules.example.json` → `specs/alert-rule-set.schema.json`
|
|
- `probes/probe.example.json` → `specs/probe.schema.json`
|
|
|
|
|
|
- `internal/alertdefaults/seed.json` is the implementation-owned, embedded v1 seed. It is reconciled at API startup without overwriting an existing rule ID or user customization.
|