rcourtman 6427f28a08 Fix stale metrics store reference in reporting engine after monitor reload ...

The reporting engine held a direct pointer to the metrics store, which
becomes invalid after a monitor reload (settings change, node config
save, etc.) closes and recreates the store. Use a dynamic getter closure
that always resolves to the current monitor's active store.

Also adds diagnostic logging when report queries return zero metrics,
and integration tests covering the full metrics-to-report pipeline
including reload scenarios.

Fixes #1186

2026-02-04 12:34:40 +00:00

..

csv.go

feat: add resource picker and multi-resource report generation

2026-02-04 10:24:23 +00:00

engine_integration_test.go

Fix stale metrics store reference in reporting engine after monitor reload

2026-02-04 12:34:40 +00:00

engine_test.go

feat(reporting): add advanced reporting engine with CSV/PDF export

2026-01-12 15:21:28 +00:00

engine.go

Fix stale metrics store reference in reporting engine after monitor reload

2026-02-04 12:34:40 +00:00

multi_report_visual_test.go

feat: add resource picker and multi-resource report generation

2026-02-04 10:24:23 +00:00

pdf.go

feat: add resource picker and multi-resource report generation

2026-02-04 10:24:23 +00:00

reporting_test.go

feat: add resource picker and multi-resource report generation

2026-02-04 10:24:23 +00:00

reporting.go

feat: add resource picker and multi-resource report generation

2026-02-04 10:24:23 +00:00