ThingBand — data destinations

ThingBand manages the destinations that receive rule matches or telemetry from ThingLogic. These destinations are called data sinks. Open ThingBand from the account console product switcher.

Data sinks

A sink has a name, a destination type, configuration, input requirements, and zero or more pipeline bindings. The supported destination types are:

• Persistence — durable storage for later query or processing.

• Notification — an operator or automation notification destination.

• External forwarding — an integration outside the platform boundary.

• Visualization — a dashboard or visualization consumer.

• Alarm lifecycle — the operator-alarm store. A rule bound to this sink raises an ack-able alarm with an open/acknowledge/shelve/resolve lifecycle, shown in the ThingLogic Alarms tab.

The configuration fields depend on the selected type. Treat credentials and destination URLs as sensitive configuration.

Create or edit a sink

1. Open Data sinks and choose Create sink.

2. Enter a unique, recognizable name and select the destination type.

3. Supply the configuration and input requirements required by that destination.

4. Save the sink. It can now be selected while composing a ThingLogic pipeline.

Edit a sink when its destination configuration changes. Review existing bindings before changing inputs: a bound pipeline may depend on the current shape.

Delete a sink

A sink that is still bound to a pipeline should not be removed. Stop or update the bound pipeline first, verify that Bindings is empty, then choose Delete and type the sink name to confirm.

Note

ThingBand does not create device cohorts and does not perform bulk device actions. Device organization belongs to ThingHub; processing orchestration belongs to ThingLogic.