Introscope service not being detected during creation time in VMware Tanzu Application Service (TAS) for VMs
Article ID: 297952
Updated On:
Products
VMware Tanzu Application Service for VMs
Issue/Introduction
There has been a change in the Java buildpack v4.20 for Introscope service detection. It now looks for agent_manager_url instead of the URL in VCAP_SERVICES.
Now when creating the service you need to run cf cups introscope -p "agent_manager_url" instead of cf cups introscope -p "url".
Now when creating the service you need to run cf cups introscope -p "agent_manager_url" instead of cf cups introscope -p "url".
Environment
Product Version: 2.3
Resolution
In order to supply the value for defaultProcessName and agentName in the service configuration, you need to use agent_name and agent_default_process_name keys and pass it in the cups command.
When creating the service it would look similar to this:
Then you can assign the values when you are prompted to.
If you need to update existing services, you need to also pass all the keys again. This is because the keys that are not present will be deleted and the agent will not be triggered, since agent_manager_url will not be there.
Updating an existing service will look similar this:
When creating the service it would look similar to this:
cf cups introscope -p "agent_manager_url,agent_name,agent_default_process_name"
Then you can assign the values when you are prompted to.
If you need to update existing services, you need to also pass all the keys again. This is because the keys that are not present will be deleted and the agent will not be triggered, since agent_manager_url will not be there.
Updating an existing service will look similar this:
cf cups introscope -p "agent_manager_url,agent_name,agent_default_process_name"
Feedback
Yes
No
Powered by
