Application name is not updated and reflected in the firehose logs after renaming an application in VMware Tanzu Application Service (TAS) for VMs 2.8.7

Products

• VMware Tanzu Application Service for VMs

Issue/Introduction

Starting in TAS 2.8.7+, the application name is not updated and reflected in the firehose logs after renaming an application.

For instance, if you update a running application to have a new name, this new name is not reflected in the cf nozzle output which grabs logs and metrics from the firehose.

origin:"rep" eventType:ValueMetric timestamp:1589208266703635417 deployment:"cf-f771fdaeb10595d332f7" job:"diego_cell" index:"9aeab32b-d5ce-4e7b-97a3-b3df01bb1104" ip:"10.##.##.73" tags:<key:"app_id" value:"333d58fa-c930-4583-b9d9-900077abeccb" > tags:<key:"app_name" value:"app-blue-deployment" > tags:<key:"instance_id" value:"3" > 

Environment

Product Version: 2.8

Resolution

Simply restarting the application is enough to fix this issue, as an application restart will update any cached versions of the old application name.

For instance, if you pushed the following app and named it App-A:

$ > cf push App_A

$ > cf rename App_A App_B

It is possible that the above operation of renaming the app has not taken effect for the firehose. In this case, simply stop and start the application.

$ > cf stop App_B

$ > cf start App_B

This should clear up any caches with the old app name.

For blue green deployments you can use the following sequence to ensure the app name is updated throughout the system:

$ > cf rename App App-old

$ > cf push App (set routes, etc...)

$ > cf delete App-old

As of TAS 4.0, customers who rename apps will now see emitted logs and metrics quickly tagged with the new application name without the need for an application restart.