question

Rene S. avatar image
Rene S. asked ·

Kubernetes service agents stop to monitor after migration from 7.0 to 7.2

Hi,

We executed a migration process from AppMon 7.0 (7.0.26.1017) to AppMon 7.2 (7.2.1.1008) at a customer last friday (11/23) everything went well, but after turned our 2 Kubernetes services collector (https://hub.docker.com/r/dynatrace/collector/), all docker agents couldn't instrumentate their metrics, nor after the recycle of all containers monitored.

Due this all migration was rolled-back to 7.0.

Looking to logs we find:

2018-11-23 20:57:39 UTC INFO [PassiveCollectorSessionInitializer] Collector "coletor-dynatrace-kubernetes@coletor-dynatrace-int-new-767d556864-xb9zw" (version=7.0.0.2469) is trying to connect...
2018-11-23 20:57:42 UTC INFO [CollectorCenter] Collector peer 'coletor-dynatrace-kubernetes@coletor-dynatrace-int-new-767d556864-xb9zw' successfully registered
2018-11-23 20:57:43 UTC INFO [CollectorSyncTransaction] Collector 'coletor-dynatrace-kubernetes@coletor-dynatrace-int-new-767d556864-xb9zw' version (7.0.0.2469) does not match Server version (7.2.0.1697), synchronizing user-defined knowledge sensor packs only. [log message will be suppressed for 1 hours]
2018-11-23 20:57:43 UTC INFO [RemoteCollectorControlClient] The agentres bundles are not synched with the Collector 'coletor-dynatrace-kubernetes@coletor-dynatrace-int-new-767d556864-xb9zw', because the Collector is running with version '7.0.0.2469', but the Server with '7.2.0.1697'
2018-11-23 20:57:43 UTC INFO [CollectorCenter] Sending peer collector list to coletor-dynatrace-kubernetes: []
2018-11-23 21:43:53 UTC INFO [CollectorCenter] Unregistering collector 'coletor-dynatrace-kubernetes@coletor-dynatrace-int-new-767d556864-xb9zw
2018-11-23 21:48:06 UTC INFO [PassiveCollectorSessionInitializer] Collector "coletor-dynatrace-kubernetes@coletor-dynatrace-int-7d9c4c9dcd-xn5cj" (version=7.0.0.2469) is trying to connect...
2018-11-23 21:48:10 UTC INFO [CollectorCenter] Collector peer 'coletor-dynatrace-kubernetes@coletor-dynatrace-int-7d9c4c9dcd-xn5cj' successfully registered
2018-11-23 21:48:10 UTC INFO [InfrastructureAutoDiscovery] added collector: 'coletor-dynatrace-kubernetes@coletor-dynatrace-int-7d9c4c9dcd-xn5cj' to cmdb.
2018-11-23 21:48:11 UTC INFO [CollectorSyncTransaction] Collector 'coletor-dynatrace-kubernetes@coletor-dynatrace-int-7d9c4c9dcd-xn5cj' version (7.0.0.2469) does not match Server version (7.2.0.1697), synchronizing user-defined knowledge sensor packs only. [log message will be suppressed for 1 hours]
2018-11-23 21:48:11 UTC INFO [RemoteCollectorControlClient] The agentres bundles are not synched with the Collector 'coletor-dynatrace-kubernetes@coletor-dynatrace-int-7d9c4c9dcd-xn5cj', because the Collector is running with version '7.0.0.2469', but the Server with '7.2.0.1697'
2018-11-23 21:48:12 UTC INFO [CollectorCenter] Sending peer collector list to coletor-dynatrace-kubernetes: []

This means that this collector (7.0) is not recognized by AppMon server 7.2.

Is there any plan to upgrade this image to 7.2 version? Or is there a way to continue to monitor this environment with another way?

appmon7.07.2migrationkubernetes
10 |2000000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

Radosław J. avatar image
Radosław J. answered ·

The information you have in the log indicates that the migration ended with an error, because the agent files have not been correctly uploaded to the servers where the agents are installed.

This is indicated by the error message:

2018-11-2320:57:43 UTC INFO [RemoteCollectorControlClient]The agentres bundles are not synched with the Collector'coletor-dynatrace-kubernetes@coletor-dynatrace-int-new-767d556864-xb9zw', because the Collectoris running with version '7.0.0.2469', but the Serverwith'7.2.0.1697'

I recommend checking the network connection and performing the migration again. Remember to open ports 8443 (col->srv) and 8441 (agent -> col) for the new version of AppMon Agents.

https://www.dynatrace.com/support/doc/appmon/inst...

1 comment Share
10 |2000000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

Is true, the agents are not updated, because there is no agent version 7.2 for Kubernetes PODs images, 7.0 is the latest version (https://hub.docker.com/r/dynatrace/agent/).

All ports are correctly opened between Srv-Col and Col-Agt.

My point here is to know if the author of Dynatrace Docker images (that is not supported by Dynatrace, but the community instead), have plans to generate new images to version 7.2.

0 Likes 0 · ·
Sebastian K. avatar image
Sebastian K. answered ·

Is there problem to upgrade collector to 7.2?

Regards,

Sebastian

2 comments Share
10 |2000000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

There is not 7.2 version for Kubernete's collector image, this is what I'm asking for here.

All these images are not supported by Dynatrace, but the community instead.

0 Likes 0 · ·

https://github.com/Dynatrace/Dynatrace-AppMon-Docker/blob/master/Dynatrace-Collector/Dockerfile

According to this script, installer of the collector i downloaded while building environment. Generally, you should be able to build such container with appmon 7.2 without any problems.

EDIT:

https://github.com/Dynatrace/Dynatrace-AppMon-Docker/blob/master/Dynatrace-Collector/.env

Modification of this file should be enough to build container with appmon 7.2

1 Like 1 · ·