Removing Personally Identifiable Information from the Configuration Variables Log

The configuration variables log contains messages about the operations, warnings, and errors that occur while Microservices Runtime applies a configuration variables template at startup. This can include messages about setting a property key for a user name to a specific value. The configuration variables log is overwritten at startup of an on-premise Microservices Runtime. The configuration variables log for a Microservices Runtime running in a Docker container is destroyed when the container is destroyed.

Microservices Runtime writes the configuration variables log messages to the console (STDOUT) and/or to the location: Integration Server_directory /instances/instanceName/logs/configurationvariables.log. A Microservices Runtime running in a Docker container always writes the configuration variables log messages to both locations.

To remove references to a user name or user ID from the configurationvariables.log, use a text editor to search the log for the user name or user ID. Then remove or replace the found data.

To remove references to a user name from the configurationvariables.log for a Docker container, you can attach to the container file system and then search for and remove or change the user name from the log.

If Microservices Runtime writes the configuration variables log to the console (STDOUT), then you need to remove or replace the user name information from the destination that captures the STDOUT stream.

Docker captures the STDOUT stream in a file which, by default, is a JSON file. You may need to edit log files generated by the logging driver used with Docker. For example, the json-file logging driver, which is the default logging driver for Docker, captures everything written to STDOUT and writes it to a JSON file. The JSON log file may be rotated. When the Docker container is destroyed, the JSON log files are removed. As a result, you might not need to remove identifying user data from thee JSON log files. If, however, you used Docker volumes to persist configuration and log files to a mounted directory on the host file system, you may need to clean the externalized log files as described above.

For an on-premise Microservices Runtime, the STDOUT stream is written to Software AG_directory /profiles/IS_instanceName/logs/wrapper.log

Use a text editor to search the wrapper.log as well as the other log files in the logs folder for user information. Then, remove or replace the found data.