The date and time is working correctly in the Terminal log!
In the future, the timezone of Terminals (NodeRed, Host… ) can follow a default time zone defined by the Administrator. In our case it would be UTC -03:00. Currently, Device Inspector Terminal already follows UTC -03:00 set by Administrator
Include the “project” field/key in the “device_resource_stream” JSON:
NOTE: It would help a lot in the NodeRED flow, especially when you want to consult users linked to the Project to trigger alerts/notifications.
The product field is informed. Why not inform the project field?
In addition to the “project” field, would it be feasible to include the “name” and “description” field in the output of the “device_stream” node?
As Node-Red works asynchronously it is not trivial to get this information from the “asset interactor” node and join with the information from the “device_stream” node.
And having these three information fields (“project”, “name” and “description”) in the device_stream node’s output would make it much easier to use along the flow, without requiring greater efforts to understand how the join node works and how it is possible to join the node information “device_stream” and “asset interactor”.
I did, but it took me a significant amount of time to understand how the join node works, especially given the asynchronous way that Node-RED works.
These three information fields (“project”, “name” and “description”) are important for us to use in the text of notification templates, for example.
Would it be feasible to create a “host” option in the “server events” node to get host event data?
I would like to capture data about CPU, RAM, Disk… (/v1/hosts/{host}/resources) and save it in a database.
From what I understand, without this option built into “node-red-contrib-thinger”, I’ll have to make requests with NodeRed’s HTTP node to “/v1/hosts/{host}/resources”, and I think this might overload ports Server connection.
Hum interesting. I thought that “node-red-contrib-thinger” when configuring $(THINGER_HOST) and $(THINGER_TOKEN_NODE_RED_PLUGIN) used internal communication (TCP/IP) between Docker container.
Ex: Thinger Server Docker with NodeRed Docker;
Influxdb Docker with NodeRed Docker.
It does go through internal communication between the containers, but from the application layer (the one that transfers application data), HTTP in this case, the requests to the server are done through the API, but it never reaches the outside world.
