monoadmin/the-other-dude
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
f4361463a729114e5a3f6f20498b1fa33b5ccb3b
the-other-dude/.planning/STATE.md
Jason Staack 8eb8c0a8fa fix(15): correct SQL column names in trend detector and alert evaluator 
- Replace `collected_at` with `time` (actual hypertable column) in 5 queries
- Remove non-existent `rule_type` column from site_alert_events INSERTs
- Fix trend dedup query to use `rule_id IS NULL` instead of `rule_type`

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-03-19 07:33:05 -05:00

5.2 KiB
Raw Blame History

gsd_state_version, milestone, milestone_name, status, stopped_at, last_updated, progress
gsd_state_version milestone milestone_name status stopped_at last_updated progress
1.0 v9.7 Tower & Site Management unknown Completed 15-03-PLAN.md 2026-03-19T12:26:34.674Z
total_phases completed_phases total_plans completed_plans
5 5 14 14

Project State

Project Reference

See: .planning/PROJECT.md (updated 2026-03-18)

Core value: Operators can monitor, configure, and troubleshoot their entire MikroTik fleet from a single pane of glass Current focus: Phase 15 — signal-trending-site-alerting

Current Position

Phase: 15 (signal-trending-site-alerting) — EXECUTING Plan: 2 of 3

Performance Metrics

Velocity:

  • Total plans completed: 7
  • Average duration: 3 min
  • Total execution time: 0.35 hours

By Phase:

Phase Plans Total Avg/Plan
11 3 12min 4min
12 2 6min 3min
13 2 5min 2.5min
Phase 13 P01 5min 2 tasks 4 files
Phase 13 P03 3min 2 tasks 6 files
Phase 14 P01 3min 2 tasks 15 files
Phase 14 P02 3min 2 tasks 9 files
Phase 14 P03 3min 2 tasks 6 files
Phase 15 P02 3min 2 tasks 4 files
Phase 15 P01 4min 2 tasks 10 files
Phase 15 P03 5min 3 tasks 9 files

Accumulated Context

| Phase 11 P01 | 3min | 2 tasks | 9 files | | Phase 11 P02 | 6min | 3 tasks | 8 files | | Phase 11 P03 | 3min | 2 tasks | 5 files | | Phase 12 P01 | 3min | 2 tasks | 6 files | | Phase 12 P02 | 3min | 2 tasks | 3 files | | Phase 13 P01 | 3min | 2 tasks | 6 files | | Phase 13 P02 | 2min | 2 tasks | 5 files |

Decisions

Decisions are logged in PROJECT.md Key Decisions table.

  • Sites must use nullable site_id FK (never mandatory) to preserve flat-list workflow
  • Per-client wireless data gets its own NATS stream and hypertable (not DEVICE_EVENTS or wireless_metrics)
  • Link state machine requires 3 consecutive missed polls before marking down (prevents false flapping)
  • [Phase 11]: alert_count set to 0 with TODO -- alert_events integration deferred to avoid coupling
  • [Phase 11]: Site detail page kept minimal (info + stats) -- full dashboard deferred to Phase 14
  • [Phase 11]: Used Dialog for delete confirmation (no AlertDialog component in UI library)
  • [Phase 11]: Site column placed after Model in fleet table for logical grouping
  • [Phase 11]: Viewers see site name text, operators get Select dropdown for assignment
  • [Phase 12]: Used unified tenant_isolation RLS policy with super_admin OR clause (matching codebase convention) instead of separate super_admin_bypass policy
  • [Phase 12]: WIRELESS_REGISTRATIONS NATS stream uses 30-day retention (vs 24h for DEVICE_EVENTS) for historical client analytics
  • [Phase 12]: RF monitor collection gated on wireless interface presence to avoid unnecessary API calls
  • [Phase 13]: No backref on DeviceInterface.device relationship -- link discovery reads interfaces directionally
  • [Phase 13]: MAC addresses lowercased at collection time for consistent downstream matching
  • [Phase 13]: InterfaceInfo (identity/link discovery) kept separate from InterfaceStats (traffic counters)
  • [Phase 13]: Link discovery uses separate durable consumer on WIRELESS_REGISTRATIONS for independent processing
  • [Phase 13]: Unknown clients query uses DISTINCT ON (mac_address) for most recent data per MAC
  • [Phase 14]: Sector CRUD nested under sites path (/sites/{sid}/sectors) matching REST hierarchy
  • [Phase 14]: Device sector assignment uses PUT /devices/{did}/sector with nullable sector_id for set/clear
  • [Phase 14]: Wireless registration queries join device_interfaces for MAC-to-hostname resolution
  • [Phase 14]: Shared signalColor helper in separate module for reuse across wireless components
  • [Phase 14]: Wireless links grouped by AP hostname with nested CPE rows for topology clarity
  • [Phase 14]: Sidebar Wireless Links href is tenant-scoped for non-super_admin users
  • [Phase 14]: Used fleet summary API for CPU/memory data since devicesApi.list does not return health metrics
  • [Phase 15]: Used getattr with fallback for config settings so trend/alert services work before Plan 01 adds them to Settings class
  • [Phase 15]: Alert events created with consecutive_hits=1 immediately; UI/API filters for >= 2 to confirm (hysteresis pattern)
  • [Phase 15]: Site alert tables are separate from device-level alert_rules/alert_events (no coupling between systems)
  • [Phase 15]: Signal history uses TimescaleDB time_bucket with 3 range presets (5min/1h/4h buckets)
  • [Phase 15]: Alert event count endpoint returns simple JSON for notification bell badge
  • [Phase 15]: NotificationBell placed in ContextStrip for consistent header integration
  • [Phase 15]: Expandable chart rows use React.Fragment pattern with per-component state
  • [Phase 15]: Alert rule type selector is context-aware (sector types when sectorId provided, site types otherwise)

Pending Todos

None yet.

Blockers/Concerns

  • OpenBao dev instance loses Transit keys on data wipe — device creds need re-entry
  • RouterOS 7 WiFi registration-table field names need validation on real hardware (Phase 12)
  • MAC-to-device resolution data source needs codebase audit (Phase 13)

Session Continuity

Last session: 2026-03-19T12:26:34.671Z Stopped at: Completed 15-03-PLAN.md Resume file: None

Reference in New Issue View Git Blame Copy Permalink