How long does MCC needs to be connected to get license changes updated?

[Suryanto_1]

How long does MCC needs to be connected to get license changes updated?

From security point of view. There isnt a need to keep the connection open persistantly.

We were informed by support updating license and upgrading cluster the requirements are the same.

In order to upgrade the cluster. We leave the connection to MCC for at least an hour every month.

However the license change still dont get updated.

We even test the connection and refresh the credentials as per below but to no avail.

Dynatrace Managed >> Home >> Licensing >> MCC Status

MCC connection status

- Connection shows connected.

- Credentials is OK.

Refresh Mission Control Credentials

- Last refresh status VALID

- Last refresh time less than a day.

[Radoslaw_Szulgo]

The license is checked and, if needed, is updated every 5 minutes. 

[Suryanto_1]

Thats our understanding as well because when we upgrade the cluster. each server actually needs to do a license check in order for upgrade to proceed. Its also mention in the link that its 5 mins interval. 

https://docs.dynatrace.com/managed/managed-cluster/data-privacy/data-exchange-between-a-managed-clus...

Quote from support reply which is kind of absurd honestly especially the last sentence

"Unfortunately, we don't have that info. But I have never heard of an issue from any customer on the licensing page if they have a successful connection to Mission Control.

Perhaps please connect for a whileU (for example few days) and let me know if that resolves the issue.
Not having constant connection is unexpected usage of ONLINE Manged Cluster and you are trying to simulate Offline Managed Cluster with Online Amanaged Cluster.
This is not what we support, and you should use the product as it is designed."

[Radoslaw_Szulgo]

I'm sorry to hear that. 

Are you sure license changes not applied to your cluster are pending?

Please also check if you don't block:

https://mcsvc.dynatrace.com/public/v2.0/license/*

endopoints.

The last thing you can do is to see server.log if there are any exceptions related to the license communication and update.

[Suryanto_1]

Is this where I should be looking at ? Or is another logs or another location?

"cd /usr/var/opt/dynatrace-managed/log/server"
"cat Server.0.0.log | grep exception"

[Radoslaw_Szulgo]

usr/var/opt/dynatrace-managed/log/server is correct. You can also grep for "license"

[Suryanto_1]

Have been through the logs. Have not notice any error during the time when the connection to MCC is open. 

Just to clarify. The communication between Cluster and MCC is always from initialize from Cluster?

For license update is such changes or communication initialize from MCC?  

[Radoslaw_Szulgo]

It's always the cluster that initiates the connection to Mission Control. 

If in doubt, please create a support ticket so we can investigate with you.