I was recently asked what a clear definition of a HTTP request was. I thought that it was such a good question that I'd share it with the communities.
The basic building block of EUEM is the object. The object is a complete request/respond pair. In the object below, I've highlighted the referrer in blue, request in red and the response in green.
GET / HTTP/1.1
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Firefox/24.0
Accept-Encoding: gzip, deflate
Cookie: s_pers=%20s_nr%3D1380731561884%7C1383323561884%3B%20s_lv%3D1382020889374%7C1476628889374%3B%20s_lv_s%3DMore%2520than%25207%2520days%7C1382022689374%3B%20gpv_p8%3Ddocs.bmc.com%253Adocs%253Adisplay%253Ateam%253AInstallation-deployment%252Bprocess%252Bdoc%252Breview%252Bto%252Bidentify%252Bgaps%7C1382022689769%3B; __utma=246752535.1106976559.1328021376.1363878091.1381165442.51; s_vi=[CS]v1|2793FFBF851D355D-4000010420124D13[CE]; __utmz=246752535.1381165442.51.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none)
If-Modified-Since: Mon, 07 Oct 2013 15:23:25 GMT
HTTP/1.1 200 OK
Last-Modified: Mon, 04 Nov 2013 20:27:02 GMT
Date: Wed, 06 Nov 2013 02:28:04 GMT
Via: 1.1 localhost.localdomain
The requests coming from a particular customer does not represent all the clicks being performed - it represents all of the resources the browser is requesting to display a page or to navigate through the site. As you know, a user will have one session, many pages and many more objects on these pages.
In EUEM - the icons look like:
An Object watchpoint will gather metrics for all objects matching the filter expression defined for the watchpoint.
A Page watchpoint will gather metrics for a group of objects that form a page.
To find out the number of users (sessions) for a particular application, you can create an object or page watchpoint and run a report against that watchpoint with the metric of session arrivals. This will give a report for number of users (sessions) during the report period chosen.
It is possible to have a request and no response. EUEM reports this back to you to show that there was a server side error - ie. a 500 error. EUEM sees the request, but no response. It isn't a complete object but rather an errored object which can be important for end user experience and there is an error report generated by EUEM for trouble shooting. EUEM also has the ability to email or fire out snmp traps.
In this below example I show a report for errors by category and circled the server errors (500's) in red. This report was against all pages but you can create a separate watchpoint to only look at 500 errors.