docs(gsd): bootstrap planning and phase-1 discussion artifacts
This commit is contained in:
@@ -0,0 +1,17 @@
|
||||
# Phase 1 Context
|
||||
|
||||
## Phase
|
||||
|
||||
Phase 1: Collectors and API flow hardening
|
||||
|
||||
## Focus
|
||||
|
||||
- Endpoint collectors must continuously send data without silent hangs.
|
||||
- AW server must accept/query data for UI pages consistently.
|
||||
- Failure points around transport/CORS/runtime must be explicitly checked.
|
||||
|
||||
## Initial Acceptance Targets
|
||||
|
||||
- Endpoint collector heartbeats arrive regularly.
|
||||
- Browser domains and endpoint signals appear in corresponding buckets.
|
||||
- Activity page for target host shows non-zero timeline/events for active period.
|
||||
@@ -0,0 +1,22 @@
|
||||
# PLAN — Phase 01: collectors-and-api-flow-hardening
|
||||
|
||||
## Goal
|
||||
|
||||
Deliver stable collector-to-server data flow so activity/worktime pages have consistent data.
|
||||
|
||||
## Work Items
|
||||
|
||||
1. Validate collector runtime and log rotation behavior.
|
||||
2. Validate server ingest endpoints and bucket write/read checks.
|
||||
3. Validate CORS/origin and report link consistency.
|
||||
4. Add/adjust scripts or runbook checks to detect zero-data regressions early.
|
||||
|
||||
## Verification
|
||||
|
||||
- Manual and scripted checks show fresh events in target buckets.
|
||||
- Host activity page reflects real activity (not `0s`) for active sessions.
|
||||
- No repeating transport errors in collector logs during test window.
|
||||
|
||||
## Status
|
||||
|
||||
Planned.
|
||||
Reference in New Issue
Block a user