What is happening now, to which record, and what led here.
Where it goes today
- 01 Event broker
Events land in a queue first — partitions, replay and retention, a system with its own on-call.
- 02 Time-series store
The signals themselves: rollups, downsampling and a retention policy of their own.
- 03 Application database
The record each event is about — the join key lives here, not with the events.
- 04 Alerting pipeline
A bespoke consumer correlates the window, the record and the threshold — written and owned by your team.
Window from one store, identity from another, correlation from a service you own — late events and retention gaps surface as wrong alerts.
Three systems · one pipeline
Where it goes in PLOMID
One request
Telemetry and events are stored with the records and documents they describe, so a window, the entity behind it and its context are read from one layer.
- Events and measurements
- Windowed reads with the record attached
- No export between systems
- Time series
- SQL
- JSON
One plan · one storage contract · no exports between stores