Rsyslog

Diagram

Description

The proposed solution for logs handling is to use independant rsyslog servers writing to the Gluster filesystem. A unique rsyslog server will be deployed for each islet as well as for management nodes.

In case of islet hypervisor(s) failure(s), it will be necessary to manually switch to other islet rsyslog servers. The switch will be documented.

Also, there will be a need to configure a rate limit either on the client or on the server side in order to avoid log explosion. This rate limit threshold has to be determined.

The tree structure in which log files will be written will be based on client node names and will also take into account the node type (node, switch, etc…). Log messages format will be the same accross all rsyslog servers and shared accross all Ocean based servers.

If there is a need to export logs to the outside, the ETL service can be used.