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
fix(github): surface a mirrored control rejection on every path an operator reads
- Mirror settled control requests from the stop/cancel progress reads. Those
paths reconcile a terminal remote and end the drive, so a rejection the data
plane settled after the last regular poll would otherwise never be recorded.
- Append the rejection notice to the terminal summary comment, not only to the
progress comment the summary supersedes.
- Omit the attribution clause when the stored request names no operator, so a
proxied command is not credited to SchemaBot's internal forwarding caller.
- Rewrite the remote apply identifier out of the mirrored reason on an
operation-scoped drive, where the parent apply carries no external id.
- Name an unrecognized settled status in a warning instead of dropping it
silently.
- Document the rejection counter and the release operation in the metrics
reference, and count release as a known control operation.
Copy file name to clipboardExpand all lines: pkg/metrics/README.md
+14-1Lines changed: 14 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -39,6 +39,7 @@ available, such as `repository`, `github_app`, and `installation_id`.
39
39
|`schemabot.github.rate_limit.remaining`| Gauge | environment, operation, resource, repository, github_app, installation_id | GitHub primary rate limit requests remaining for the observed API resource |
40
40
|`schemabot.github.rate_limit.used`| Gauge | environment, operation, resource, repository, github_app, installation_id | GitHub primary rate limit requests used for the observed API resource |
41
41
|`schemabot.control_operations_total`| Counter | operation, database, environment, status | Control operations (cutover, stop, start, etc.) |
42
+
|`schemabot.remote_control_requests.rejected_total`| Counter | operation, engine, database, deployment, environment | Control requests a remote data plane accepted and its own driver then failed, mirrored back so the operator learns the command never took effect — see [Control Operations](#control-operations)|
0 commit comments