• Forums
    • Public Forums
      • Community Connect
      • Dynatrace
        • Dynatrace Open Q&A
      • Application Monitoring & UEM
        • AppMon & UEM Open Q&A
      • Network Application Monitoring
        • NAM Open Q&A
  • Home /
  • Public Forums /
  • Application Monitoring & UEM /
  • AppMon & UEM Open Q&A /
avatar image
Question by Pankaj K. · Dec 17, 2012 at 03:07 AM ·

4.2 Server compability with 4.1 agents and_or collectors

We are planning our upgrade to dynaTrace server version 4.2 from 4.1. However we have some questions:

Are there compability issues with any of the following configurations?

1. 4.2 dynaTrace Server, 4.2 dynaTrace Collector  with 4.1 dynaTrace agents

This configuration will exist because in our production environment, we may not be able to restart the monitored processes (application pools, windows services) right away.

Will the agents still collect data with this configuration? Or will they stop collecting data? Was this configuration tested?

2. 4.2 dynaTrace Server with 4.1 dynaTrace Collector with 4.1 dynaTrace agents

We have overseas collectors that cannot be restarted due to various reasons. So these collectors may not get updated to 4.1. Will there be any issues under this configuration? Was this configuration tested?

Comment

People who like this

0 Show 0
10 |2000000 characters needed characters left characters exceeded
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Viewable by all users

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

2 Replies

  • Sort: 
  • Most voted
  • Newest
  • Oldest
avatar image

Answer by Derek A. · Dec 27, 2012 at 07:46 PM

This may be better documented in the 4.2 Release notes or 4.1 to 4.2 migration guide, but from my experience I can tell you that your option 1 is compatible because I fell in this scenerio and I think option 2 is compatible too. My Server and Collectors were at 4.2 and my agents were at 4.1 and I didn't have to restart any of the agents except for small number of applications on Windows and Linux (this was probably more of an environment issue on my end). The 4.1 agents should continue to work fine and when they do eventually get restarted, they will pull down the 4.2 files from the other components so there isn't even a need to install the 4.2 agent at all.

Comment

People who like this

0 Show 0 · Share
10 |2000000 characters needed characters left characters exceeded
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Viewable by all users

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

avatar image

Answer by Pankaj K. · Dec 27, 2012 at 06:53 PM

Anyone have any insight? Should I log a support case for this instead?

Comment

People who like this

0 Show 0 · Share
10 |2000000 characters needed characters left characters exceeded
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Viewable by all users

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

How to get started

First steps in the forum
Read Community User Guide
Best practices of using forum

NAM 2019 SP5 is available


Check the RHEL support added in the latest NAM service pack.

Learn more

LIVE WEBINAR

"Performance Clinic - Monitoring as a Self Service with Dynatrace"


JANUARY 15, 3:00 PM GMT / 10:00 AM ET

Register here

Follow this Question

Answers Answers and Comments

2 People are following this question.

avatar image avatar image

Forum Tags

dotnet mobile monitoring load iis 6.5 kubernetes mainframe rest api dashboard framework 7.0 appmon 7 health monitoring adk log monitoring services auto-detection uem webserver test automation license web performance monitoring ios nam probe collector migration mq web services knowledge sharing reports window java hybris javascript appmon sensors good to know extensions search 6.3+ server documentation easytravel web dashboard kibana system profile purelytics docker splunk 6.1 process groups account 7.2 rest dynatrace saas spa guardian appmon administration production user actions postgresql upgrade oneagent measures security Dynatrace Managed transactionflow technologies diagnostics user session monitoring unique users continuous delivery sharing configuration alerting NGINX splitting business transaction client 6.3 installation database scheduler apache mobileapp RUM php dashlet azure purepath agent 7.1 appmonsaas messagebroker nodejs 6.2 android sensor performance warehouse
  • Forums
  • Public Forums
    • Community Connect
    • Dynatrace
      • Dynatrace Open Q&A
    • Application Monitoring & UEM
      • AppMon & UEM Open Q&A
    • Network Application Monitoring
      • NAM Open Q&A