Mission Control in Development environments

[sandre]

In our development environment, the security team does not allow outbound connections from the local area. This became a problem when we implemented Dynatrace Managed for development. From what I understand, Dynatrace Managed will be disabled if the cluster cannot connect to Mission Control for 14 days. Our Dyantrace Managed Development is rarely used, we only use it when testing application development.

1. Can we connect to Mission Control only when we are using it? If so, does the connection process require additional configuration?
2. If it hasn't been connected for a long time, do we need to request a new license again?

Thanks.

[Radoslaw_Szulgo · Accepted solution]

When your cluster is not connected for 14 days only overages will be disabled.

Can you provide requirements from the security team to keep the connection open? That will be beneficial so we can support your dev cluster properly.

[sandre]

If I reactivate the connection on the 20th day, will the cluster connect to Mission Control automatically? Or should I request a new license?

Unfortunately the security team does not allow persistent outbound connections to the development environment for any reason. I tried to explain the situation to them, but I didn't get approval.

[Radoslaw_Szulgo]

It will reconnect automatically.