EdgeEventController
EdgeEventController exposes REST endpoints for querying the inbound event log — downlink messages received from the server, like entity assignments, rule chain pushes, and RPC calls.
Endpoints
Section titled “Endpoints”Base path: /api/edge/{edgeId}/events
| Method | Path | Description |
|---|---|---|
| GET | /api/edge/{edgeId}/events | Returns a paginated list of edge events. Supports pageSize, page, textSearch, sortProperty, sortOrder, startTime, and endTime. Requires TENANT_ADMIN authority. |
Cloud events vs. edge events
Section titled “Cloud events vs. edge events”Edge maintains two separate event logs:
- Cloud events at
/api/edge/events: Outbound messages queued on Edge waiting to be sent upstream to the server, like telemetry, alarms, and entity changes. Accessible viaEdgeController. - Edge events at
/api/edge/{edgeId}/events: Downlink messages received from the server, like entity assignments, rule chain pushes, and RPC calls. Accessible viaEdgeEventController.
Both queues use the same pagination interface and are useful for diagnosing synchronization issues. If the cloud events queue grows without draining, check the gRPC connection status via Edge status & events and message statistics.