Suggest an Idea

[Prabodh]

The VERBOSE logging level in Replicate is useful for troubleshooting. However, Replicate starts logging actual data to the log files in VERBOSE level.

While it is good for troubleshooting certain issues, the data is not always needed. Having data in the log also limits our ability to share the log files with support team. It is also against our security best practices and against PCI standards.

I would like to propose an enhancement to add a configuration to disable writing actual data to log files. The config can be enabled to write the data to logs in cases where it is absolutely required.

[Shelley_Brennan]

Thank you for the suggestion.  The request as I understand it is to provide an option that removes some sensitive data from the VERBOSE logging level so it can be used for troubleshooting while still complying with your security best practices?

Could you either provide some specifics of the information that would need to be removed from VERBOSE level that is considered sensitive or provide specific examples of information shown in VERBOSE that you depend on for troubleshooting that could potentially be added to TRACE logging level?  This would help us find the right balance of troubleshooting capabilities vs meeting security standards.

In the meantime, we will leave this open to collect feedback and see if others would find this useful as well.

[Shelley_Brennan]

Note that in the May 2021 release, we have introduced a new configuration parameter that controls if data fragments are written to the log in Verbose mode.  it is turned off by default.  We do plan on adding additional feature to encrypt data fragments in a future release as well.  Thank you!