Why shouldn't print chaincode logging to peer in production? #fabric-chaincode-evm


Hubert Z
 

Hi all,

I found that for chaincode logging, we shouldn't set peer environment variable "CORE_VM_DOCKER_ATTACHSTDOUT=true" in production, from https://hyperledger-fabric.readthedocs.io/en/release-1.4/logging-control.html

The reason is,
these channels are normally disabled on a production network to mitigate abuse from broken or malicious code.
OR
Any output written to either stdout or stderr will be integrated with the peer's log on a per-line basis. It is not recommended to enable this for production.
Could anyone explain the details why chaincode logging output would cause production problems?

Thank you.

Best Regards,
Hubert

Join fabric@lists.hyperledger.org to automatically receive all group messages.