1 minute read

Date

August 2, 2024

New Features and Improvements

Note: The device log filtering API GetLogWithFilter has been Deprecated. It is recommended that filtering be performed on the server using GetLog, EnableMonitoring and SubscribeRealtimeLog.

The device log filtering GetLogWithFilter API reviews the device’s logs against the conditions set by the server.
This means that the device may invest considerable time in log filtering, and as the number of logs on the device increases, more time will be required.

Also, logs are not permanently stored on the device.
If the maximum number of logs that the device can hold is exceeded, the device will overwrite the oldest logs, and logs older than a certain period of time may be automatically deleted.
It is recommended that all logs from the device be stored and managed on a server.

It is recommended that logs be received in bulk from the device using the GetLog API, and that logs occurring after the current time be received in real time using the EnableMonitoring and SubscribeRealtimeLog APIs, so that the server stores all logs in an appropriate DBMS and filters the logs from the DBMS.