Server Event Groups¶
The server’s events are grouped in event groups. Grouping facilitates operations on multiple events, and is done based according to various criteria.
Below is the reference of available Server Event Groups.
Events emitted by actions done by local administrators or by the process itself. All events have an avatar data field.
Events emitted by authenticated accounts. All events have an avatar data field.
Events emitted by the client side file transfer operations.
Operating system compatibility layer.
Events generated by a failed operation. Any failed operation, critical or non critical.
Events generated by a critical failure. This event should not occur under normal operation.
Events generated by failures with a high impact on server operation. This can be configuration or operational errors.
Failures which don't have details attached.
Events generated by file handling operations. They can be both server-side or client-side operations. When the events are generated by a server-side component, operating in a chrooted/locked filesytem, the path data field is set to the virtual path of the file on which the operation is performed. The 'real_path' data field is set to the full path of that file, as present to the normal file system.
Events generated by FTP/FTPS file transfers client and server side.
Events generated by HTTP/HTTPS file transfers client and server side.
Events informing that an action is going to be performed, or containing details about the service state.
Events generated by Local Manager service.
Events generated by operations on location. All events have a path data field populated with the local path of the file on which the operation is performed. The path can be local or remote.
Events generated by the monitor service.
File content was appended.
A new folder was created.
A file or folder was deleted.
The content of a file was read.
A file or folder was renamed or moved.
The content of a file was written.
Events generated by internal server functions.
Events generated by process itself while not associated with any account, administrator or remote peer. All events have an avatar data field.
Event generated by opening and closing connection and establishing authenticated sessions for clients. All events have a peer data field populated with the host/port address of the client connection.
Events generated by SSH file transfers client and server side. Common SSH services, and SCP and SFTP specific events.
Events generated by a successful operation.
Events generated by client-side transfers.