question

Yifan L. avatar image
Yifan L. asked ·

Looking for guidelines for dynaTrace upgrade in production

We're planning to upgrade our production dynaTrace installation from Version 5.5 to 6.0+.

We currently have both collector and server running on the same physical box with 32 processors, 250GB memory and 1.1TB disk space. We have 60 Java keys available and currently 39 agents are connected. Can we use the same box for 6.0+ installation? Or we should use more powerful server?

Our agent library is at Version 5.0 that is installed on every production box through standard image. It has been working all right for Version 5.5. The 5.5 agent is downloaded and put under /tmp/dynaTrace/agent/download/ on active agent box. Will it continue working for 6.0+? Or we need to have new image that includes 6.0+ agent library. Our Test Center Version 6.0 has been working fine with the same image with 5.0 agent library. But I'm concerned it will be different for production.

DynaTrace in production was installed and is managed by our production support team. We can work on dynaTrace only through the dynaTrace Client. Could you give me some guideline on the order of steps we should request for our production support engineers to work on? And let me know the steps that we should pay special attention to ensure least down time and smooth upgrade?

Thanks,

Yifan


 

 

 

production
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.

Yifan L. avatar image
Yifan L. answered ·

Thank you, Graeme.

Yifan

 

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.

Graeme W. avatar image
Graeme W. answered ·

Yifan,

The bootstrap agent library connects to the Collector specified in the agent configuration (e.g., in the -agentpath option for Java) and checks with the Collector to see if a new version on the agent is available.  If so, it is downloaded from the Collector.  No access to the Internet is required.

-- Graeme

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.

Yifan L. avatar image
Yifan L. answered ·

Kyle and Reinhard,

Could you explain to me the details of how agent library bootstrap triggers the download of the agent library? Is the code in collector or server packages? Or it triggers a download of agent library from Internet?

I need to understand the exact steps for our production upgrade because some of our mid-tier boxes don't have external internet access.

Thanks,

Yifan


 

 

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.

Kyle K. avatar image
Kyle K. answered ·

In short no see Agent Compatibility Matrix for more information but for the best experience I would recommend keeping versions synced up as much as possible

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.

Yifan L. avatar image
Yifan L. answered ·

Reinhard,

You're right that "You will need to update the bootstrap agent at some point". But if it's not required in sync with dynaTrace collector/server 6.2 upgrade, it will be much easier for us. We have different groups and processes for upgrading dynaTrace collector/server vs. upgrading the server image that contains dynaTrace agent library bootstrap.  It's difficult to keep them exactly in sync. If we have agent library bootstrap upgraded first, it will conflict with older version of collector/server. Therefore, if agent library bootstrap upgrade is not required for 6.2 collector/server upgrade, we can upgrade collector/server first, then work on the process to bring up-to-date the agent library bootstrap.

If you can, please let us know: is agent library bootstrap upgrade absolutely required for 6.2 collector/server upgrade?

Talking about "agent monitoring dashboard", I meant the "Monitoring" button on the top right corner of dynaTrace Client that turns the screen to black and shows JVM memory/CPU/thread utilization.

Thanks,

Yifan



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.

Reinhard B. avatar image
Reinhard B. answered ·

Yifan,

I don't know which dashboard you are referring to with a the standard "agent monitoring dashboard" do you mean the transaction flow entry screen?
Generally there have been lots of performance improvements since 5.6, please refer to the release notes.

I highly recommend to upgrade the agents with the newest library, the release notes and techalerts as well as the fixpack notes explain why. I would not recommend to upgrade to 6.0 only but go to 6.2 for optimal improvements in performance etc. 6.0 is 'too old' already. You will need to update the bootstrap agent at some point anyway so better do it now.

I suggest if you need detailed help on-site you should contact your client manager for some enablement services.

Reinhard 

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.

Yifan L. avatar image
Yifan L. answered ·

Reinhard,

e.g. the standard agent Monitoring Dashboard takes long time to load even when I set the timeframe to 6 hours. The dynaTrace self-monitoring Deployment Dashboard always shows the memory usage is very high.

Could you also confirm my understanding with the other question: if we upgrade to 6.0, we don't need the upgrade our agent bootstrap library; but if we upgrade to 6.1+, we have to create a new image with the newer agent library. 

Thanks,

Yifan

 

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.

Dave M. avatar image
Dave M. answered ·

When you connect the database initially to the new version, the schema will be automatically upgraded.  The session directory will work as is in the new version.  Just be sure to follow the 6. 1 Upgrade and Migration Guide.

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.

Arumit G. avatar image
Arumit G. answered ·

Hi, 

We're also planning to upgrade our production dynaTrace installation from Version 5.5 to 6.1.

Question is  — How to retain the historical data i.e. performance warehouse (Oracle) and session data which we can access in Dynatrace 6.1. 

After Dynatrace 6.1 server installation, if I give the same database details and same session path, will it retain the 5.5 historical data or it will wipe (rebuild) the old (5.5) tables and create a new database table structure.

Thanks,

Arumit

 

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.

Yifan L. avatar image
Yifan L. answered ·

From your responses, I see our server resources are good enough. However, I often see slowness to load the dashboards. Almost always, I have to change the timeframe from the default (24 hrs, 72 hrs) to 30 minutes. 

I looked at the Deployment Dashboard. The CPU is below 20%, memory is ~90%. There's long GC suspension time. The server memory is set to 12g which is the maximum. Please advice what we can do to improve the dynaTrace server performance. Will upgrade help?

Thanks,

Yifan

 

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.

Yifan,

what kind of dashboards are you referring to? I really depends on the data you are presenting. With a timeframe of 24 or even 72hrs e.g. PurePath based dashlets potentially have to go through all Purepaths within that timeframe (that could be 100s GB of data read from a disk and then processed). If the data is measure based (charts only) the data comes from the performance warehouse which should be considerably fast.

Reinhard 

0 Likes 0 · ·