Build an event integration
Work through event fields, MQTT delivery, timestamps and recovery after a connection fails.
Sources and scopeRead before use
Navigation or project guidance; not a claim of product, standards or environment validation.
On this page
1. Keep the original record#
Read events and time, then the event field guide. Keep source identity, device time, receipt time and mapping revision with the raw message.
Limit: normalising a timestamp does not improve the source clock.
2. Choose the delivery path#
Read MQTT or WebSocket, SSE and webhooks, depending on the interface. Record the protocol version, connection owner, topic or resource scope, and permissions.
For MQTT, think through retained messages, sessions, expiry and delivery acknowledgements before treating an incoming message as a new physical event.
3. Design duplicates and gaps#
Read retries and idempotency and reconnects and queues. State how much work may be buffered and when it becomes stale.
4. Rebuild a trustworthy view#
Read polling and reconciliation and schema evolution. Decide which source can reestablish current state after a gap.
Practise on a synthetic contract#
Read the MQTT event example and MQTT trust and ACL review. No broker deployment or live device is needed for the reading exercise.