Allow observer to share logs to external parties

[lumtis]

Describe the Issue

Implement a solution that allows an observer to voluntarily share logs to a specific channel.

Requirements:

• Must be optional for the observer
• Must not share sensitive actions

Tasks:

• Eventual refactoring in log system to enable this
• Implement channel for log sharing
• Add options in node config for this functionality

cc @CryptoFewka @morde08

[CryptoFewka]

Supporting an external log destination seems like something that is outside the scope of zetaclientd when it already logs to syslog.

Would this feature be satisfied with a reference implementation of an off the shelf open-source log forwarding solution that would transmit logs to us? It could go as far as to be an installation script to download, install and configure an open source forwarder pointed at our infrastructure.

If we want to embed the forwarder's installation inside zetaclientd we could if that better fits the vision you have in mind for this.

Regardless of the ultimate architecture, would it be possible to get a list of log filters or grep strings to either: A. Filter out log messages that shouldn't be forwarded for a default forward strategy. B. Explicitly include log messages for a default do not forward strategy.

[lumtis]

Regardless of the ultimate architecture, would it be possible to get a list of log filters or grep strings to either: A. Filter out log messages that shouldn't be forwarded for a default forward strategy. B. Explicitly include log messages for a default do not forward strategy.

Is it something you need from the protocol team?