wire data Structured transactional data passed over HTTP, including information encoded using SOAP/XML SQL transaction details, such as errors, methods used, and stored procedures executed Unique customer IDs, handset type, and credit-control details defined by AVPs and commands contained in Diameter transactions Cross-tier (web, database, storage, etc.) transaction metrics parsed by unique session IDs or other GUID Correlation of network transfer time and server processing time TCP mechanisms such as Nagle delays and throttling HTTP metadata including user-agent, session ID, status code, and IP address HTTP page content including page title, user ID, and transaction values Methods of analyzing wire data Traditional methods of capturing and analyzing wire data include offline network packet analyzers. Newer approaches receive a copy of network traffic from a port mirror (SPAN) or network tap and reassemble those packets into full per-client sessions and transaction streams, analyzing the entire transaction payload in real time and generating metadata on those transactions without storing the actual packets. Bibliography Will Cappelli, Gartner: "Use Data- and Analytics-Centric Processes With a Focus on Wire Data to Future-Proof Availability and Performance Management," March 2016 Will Cappelli, Gartner: “Data Growth Demands a Single, Architected IT Operations Analytics Platform,” September 2013 Will Cappelli, Gartner: “How ITOA Relates to Other Analytics-Driven Disciplines,” November 2013 References Network performance System administration