Glossary
The words UpBlue uses for the way data flows through the platform.
| Word | Meaning |
|---|---|
| Source | A connection that brings data into UpBlue: a machine protocol such as OPC UA, Modbus or MQTT on a collector, an UpBlue Connect device, or a cloud connector such as Kenter or a webhook. |
| Destination | A connection that sends data from UpBlue to another system: HTTP out or MQTT out. Delivered by says which collectors send to it: one collector, or all collectors of the organisation. |
| Rule | What a source reads into one tag, with its transformations. Alert rules and event rules are always called by their full name. |
| Store in UpBlue | The switch on a rule that keeps its values in UpBlue for dashboards, alerts and analysis. Without it, the values only go to destinations. |
| Route | Which destination receives which data, chosen by labels, sources or tags. Routes are applied for the whole organisation; each route is started or stopped on its own. |
| Event | A period on an operation tag, for example a machine that runs or stands still. A rule creates events when its value crosses a threshold. |
| Attention item | Something you can fix that keeps data from arriving or leaving, such as a refused password, a destination that does not answer or a sensor without a valid reading. It links to the Flow view where the problem is. |
| Flow view | The Flow card on a tag page, and Flow on a connection page: where the data comes from, its rule, whether it is stored, every destination it goes to, and how much passed each step. A step where something fails is red. |
| Lineage | The path of one tag, as the Flow view shows it. |