74:, which is system self-reported information typically in the form of logs sourced from elements like network routers, servers, and other equipment. Unlike those forms of machine-generated data, which are dependent on the logging configurations of those devices, wire data is defined by wire and transport protocols. There is a small amount of overlap between wire data and machine-generated data but also significant differences. For example, web server logs typically record
54:, wire data will play a more important role than machine data for analytics in the future: "While log data will certainly have a role in future monitoring and analytics, it is wire data—radically rethought and used in new ways—that will prove to be the most critical source of data for availability and performance management over the next five years."
46:
Wire data is the observed behavior and communication between networked elements which is an important source of information used by IT operations staff to troubleshoot performance issues, create activity baselines, detect anomalous activity, investigate security incidents, and discover IT assets and
78:
responses, indicating that a web page was served to a client. However, web servers do not log the transaction payload and so would not be able to show which HTTP status code 200 responses were for pages with a “service unavailable” message. That information is contained in the wire data or
61:
teams. In these types of scenarios, wire data is used to measure order transactions for real-time reporting on transaction volume, success, and failure rates; tracking patient admission rates at hospitals; as well as reporting on the weights and measures of airplanes prior to take-off.
144:(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.
153:
Will
Cappelli, Gartner: "Use Data- and Analytics-Centric Processes With a Focus on Wire Data to Future-Proof Availability and Performance Management," March 2016
140:
Traditional methods of capturing and analyzing wire data include offline network packet analyzers. Newer approaches receive a copy of network traffic from a
34:
containing the bi-directional data payload. More precisely, wire data is the information that is communicated in each layer of the
201:
234:
179:"Use Data- and Analytics-Centric Processes With a Focus on Wire Data to Future-Proof Availability and Performance Management"
38:(Layer 1 not being included because those protocols are used to establish connections and do not communicate information).
229:
156:
Will
Cappelli, Gartner: “Data Growth Demands a Single, Architected IT Operations Analytics Platform,” September 2013
102:
58:
27:
26:
is the information that passes over computer and telecommunication networks defining communications between
71:
122:
112:
Cross-tier (web, database, storage, etc.) transaction metrics parsed by unique session IDs or other
106:
159:
Will
Cappelli, Gartner: “How ITOA Relates to Other Analytics-Driven Disciplines,” November 2013
75:
141:
223:
98:
SQL transaction details, such as errors, methods used, and stored procedures executed
31:
88:
Structured transactional data passed over HTTP, including information encoded using
50:
According to a March 2016 research note from
American IT research and advisory firm
57:
Real-time wire data streams are also important sources of data for business and
35:
128:
HTTP metadata including user-agent, session ID, status code, and IP address
101:
Unique customer IDs, handset type, and credit-control details defined by
131:
HTTP page content including page title, user ID, and transaction values
51:
178:
79:
transaction payload and is not necessarily logged by the server.
113:
89:
118:
Correlation of network transfer time and server processing time
93:
66:
Distinction between wire data and system self-reported data
83:Examples of information derived from wire data
8:
16:Format of network information as transmitted
169:
30:devices. It is the result of decoding
7:
202:"Morgan Stanley Turns To Wire Data"
14:
204:. Wall Street & Technology
136:Methods of analyzing wire data
1:
32:wire and transport protocols
70:Wire data is distinct from
251:
105:and commands contained in
59:operational intelligence
121:TCP mechanisms such as
72:machine-generated data
235:System administration
103:attribute–value pairs
47:their dependencies.
76:HTTP status code 200
230:Network performance
28:client and server
242:
214:
213:
211:
209:
197:
191:
190:
188:
186:
177:Cappelli, Will.
174:
250:
249:
245:
244:
243:
241:
240:
239:
220:
219:
218:
217:
207:
205:
199:
198:
194:
184:
182:
176:
175:
171:
166:
150:
138:
85:
68:
44:
17:
12:
11:
5:
248:
246:
238:
237:
232:
222:
221:
216:
215:
200:Patel, Zarna.
192:
168:
167:
165:
162:
161:
160:
157:
154:
149:
146:
137:
134:
133:
132:
129:
126:
125:and throttling
119:
116:
110:
99:
96:
84:
81:
67:
64:
43:
40:
15:
13:
10:
9:
6:
4:
3:
2:
247:
236:
233:
231:
228:
227:
225:
203:
196:
193:
180:
173:
170:
163:
158:
155:
152:
151:
147:
145:
143:
135:
130:
127:
124:
120:
117:
115:
111:
108:
104:
100:
97:
95:
91:
87:
86:
82:
80:
77:
73:
65:
63:
60:
55:
53:
48:
41:
39:
37:
33:
29:
25:
21:
206:. Retrieved
195:
183:. Retrieved
172:
148:Bibliography
139:
123:Nagle delays
109:transactions
69:
56:
49:
45:
23:
19:
18:
142:port mirror
224:Categories
164:References
24:wire image
208:March 14,
185:March 11,
181:. Gartner
42:Relevance
36:OSI model
20:Wire data
107:Diameter
52:Gartner
210:2014
187:2016
114:GUID
90:SOAP
94:XML
22:or
226::
212:.
189:.
92:/
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.