Pipeline Manager is where you set up and inspect the connections that bring monitoring data into a project. It answers one question better than anywhere else in Observis: what is feeding this project, and is it working?
Two ways to look at the same thing
Pipeline Manager offers a flow view and a table view, switched from the button group in the header.
The flow view draws the project as a map. Each connection appears as a node showing its name, type, and device count, with lines running out to the devices it has discovered. It is the fastest way to see the shape of a project and spot a connection that has nothing attached to it.
The table view lists the same connections as rows, with type and running status, and expands to show the devices under each one. Use it when you want to scan, search, or confirm a specific device is present rather than see the shape of the project.
There is also a fullscreen mode for the canvas, which is worth using on projects with more than a handful of connections.
Data reads left to right: devices on the left, the connection they arrive through on the right.
The canvas is a map, not a workspace
The flow view is read-only. You can move around it, search it, and open things from it, but you cannot drag nodes into new positions or draw connections between them by hand. Node layout is generated, not saved.
This surprises people who expect a diagramming tool. Manual canvas editing is planned for a later version. For now, treat the canvas as a live picture of what exists rather than something you arrange.
The connection pane
A floating pane over the canvas is how you navigate once a project has more than a few connections. From it you can:
| Action | What it does |
|---|---|
| Search | Filter the connection list by name. |
| Solo | Isolate one connection on the canvas and hide the rest. |
| Hide and show | Remove individual connections from view, or hide and show all at once. |
| Collapse | Fold the pane away when you want the full canvas. |
The pane header carries the project's total device count, and each connection shows its type and a device count badge.
Connection status
Each connection carries a status indicator showing whether it is running, both on the pane and in the table view. This is your first check when data has stopped arriving: a connection reporting a problem explains a silent project far more often than the instruments do.
Status is reported per connection rather than per device. A connection can be healthy while one instrument on it has stopped, so a green connection is not proof that every device is reporting. Alerts are where per-device silence gets caught, through stale data events.
If a connection shows a problem you cannot explain from its configuration, contact Observis Support.
Large connections group themselves
A single connection can carry hundreds of devices. One production connection carries over 500, and drawing that many nodes would make the canvas useless.
Device grouping handles this, and you control it from the pane:
| Mode | What it draws |
|---|---|
| Auto | Groups a connection's devices once there are enough to crowd the canvas, and draws them individually when there are few. The default. |
| Device Type | Always groups by device type, however few devices there are. |
| None | Always draws every device as its own node. |
A group node is labelled with the device type and a count. Clicking one opens a searchable list of the devices inside it.
Auto suits most work. Reach for None when you need to confirm a specific device is present and you have few enough to look at, and Device Type when you want a consistent shape across connections of very different sizes.
If a project shows more devices than you have instruments installed, that is expected. Connections, devices, and metrics explains why device counts and instrument counts often differ.
Comments
0 comments
Article is closed for comments.