What information can Pion capture?
Pion can capture and record just about any piece of information that exists within the conversations that visitors have with your website. Pion provides the most accurate, reliable and detailed data possible to satisfy the needs of even the most demanding business users.
Pion captures any HTTP request or response header, anything contained within the requests or responses, and a wealth of detailed timing and performance metrics. This includes cookies, IP addresses, browser information, form submissions, login ids, AJAX data, page load times, and much more. You can easily customize Pion to generate custom fields derived from page content and other sources.
Here is a list of some of the fields Pion populates out-of-the-box:
Time stamps
| date | Date of the event (2008-07-20) |
| time | Time of the event (12:20:21) |
| date-time | Date and time of the event (2008-07-20 12:20:21) |
| epoch-time | Number of seconds since the epoch (January 1, 1970) |
| clf-date | Date and time of the event (CLF format) |
| request-start-time | Date and time of the first request packet (20080720T122021.123213) |
| request-end-time | Date and time of the last request packet (20080720T122021.123213) |
| response-start-time | Date and time of the first response packet (20080720T122021.123213) |
| response-end-time | Date and time of the last response packet (20080720T122021.123213) |
Basic Fields
Note: These fields correspond to what is normally available using web server log files.
| status | The HTTP status code returned to the client |
| comment | The HTTP status message returned to the client |
| method | The HTTP method of the request (GET, POST, etc.) |
| uri | The requested resource (including query) |
| uri-stem | The requested resource (excluding query) |
| uri-query | The query portion of the requested resource |
| request | The request line exactly as it came from the client |
| host | The Host HTTP request header |
| referer | The Referer HTTP request header |
| useragent | The User-Agent HTTP request header |
| cookie | The Cookie HTTP request header |
| set-cookie | The Set-Cookie HTTP response header |
| cs-content-type | The Content-Type HTTP request header |
| content-type | The Content-Type HTTP response header |
| location | The Location HTTP response header |
| rfc931 | The remote logname of the user |
| authuser | The username as which the user has authenticated himself |
| cached | 1 if the response was cached, 0 if it was not |
| sitename | The Internet service name and instance number that was running on the client |
| cs-version | The protocol version that the client used |
Network Fields
| proxy-ip | IP address of the closest proxy server in dot-quad notation |
| c-ip | IP address of the client in dot-quad notation |
| s-ip | IP address of the server in dot-quad notation |
| c-mac | Client packets MAC address in hexadecimal format |
| s-mac | Server packets MAC address in hexadecimal format |
| c-port | Client port number for the HTTP request |
| s-port | Server port number for the HTTP request |
| cs-packets | The total number of packets sent from client to server |
| sc-packets | The total number of packets sent from server to client |
| cs-ack-packets | The number of acknowledgement packets sent from client to server |
| sc-ack-packets | The number of acknowledgement packets sent from server to client |
| cs-missing-packets | The number of missing packet gaps detected within the request |
| sc-missing-packets | The number of missing packet gaps detected within the response |
| cs-duplicate-packets | The number of duplicate packets sent from client to server |
| sc-duplicate-packets | The number of duplicate packets sent from server to client |
| cs-data-packets | The number of data packets sent from client to server |
| sc-data-packets | The number of data packets sent from server to client |
| cs-bytes | The number of bytes sent from client to server |
| sc-bytes | The number of bytes sent from server to client |
| bytes | The total number of bytes transferred |
| request-status | HTTP request status: 0=NoData, 1=MissingEnd, 2=MissingMiddle, 3=OK |
| response-status | HTTP response status: 0=NoData, 1=MissingEnd, 2=MissingMiddle, 3=OK |
| tcp-status | TCP handshake status: 0=OK, 1=Reset, 2=Ignored |
| refused | Number of HTTP requests that were refused by the server |
| canceled | Number of HTTP responses that were canceled early by the client |
Performance Metrics
| time-taken | Number of microseconds that it took to complete an HTTP event, from the end user's perspective |
| cs-send-time | Number of microseconds that it took the client to send an HTTP request |
| cs-ack-time | Number of microseconds that it took the server to acknowledge receipt of the HTTP request |
| sc-reply-time | Number of microseconds that it took the server to start replying to an HTTP request |
| sc-send-time | Number of microseconds that it took the server to send an HTTP response |
| sc-ack-time | Number of microseconds that it took the client to acknowledge receipt of the HTTP response |
| ssl-time | Number of microseconds that it took to negotiate an SSL handshake |
| ssl-version | SSL protocol version used for encryption, or undefined if not encrypted |
| data-center-time | Number of microseconds from the last request packet to the last response packet |
| cp-rtt | Average round trip time in microseconds from the client to the Pion server |
| ps-rtt | Average round trip time in microseconds from the Pion server to the protocol server |
| cp-rtt-sum | Sum of all round trip time measurements from the client to the Pion server |
| ps-rtt-sum | Sum of all round trip time measurements from the Pion server to the protocol server |
| cp-rtt-packets | Number of round trip time measurements from the client to the Pion server |
| ps-rtt-packets | Number of round trip time measurements from the Pion server to the protocol server |
| page-load | Number of microseconds that it took to load a page view |
| page-load-redirect | Number of microseconds that it took redirecting a page view |
| page-load-base | Number of microseconds that it took loading a page's HTML |
| page-load-content | Number of microseconds that it took loading a page's content |
Visitor & Session Tracking
| session-group | The group to which a visitor session was assigned (based upon hostname) |
| session-id | Unique identifier assigned to the clickstream visitor session |
| visitor-id | Unique identifier assigned to the visitor (across sessions) |
| cookie-id | Cookie identifier used for sessionizing clickstream ("name:value") |
| page-number | Page sequence number for page view events |
| request-number | Request sequence number for HTTP events |
| page-title | Page title, extracted from HTML content for page events |
| page-content | Response content (normally HTML) for the http-event which triggered the new page-event |
| new-page | 1 if the http-event triggered the generation of a new page |
| new-session | 1 if the (http or page) event triggered the generation of a new visitor session |
| page-object | 1 if the http event matched the page object detection rules |
| page-hits | Number of HTTP requests associated with the page view |
| page-dwell | Number of seconds spent viewing a completed page view |
| session-pages | Number of page views associated with a visitor session |
| session-hits | Number of HTTP requests associated with a visitor session |
| session-dwell | Number of seconds spent viewing all pages within a visitor session |
| session-length | Number of seconds between the first and last session requests |
| visitor-status | New visitor: how determined? c=Cookie, v=visitorDB, a=anonDB |
Other Fields
| cs-content | Payload content sent from client to server |
| sc-content | Payload content sent from server to client |
| cs-headers | All HTTP headers sent from client to server |
| sc-headers | All HTTP headers sent from server to client |
| content-id | Unique MD5 hash of response content |
| robot | 1 if the event was generated by a robot visitor, undefined if it was not |
Submitted by Mike Dickey on Tue, 06/22/2010 - 12:59
