Gateway events

Who it’s for

Engineers investigating a ThingsBoard IoT Gateway that is behaving oddly — a connector that stopped, a device that disappeared, a restart nobody expected. The events are the gateway’s own account of what happened, and this widget is where they are read.

What it does

The Gateway events widget lists the events a gateway reports, with a filter for narrowing them to the ones being investigated. Pointed at a gateway device, it browses that gateway’s event stream, so a fault can be traced to the moment it started rather than inferred from missing telemetry.

• The gateway’s own account of events, which is often the only record of why a connector stopped.
• A key filter narrows the stream, so a specific connector or event class can be isolated from a busy log.
• A generous default size, 7.5×8, because event investigation means reading a lot of rows.
• The form title is configurable, which matters on a dashboard carrying several gateway widgets.
• The Gateway events widget reads what the gateway reports: a gateway that has stopped reporting has no events to show, which is itself the finding.

How to set up

Data keys

The Gateway events widget takes its content from the gateway device it is pointed at.

Key	Role	Type	Description
Gateway event keys	The events listed	Timeseries	Point the datasource at the gateway device; the widget browses the events that gateway reports.

Filter

Setting	Default	Effect
Gateway events form title	Gateway Events Form	The caption above the list
Events filter	Empty	Narrows the list to events whose key contains the given text

Confirm event reporting is enabled on the gateway. An empty list means either nothing happened or nothing is being reported, and the two look identical from here.

How to customize

• To isolate one connector — set the Events filter to text contained in that connector’s event keys.
• To name the panel — set the Gateway events form title, ideally to the site rather than the generic default.
• To give investigation room — keep the widget at or above its default height, since events are read in sequence.

Tips

• Put the events list beside the gateway’s statistics charts on the same time window. The charts show when something changed and the events usually say what, and having both on one window removes the step of correlating two periods by hand.
• Filter to a connector before concluding a gateway is healthy. A busy gateway produces enough routine events to bury the one that matters, and an unfiltered list scrolls past the finding.