Query Regarding Dynatrace License Renewal and Configuration

Note: please note that Liferay has renamed its Liferay Experience Could offerings to Liferay SaaS (formerly LXC) and Liferay PaaS (formerly LXC-SM).

Issue

• Dynatrace is displaying a License Expired message. As per Liferay's guidance in this article: Liferay PaaS Dynatrace Update, we need to generate a new access token in Dynatrace and configure it in the Liferay service environment variables. We have a few queries before proceeding with this task:

  1. If we configure the access token in the Liferay service environment variables, will this cause the service to restart? If so, what impact, if any, will this have on Liferay during the restart?

  2. In the Liferay LCP.json file, there are two variables related to Dynatrace:

     • The "LCP_PROJECT_MONITOR_DYNATRACE_TENANT" variable contains the value "xxxxx", which I believe is common for all users.
     • If I generate a new access token and configure it in the "LCP_PROJECT_MONITOR_DYNATRACE_TOKEN" variable, will this work as expected? Can you confirm this?

Environment

• Liferay PaaS

Resolution

• Regarding question 1:
   
  You need to deploy Liferay again with the NEW Tenant and Token values. Then, a restart will happen as part of the deployment.
   
  Regarding
   
  

  In the Liferay LCP.json file, there are two variables related to Dynatrace:

  The "LCP_PROJECT_MONITOR_DYNATRACE_TENANT" variable contains the value "xxxxx", which I believe is common for all users.

  No, each customer has its own Tenant ID. 
   
  Regarding
   
  

  If I generate a new access token and configure it in the "LCP_PROJECT_MONITOR_DYNATRACE_TOKEN" variable, will this work as expected? Can you confirm this?

  Yes, you should generate a new Dynatrace Token in the new Dynatrace 
   
  To get the token, navigate to Manage → Deploy Dynatrace → Set up PaaS Integration, then enter the environment ID and click Generate new token.
   
  Document for reference: Application Metrics