Files
infoscreen/DEV-CHANGELOG.md
Olaf 9c330f984f feat(monitoring): complete monitoring pipeline and fix presentation flag persistence
add superadmin monitoring dashboard with protected route, menu entry, and monitoring data client
add monitoring overview API endpoint and improve log serialization/aggregation for dashboard use
extend listener health/log handling with robust status/event/timestamp normalization and screenshot payload extraction
improve screenshot persistence and retrieval (timestamp-aware uploads, latest screenshot endpoint fallback)
fix page_progress and auto_progress persistence/serialization across create, update, and detached occurrence flows
align technical and project docs to reflect implemented monitoring and no-version-bump backend changes
add documentation sync log entry and include minor compose env indentation cleanup
2026-03-24 11:18:33 +00:00

3.3 KiB
Raw Blame History

DEV-CHANGELOG

This changelog tracks all changes made in the development workspace, including internal, experimental, and in-progress updates. Entries here may not be reflected in public releases or the user-facing changelog.


Unreleased (development workspace)

  • Monitoring system completion: End-to-end monitoring pipeline is active (MQTT logs/health → listener persistence → monitoring APIs → superadmin dashboard).
  • Monitoring API: Added/active endpoints GET /api/client-logs/monitoring-overview and GET /api/client-logs/recent-errors; per-client logs via GET /api/client-logs/<uuid>/logs.
  • Dashboard monitoring UI: Superadmin monitoring page is integrated and displays client health status, screenshots, process metadata, and recent error activity.
  • Bugfix: Presentation flags page_progress and auto_progress now persist reliably across create/update and detached-occurrence flows.
  • Frontend (Settings → Events): Added Presentations defaults (slideshow interval, page-progress, auto-progress) with load/save via /api/system-settings; UI uses Syncfusion controls.
  • Backend defaults: Seeded presentation_interval ("10"), presentation_page_progress ("true"), presentation_auto_progress ("true") in server/init_defaults.py when missing.
  • Data model: Added per-event fields page_progress and auto_progress on Event; Alembic migration applied successfully.
  • Event modal (dashboard): Extended to show and persist presentation pageProgress/autoProgress; applies system defaults on create and preserves per-event values on edit; payload includes page_progress, auto_progress, and slideshow_interval.
  • Scheduler behavior: Now publishes only currently active events per group (at "now"); clears retained topics by publishing [] for groups with no active events; normalizes naive timestamps and compares times in UTC; presentation payloads include page_progress and auto_progress.
  • Recurrence handling: Still queries a 7day window to expand recurring events and apply exceptions; recurring events only deactivate after recurrence_end (UNTIL).
  • Logging: Temporarily added filter diagnostics during debugging; removed verbose logs after verification.
  • WebUntis event type: Implemented new webuntis type. Event creation resolves URL from system supplement_table_url; returns 400 if not configured. WebUntis behaves like Website on clients (shared website payload).
  • Settings consolidation: Removed separate webuntis_url (if present during dev); WebUntis and Vertretungsplan share supplement_table_url. Removed /api/system-settings/webuntis-url endpoints; use /api/system-settings/supplement-table.
  • Scheduler payloads: Added top-level event_type for all events; introduced unified nested website payload for both website and webuntis events: { "type": "browser", "url": "…" }.
  • Frontend: Program info bumped to 2025.1.0-alpha.13; changelog includes WebUntis/Website unification and settings update. Event modal shows no per-event URL for WebUntis.
  • Documentation: Added MQTT_EVENT_PAYLOAD_GUIDE.md and WEBUNTIS_EVENT_IMPLEMENTATION.md. Updated .github/copilot-instructions.md and README.md for unified Website/WebUntis handling and system settings usage.

Note: These changes are available in the development environment and may be included in future releases. For released changes, see TECH-CHANGELOG.md.