• 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 Cesar Q. · Dec 24, 2014 at 06:39 AM ·

Finding Cause of dynaTrace Server Resource Usage Spikes

Hello All,

I'm seeing what for now are random spikes in the dynaTrace Server resource usage. Memory, CPU, and MPS particularly are spiking.

What's the best way to locate the cause of these? Also, while we're at it, I did some searches here and read some answers on what MPS really means in the Server Health dashboard, but I'm still not completely clear. Can anyone tell me what it really means? Actual Performance Warehouse Measure? Nodes Per Second? Events? (What are events?)

Thanks (smile)

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.

3 Replies

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

Answer by Andreas G. · Dec 26, 2014 at 01:33 AM

So - MPS - is not related with the number of Measures you have in your System Profile. We know that this name is confusing - there is some historical background on this. It means how many data packages we receive from our agents. These packages contain data form PurePaths or from non-PurePath measures.

If you see a Spike in these MPS it means that more data is captured. I would assume this is due to a higher peak in traffic. If you have multiple Collectors you could look at the Collector Health DAshboard and see from which collector this traffic comes in. If you then know which agents are connected to that collector you can look at the PurePaths that came in in that timeframe from these agents. If you have that information you can check whether you have a larger number of PurePaths than average coming in or whether the size of PurePaths is just so much bigger. Maybe there are some batch jobs running during off-business hours that generate very long PurePaths? That is a very common scenario. So - check it out and let mek now what you fin

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 Cesar Q. · Dec 25, 2014 at 04:10 AM

Thanks for the response. A couple of things.

 

I definitely did check out the Deployment Dashboards page beforehand. But, it appears to contradict other posts in the forum. Is MPS then the actual measures from System Profile > Measures being shown per second? Or are they some other measurement?

It's definitely not the PW cleanup. This occurs randomly during all hours.

We're still on 5.6 ( got to convince mulitple business units to let us uplift to 6.1! ), so everything is being handled by the pre-split dT Server. We have intructed all users to use very short timeframes unless absolutely necessary. Finally, many of these spikes occur during non business hours when there are essentially no dT users, so it's not the dashlets.

The Realtime Analyzer Queue Size actually seems stable. But, I do see a spike in Server Traffic, which does make me think it is indeed more load coming in. So there lies my question. Is there an easy way to see where this load is coming from?

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 Andreas G. · Dec 24, 2014 at 09:02 PM

Hi

for details on MPS and other indicators on these health dashboards check out Deployment Dashboards MPS in general indicates how much data is collected from your individual agents. If that number spikes you know you have more traffic on your agents - or - they are hitting some code in your application that causes dynatrace to capture a lot more data, e.G: excessive number of Exceptions, DB, ...

As to your periodic spikes. Do you have some periodic tasks running? There is one task that by default executes at 2AM in the morning. it is the performance warehouse cleanup task which is taking care of performance warehouse data aging. If that is the spike you see then I can tell you that that is expected. if you see other spikes than it be related to e.g: spikes in application traffic in combination with some heavy-weight Business Transaction analysis maybe? Check out the real time analyzer queue. If that is also spiking you know that the CPU and Memory spike is related to PurePath analysis. Otherwise it is more likely related to these background tasks. Another option could be that you have end users refreshing their dashboards very frequently. Most dashboard requests are now handled by the frontend and no longer the backened dynatrace servers. But some requests, e.g: Visit-based Dashlets or Incidents are still handled by the backend dynatrace server. So - if you have end users that have their dynatrace clients open and refreshing these dashlets using a very long timeframe it would also impact CPU and Memory

 

Andi

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

No one has followed this question yet.

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