Device Log Object(s) Integration¶

Objective¶

Verify the driver's behavior when viewing the historical log of the device's Log type objects.

Expected Behavior¶

The driver must create different Log type objects for each type of Log that the device has if it handles multiple, for example system, access, events. If it only handles one general log, it must create a single Log type object. Each Log type object must return the exact records that the device displays.

Test Steps¶

Start the driver
Verify that Log type objects have been created
Verify that Log type objects return the exact records displayed by the device.
Go to the device, locate the log domain and call the "Get logs" action for each object.
Verify that the records returned by the driver are the same as those returned by the device.

Expected Result¶

These events must be logged in the audit log:

'DEVICE' started.
All events that occurred during the disconnection time

Where:

DEVICE is the name of the started device

Important Notes¶

The test is considered successful when:
- Historical log events are read correctly
- For devices that send events automatically, all events generated during disconnection must be stored in the Netsocs audit log
The device's historical log must not be deleted, even if the protocol allows it

Implementation Notes¶

Events stored before controller installation have lower priority
On devices where initial reading may take hours, the query can be limited to the period after controller initialization
The integrity of the device's historical logs must be maintained at all times