HAR analysis: Event report page
Source: event-report.har — opening the Event report page.
Flow: User navigates to the event report. The page loads control room, collaborators, rules, rule-types, events (search + summary), tasks count, preferences, and event summaries with different grouping/date ranges.
API calls (observed)
| API | Count | Notes |
|---|---|---|
GET /controlrooms/{id} |
2× | Same control room within ~23ms (breadcrumb + app state) |
GET /controlrooms/{id}/collaborators |
2× | ~512ms apart |
GET /events/summary (groupBy=asset,eventType, date range) |
1× | 13.4 s — dominant latency |
GET /events/summary (startDate 2026-02-09) |
1× | Different date range |
GET /events/summary (groupBy=asset, eventTypeId=…) |
1× | 828ms; different params |
POST /events/search (no size) |
1× | |
POST /events/search?size=200&page=0,1,2 |
3× | Pagination (by design) |
POST /rules/search, GET /rule-types |
1× each | |
POST /tasks/search?size=1, GET /me/preferences |
1× each |
Duplicated calls
- getControlRoom — 2× (same pattern as other control room pages).
- getCollaborators — 2× (same pattern as asset/place drawer, task page).
Performance note (non-duplicate)
- events/summary (groupBy=asset,eventType) — One call took 13.4 seconds. This is the main blocker for event report load time. Consider backend optimization, caching, or reducing aggregation scope.
Suggested fix
- Control room / collaborators — Use store; resolver/effects should not re-fetch when already loaded.
- events/summary — Backend: profile slow query; consider indexes, caching, or async/precomputed aggregates.
Estimated impact
- Duplicates: 2× getControlRoom + 2× collaborators → 1× each with store. 2 calls saved.
- Slow summary: 13.4s — backend tuning could cut this significantly.