You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -92,6 +92,8 @@ Discovery preserves every metric name, model and provider value returned by the
92
92
93
93
Inline composition is capped at **40 models with usable prices**. Above that limit, no monetary subtotal or budget is generated: select the financial datasource with `--datasource`, generate and load its recording rules, then repeat discovery and forge. All priced models supplied to the rule generator are retained, including beyond 60 models. Recorded queries are shorter, but execution cost still depends on series count and time window. Native and recorded sources retain unverified upstream coverage and do not depend on registry coverage.
94
94
95
+
With `--deploy --with-alerts`, an ineligible budget also pauses an existing Forge budget in the resolved organization and folder. Forge checks its deterministic UID, rule group and ownership labels before updating only `isPaused`; an absent budget is not created. The manifest records `budget_alert.action`, `result` (`paused`, `already_paused`, `absent` or `failed`) and the coverage reason. Alert resource counts include this maintenance operation, including confirmed absence or an already paused rule. A collision or unconfirmed HTTP response makes the deployment partial/failed. Generation, dry-run and deployments without `--with-alerts` do not perform this check. When coverage becomes eligible again, Forge updates the budget while preserving its existing pause (`upserted_paused`): review the coverage and resume it explicitly in Grafana. Other SLO pause behavior is unchanged.
96
+
95
97
### Provider origin and declared deployment locations
96
98
97
99
The registry field and Prometheus label `region` remain compatible and describe **provider origin**. They establish neither processing nor storage location. Governance always includes a separate deployment panel: locations default to **unknown**. Optionally pass `--deployment-inventory ../instance/deployment_inventory.json`, keeping real inventory outside the packaged skill. A US-origin model can have declared processing in France; both facts are shown separately.
0 commit comments