The Reekoh Integration platform is able to ingest data from physical, open or enterprise systems. A number of unique capabilities of the platform is related to its ability to handle physically generated data and thus, the default expectation will typically be that data from systems that may be capable of producing device specific (or asset specific) data will in fact do so.
Where possible, Reekoh enables the pipeline developer to make that choice. Do they wish to restrict data telemetry to only pre-registered devices? Do they want the static contextualisation capability of the registry? It should also be noted that utilising these capabilities naturally incurs a small performance penalty; for those solutions where the overall network and devices on it are fully controlled, it may be desirable to disable this functionality.
On data ingestion plugins (Gateway or Stream plugins) that support these capabilities, you may notice a configuration option that will typically be called Data Mode. The acceptable options are:
- Device Data: This value means we expect the device to be identifiable through the connection or message in some way, that we will validate that ID against the registry (and reject messages where the ID is not registered) and that we will enrich the telemetry data with the metadata and location information contained in the Device Registry.
- Application Data: This value means that no checks are needed and the message will be accepted as is.