Audit monitor targeting model and entity-detail inverse lookup

completed

Priority: 0

Artem-requested evidence-only audit: locate monitoring Prisma/domain model; classify monitor targeting mechanisms; use read-only production data for cardinalities/cohort examples; determine inverse device/site lookup cost; audit Dashboard monitor detail/list/Explorer/alert UI and monitor-to-alert linkage. No code changes.

Event Timeline

created

status_change

queued → in_progress

failed

lease expired — re-queued for retry

in_progress → queued

progress

Located monitor engine in domains/device and confirmed current production dataset is only 10 monitors. Targeting is MonitorTarget rows resolved dynamically to ES; production has DEVICE_TYPE and WORKSPACE targets only. Auditing exact candidate cohort sizes, UI inverse resolver, and alert monitor attribution now; no source changes.

progress

Production target cardinality confirmed: 10 monitors total; all existing targets are 8 DEVICE_TYPE + 2 WORKSPACE, no DEVICE_FILTER/SITE/COLLECTION/PROGRAM rows and no cached entityCounts. Largest workspace has 6 monitors; tracked MonitorEntityState is sparse (7 total) and cannot serve as a current cohort membership materialization. Finalizing exact/approximate inverse-query boundaries and monitor-generated alert fallback.

status_change

queued → completed