Log messages containing non-ASCII characters are dropped when being forwarded to third party platforms

Products

• VMware Tanzu Application Service for VMs

Issue/Introduction

• When a task is completed, you will be able to see the below records in the app logs. 
  • Container lifecycle 
  • OUT logs for the task
• Below is a full log example for a task named "検証テスト". You should be able to view the similar outputs on both Tanzu Application Service for VMs (Apps Manager or cf logs command or App Metrics) or the third party platform where the logs are forwarding to.

[CELL/0] [OUT] Cell [DIEGO_CELL-INSTANCE-ID-xxx] creating container for instance [INSTANCE-ID-xxx]
[CELL/0] [OUT] Cell [DIEGO_CELL-INSTANCE-ID-xxx] successfully created container for instance [INSTANCE-ID-xxx]
[APP/TASK/検証テスト/0] [OUT] /home/vcap/app
[APP/TASK/検証テスト/0] [OUT] Exit status 0
[CELL/0] [OUT] Cell [DIEGO_CELL-INSTANCE-ID-xxx] stopping instance [INSTANCE-ID-xxx]
[CELL/0] [OUT] Cell [DIEGO_CELL-INSTANCE-ID-xxx] destroying container for instance [INSTANCE-ID-xxx]
[CELL/0] [OUT] Cell [DIEGO_CELL-INSTANCE-ID-xxx] successfully destroyed container for instance [INSTANCE-ID-xxx]

• However, due to a bug recorded in Sanitize ProcID in syslog messages #202 , the log messages with non-ASCII characters will be dropped when being forwarded to the third party log platform. Although it's still able to forward container lifecycle related logs.

[APP/TASK/検証テスト/0] [OUT] /home/vcap/app  # Will be dropped
[APP/TASK/検証テスト/0] [OUT] Exit status 0   # Will be dropped

Environment

Product Version: 2.13

Resolution

• The bug has been fixed in loggregator-agent-release v6.5.7 . Therefore, to mitigate the issue, you are suggested to upgrade to the Tanzu Application Service for VMs versions with this release packaged. e.g. Tanzu Application Service for VMs 2.13.16
• If you are not able to perform the version upgrade immediately, you can set the task name with ASCII characters to avoid the log messaged being dropped.