• 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
        • Enterprise Synthetic Monitoring
      • Synthetic Classic
        • Synthetic Classic Open Q&A
      • BSM Open Q&A
  • Home /
  • Public Forums /
  • Dynatrace /
  • Dynatrace Open Q&A /
avatar image
Question by Alex L. · Jun 02, 2017 at 07:16 AM · oneagent

How much overhead does the oneagent take?

Comment

People who like this

0 Show 0
10 |2000 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users

5 Replies

· Add your reply
  • Sort: 
  • Most voted
  • Newest
  • Oldest
avatar image
Best Answer

Answer by Patrick H. · Jun 02, 2017 at 07:38 AM

I can't give a solid number, but the overhead is kept so that there is no impact on the response time of the application. The Watchdog is also Monitoring the overhead of the One Agent and will for example minimize Network Monitoring if the Overhead goes above 5% CPU.

Comment
Florian O.
Wai C.

People who like this

2 Show 0 · Share
10 |2000 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users
avatar image
Best Answer

Answer by James K. · Sep 11, 2017 at 03:32 PM

I'll paste the responses with information from dev directly form a support case where this was asked:

The overhead of the Agent (regarding response time, CPU, memory & network traffic) depends on so many factors and their correlations that it's just impossible to estimate it upfront.
Such factors include, but are not limited to e.g.:

  • from the application perspective:
    • used technologies (Java, .NET, PHP, Apache, node.js, ...)
    • involved frameworks
    • requests per second (or some other load indicator)
    • general CPU consumption
    • number of concurrently executed threads
    • amount of remote communication and IO interaction
    • error handling, e.g. number of thrown exceptions
    • complexity of the code in general
  • from the environment perspective:
    • operating system and version
    • hardware, e.g. CPU
    • any potential virtualization in place
    • disk & network throughput
    • inter-process mutexes and other dependencies
  • from the Agent & configuration perspective:
    • type of Agent (OS Agent, Java Agent, Network Agent, Log Agent, ...)
    • number of placed sensors & instrumented methods
    • level of detail of captured information

Measuring the overhead is also non-trivial, as the Agent itself is part of the whole system and can as such not easily measure itself. The only really reliable way to measure the overhead is and always will be to make reasonable load tests with an external tool including reproducible load and warmup/cooldown phases executed multiple times with and without the Agents.
However, over the years we investigated multiple approaches to try to estimate and limit the Agent overhead. Some of those turned out to be effective (e.g. around Auto-Sensor overhead limitations) and are implemented in the Agent code itself. Also, we're always trying to make the Agents even more robust also in terms of overhead.
In addition to that we're always selecting our default configurations to be as low-overhead and as production-ready as possible while still providing valuable information.
To ensure this we execute automated performance tests on a daily basis which will instantly show us if something got better or worse.

___

so here's what we do in terms of overhead measurement and reduction:

  • in Dynatrace & AppMon Special Agents (OneAgent and Classic Agent)
    • check overhead of Auto-Sensors in the process and adapt it to not exceed fixed 1-3% (in Dynatrace, depending on Agent type) or configurable 1%-20% (in AppMon)
    • if network is too slow for the captured data, creation of new PurePaths will be reduced and finally data will be discarded
    • also some Sensors will reduce data capturing when certain limits are reached (e.g. Exception Sensor -> limit stacktrace capturing)
  • in Dynatrace Network Agent
    • turning off the network data collection as soon as CPU reaches certain limit (5% or so)
Comment
Kristof R.
Davorin-Josip K.

People who like this

2 Show 0 · Share
10 |2000 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users
avatar image

Answer by Pawel B. · Oct 03, 2017 at 09:47 AM

Results may vary, depending on the environment. It's best to take a free trial to be 100% sure. I have although taken a look at one of our internal tenants monitoring our production systems and found following data:

Working set size:Oneagent: 80MB AVG , 204MB MAX plus optional components - log (18MB and 23MB) and network (56MB and 59MB respectively).

CPU usage: Oneagent: 0.51% AVG, 2.73% MAX plus optional components - log (0.05% and 0.16%) and network (0.08% and 1.8% respectively).

Network: Oneagent 619Bps AVG, 730Bps MAX (that includes network component) plus optional component - log 298Bps AVG, 348Bps MAX.

Comment
Florian O.
Kristof R.
Bhagavad D.
Joel S.

People who like this

4 Show 0 · Share
10 |2000 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users
avatar image

Answer by Kay K. · Sep 11, 2017 at 02:50 PM

Can someone from dynatrace be a bit more precise like here https://www.dynatrace.com/resources/ebooks/javaboo...?

How much is the overhead for cpu, ram, heap, network, responstime? It is allways a question by the customer and angry operators.

Comment

People who like this

0 Show 0 · Share
10 |2000 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users
avatar image

Answer by Gautier B. · Nov 30, 2017 at 11:55 AM

I have also made some tests. As said by the previous persons, the impact on CPU/Memory/network (threads for PHP) may vary according your application, but the are of relatively low impact.

But I can say that the most important thing to monitor is the response time of your application, here may be the real impact.

Comment

People who like this

0 Show 0 · Share
10 |2000 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users

Your answer

Hint: You can notify a user about this post by typing @username

Up to 10 attachments (including images) can be used with a maximum of 52.4 MB each and 262.1 MB total.

Welcome to the
Dynatrace Community Forums

Check out the Forum User Guide and Forum Guidelines to learn how to get started.

Community Member of the Month
February 2019

Announcing Dynatrace's Community Member of the Month for February 2019, Larry R.! Click here to read more!

Employee Member of the Month
February 2019

Announcing Dynatrace's Employee Member of the Month for February 2019, Dave M.! Click here to read more!

Live webinar: AIOps done right through enhanced Dynatrace AI root cause detection

Learn the enhanced capabilities of the next generation Dynatrace AI root cause analysis and how to feed it with your own data sources.
Wednesday, February 20, 2019
Register today!

Live webinar: AIOps done right through enhanced Dynatrace AI root cause detection

Learn the enhanced capabilities of the next generation Dynatrace AI root cause analysis and how to feed it with your own data sources.
Wednesday, February 20, 2019
Register today!

NAM 2019 Beta is available

Would you like to have an early taste of what we have cooked up for 2019? We would love to hear your feedback and improve some of the new features. Check NAM 2019 Beta release notes.
Sign up today!

Follow this Question

Answers Answers and Comments

28 People are following this question.

avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image avatar image

Related Questions

Report generation on application performance ( oneagent) 1 Answer

Why are we not getting Throughput, IOPS and latency metrics for a storage volume? 3 Answers

Is possible to split services automatically detect by Dynatrace? 1 Answer

Not seeing k8 labels in process view 1 Answer

Asynchronously Load Dynatrace RUM Agent via Tealium 1 Answer

Forum Tags

java user management dotnet redis docker ios davis log analytics gui mobileapp database cloud foundry usability services faq management zones user sessions test automation Dynatrace Managed amazon web services plugins php android javascript processes monitoring nodejs sso rest api appmon license dynatrace saas mobile monitoring user tagging installation nam aix oneagent sdk purepath network synthetic monitors apache hosts iis user actions paas azure http monitor linux mongodb mysql dashboard tipstricks rest openshift mission control activegate webserver servicenow kubernetes rum host monitoring cmc key user actions notifications openstack technologies configuration account continuous delivery tagging postgresql security smartscape high five award agent documentation alerting auto-detection cassandra administration vmware oneagent
  • 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
      • Enterprise Synthetic Monitoring
    • Synthetic Classic
      • Synthetic Classic Open Q&A
    • BSM Open Q&A