How is "Total PurePath Count" calculated in the Agents Overview dashlet?

Ok, thanks for the suggestions, Thomas.  I'm just annoyed that the Agent Overview dashboard shows the timeframe control, when that really has no effect on what is shown.

Hi Mark,

I just wanted to point out that you can chart some agent information without capturing data at regular intervals. You can chart any PurePath measure (PurePath Duration for example) and change the aggregation to Count. Since this measure is stored in the PW you will be able to set the timeframe and resolution to last 6 hours, for example, to see a total count of PurePaths broken down by agent for the last 6 hours. Another  option would be a Dynamic Measure Matrix. 

Tom 

Is there another discussion somewhere about this behavior?  Because I've been using DT for a number of months, and I only just now learned, the hard way, that changing the timeframe value has no effect whatsoever on the data being displayed, and I find that (mis)behavior extremely aggravating.

I mean, if I set the timeframe to a 5-min interval, then as I scroll backwards and forwards, I expect it to show me only info relating to that 5-minute window of activity, whether I'm looking at Agent Overview or dynaTrace Server Health.  Otherwise, if the time selector has no effect, then you should gray it out.  And then when someone's in the editor, constructing an Agent Overview dashboard, it's particularly misleading to present the timeframe selector, as if their use of different timeframe values would have any effect whatsoever on the resulting display, when in fact it doesn't.  (sigh)

This means, though, that there is no straight-forward way of getting a summary of agent information strictly over the last <n> minutes, in terms of event count, purpaths, which agents hit "license exhausted" errors, etc.  The only option is to capture that data at regular intervals and look at the deltas.  Awkward...

hi Thomas & Pierrick,

the numbers in the agent overview dashlet are not timeframe-specific, but just plain total.
this means: as soon as an agent is started, the numbers start at 0 (well, except for the timestamp of course ) and get incremented from then on.

however, it's still not so obvious what exactly is shown here.
those PurePath and Event based values are calculated on the server and kept in-memory only. this means, these values are resetted in 3 cases:

• the agent is newly started (obviously) 
• the collector, which the agent is connected to, is restarted
• the server is restarted

hope this helps,

Christian

Thomas,

That's a great question and I would be interested in the answer if you find it!

My guess would be that it has to do with the Instrumentation Map stored on the Collector, and therefore it would be updated whenever a purepath has been processed.

Perhaps it is stored directly on the server ?

If the time frame doesn't have an impact, I would imagine the count started when the Agent was deployed.

Please let me know if you find out and have a great day!

Pierrick.