Skip to content

feat: uptimerobot monitoring design - #96

Merged
vthwang merged 3 commits into
mainfrom
feat/uptimerobot-monitoring-design
Oct 25, 2026
Merged

vthwang merged 3 commits into
mainfrom
feat/uptimerobot-monitoring-design

Conversation

@vthwang

@vthwang vthwang commented Oct 25, 2026

Copy link
Copy Markdown
Member

No description provided.

Define a safe customer-facing status model and an internal alerting boundary.

- document public and internal monitor contracts
- capture token containment and migration steps
- specify UptimeRobot groups, allowlists, and acceptance checks

Signed-off-by: vthwang <vthwang.work@gmail.com>
Move the documented UptimeRobot contract away from query-string secrets while preserving a short cutover bridge.

- validate monitor bearer headers in constant time
- document the OpenAPI security scheme
- cover auth failures and migration behavior

Signed-off-by: vthwang <vthwang.work@gmail.com>
Expose customer-safe availability signals for the Farm control plane, platform VTA, and shared platform services.

- probe fixed public targets with bounded timeouts
- return generic status responses without infrastructure details
- apply a shared per-IP rate limit and document the policy

Signed-off-by: vthwang <vthwang.work@gmail.com>
@vthwang vthwang self-assigned this Oct 25, 2026
@vthwang vthwang added the enhancement New feature or request label Oct 25, 2026
@vthwang
vthwang merged commit bb003e1 into main Oct 25, 2026
1 check passed
@vthwang
vthwang deleted the feat/uptimerobot-monitoring-design branch October 25, 2026 07:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant