IIS Web Server measure - Request Rate / Request
1) Need help to understand the definition of Requests - request/sec and MB/sec which reports via IIS Application Process
2) when create dashboard of web server - request - the aggregation of SUM and Count the number huge difference. what do the represent?
Measures that are calculated from UEM or PurePaths are a little bit different. We still calculate them every 10 seconds - but - as you can have more than 1 PurePath in 10 seconds the Count in this case reflects e.g: The number of Web Requests that contribute to that measure in the 10 second interval.
For the Web Request Count the "Count" and "Sum" measure are for instance the same.
It makes sense for the sample. is it same across all typr of measures? for example - which aggregation should I use SUM or COUNT for measure of "Visit Count" or "Web Request Count (under transaction based measures)" or UEM "Visits Action Count"?
The Count represents the number of Measurements we have taken in the selected timeframe. The Sum represents the sum of the values we measured.
To give you some more background. dynaTrace captures measures every 10 seconds. So - within a minute have 6 Measurements (Count = 6). Here is a little example of 3 measurements and the values to it
#1: Value = 10
#2: Value = 20
#3: Value = 15
In this example Count = 3 (because we have 3 measurements). Sum = 45. Avg = 15, Min = 10, Max = 20, ...
Makes sense?
Hi
We capture these two measures through our Web Server Agent. It tells you how much throughput you have on IIS - meaning - how many web requests are processed by IIS per second and how many MegaBytes are transfered (in & out) from IIS to handle these requests. I hope this makes it clear. These are very "standard" measures when it comes to measuring throughput of a Web Server
As for your second question: can you tell me exactly wich measure you are charting with both Sum and Count aggregation and also which values you see? If you can then please attach a screenshot
Andi
