I don't see that there is a dynaTrace self-monitoring measure called Estimated CPU Overhead anymore in 4.2. This measure was in previous versions and showed you the percent overhead caused by the dynaTrace agent. Has then been removed or just renamed? I didn't see any other measures similar in name. This helped us get a better idea of how much overhead the dynaTrace agent is causing.
Answer by McKenna J. ·
I have seen this question before, but instead of risking confusing you by me trying to explain it I think what you are looking for is here
Answer by Derek A. ·
Getting a page not found.
Hi Derek
This was a post on the internal forum. I've just moved it to the public forum. you should now be able to access it
Andi
Hmm well in 4.2 the best way to measure CPU overhead in dynaTrace is the use the CPU Sampling under Diagnose Runtime. You will then be able to see how much time is spent in dynaTrace code that has been instrumented into the application. I hope this helps get you started.
Answer by Derek A. ·
Is there a better way to do this other than creating a CPU sampling? I want to be able to better monitor the CPU overhead on 400+ applications and would prefer not to have to set up CPU samplings on all applications and have them run constantly.
Hi Derek
right now there is no better way to measure the "estimated overhead" per agent.
Andi
Answer by Derek A. ·
Are there any plans in later releases that this will become easier to get?
hi Derek,
there's already some approaches that we've been thinking of to get such a (hopefully) meaningful overhead estimate.
so i'm very confident we will have something in future releases, but i cannot tell when that will be.
best,
Christian
JANUARY 15, 3:00 PM GMT / 10:00 AM ET