Context

The platform has an auditing system that allows every operation that occurs on the platform to be audited. These operations include logins and logouts in the Control Panel, communications between devices and systems, etc. Information on how auditing works can be found here.

Until now, all operations performed through the Platform Digital Broker were categorized within the audit as IoTBroker, which did not allow to know whether the operation was performed from a Microservice (through a Java client, SpringBoot, Python, ...), a Dataflow Pipeline or a Notebook. Among the improvements that are being implemented within the scope of Data Governance, we have improved this part of the audit to have a greater traceability over the data, so now we will be able to know specifically from where the data is being inserted, modified or queried.

Modifications in DigitalBroker

A new optional parameter, tags, has been included in the DigitalBroker operations, so that if that field is not specified, then the operation will be categorized as before (IoTBroker); but, if you add this parameter, you will be able to specify the origin of the data.

To do so, you only need to enter the tags parameter with a value with the following structure:

where data_source can take the following values: CONTROLPANEL, APIMANAGER, IOTBROKER, FLOWENGINE, ROUTER, RTDBMAINTAINER, SQLENGINE, PLANNER, OAUTHSERVER, DATAFLOW, NOTEBOOK, JAVACLIENT, PYTHONCLIENT

Client modifications

The clients have been modified so that, from version 3.1.0, the operations coming from these clients are correctly categorized (JAVACLIENT, PYTHONCLIENT...).

The Dataflow Platform libraries have also been modified so that all operations originating from Dataflow are categorized as DATAFLOW.