An integration is Observis's support for one device provider. It defines how to talk to that vendor's system and what configuration a connection to it requires. A connection is one configured, deployed instance of an integration.
Where you see them
Integrations are not a page you browse. They appear inside the wizard when you add a connection, as a searchable, filterable template list.
That is deliberate: the list exists to be chosen from at the moment you need it, rather than to be kept on screen. Adding a connection covers the flow.
What an integration determines
| It defines | Which means |
|---|---|
| How the vendor system is contacted | You do not configure protocols or endpoints beyond what the form asks for. |
| What configuration is required | The form changes completely depending on the integration you pick. |
| How readings become devices and metrics | The same physical setup can appear differently under different integrations. |
That last point catches people out. One vendor may report a multi-channel logger as a single device carrying many metrics, while another splits each channel into its own device. Neither is wrong, and neither is something you configure. Connections, devices, and metrics covers what this looks like in practice.
The list is live
Available integrations are fetched when you open the wizard rather than being a fixed list, so it reflects what is supported now. Coverage spans wireless sensor networks, dataloggers, geotechnical monitoring systems, vibration and noise monitors, and file-based sources.
Some vendors appear more than once, covering different ingest modes for the same hardware — polling an API is a different integration from reading exported files, even for the same logger. Pick the one that matches how you actually get your data, and if you are unsure, ask before configuring.
If your source is not listed
Contact Observis Support and describe the hardware and how it currently delivers data.
Do not substitute a different integration that looks close. Integrations are specific to a vendor's protocol and data shape, so a near match will either fail to connect or produce readings that are wrong in ways that are hard to notice.
Comments
0 comments
Article is closed for comments.