--- title: Telemetry to alert description: How a raw device reading becomes a live dashboard update and, when needed, an alert. --- # Telemetry to alert This workflow is the platform's hot path: millions of devices publish readings, and within seconds those readings must appear on dashboards and, when a rule trips, turn into an alert in an operator's inbox. End-to-end target is **< 5 seconds** from device publish to dashboard update, and **< 10 seconds** from a threshold breach to a delivered alert. ## Participants Accepts device sessions and fans telemetry to consumers. Windows and aggregates the firehose into metrics. Evaluates thresholds and anomaly signals. ## Steps ### Publish The [**Edge Agent**](:obj:@example-iot.product.edge.edge_agent) batches readings and publishes to the broker. ### Aggregate The [**Stream Processor**](:obj:@example-iot.product.processing.stream_processor) consumes the topic and computes windowed aggregates. ### Evaluate Enriched events are passed to the rules, which decide whether a threshold or anomaly condition is met. ### Notify & render A live aggregate is pushed to the dashboard; a breach additionally raises an alert via the notification provider. The same aggregate that updates charts also feeds rule evaluation, so what an operator sees and what triggers an alert are always derived from one source.

Number	Source	Destination	Description
1	Edge agent	MQTT broker	Publish telemetry batch
2	MQTT broker	Stream processor	Deliver to consumer
3	Stream processor	Stream processor	Window aggregation
4	Stream processor	Rule runtime	Enriched event
5	Stream processor	Dashboard	Live aggregate (WebSocket)
- if Threshold breached
6	Rule runtime	Notifications	Raise alert
7	Notifications	Dashboard	Alert delivered
else Within bounds
8	Rule runtime	Stream processor	No action
end