web_log squid charts added to dashboard_info.js
Ilya committed
May 30, 2017 at 22:46 UTC
ddad054da99f826b202f598cba7bea06d8552008
1 file changed
+29
web/dashboard_info.js
+29
@@ -289,6 +289,35 @@ netdataDashboard.menu = {
289
290
// information about the submenus
291
netdataDashboard.submenu = {
292
+ 'web_log.squid_bandwidth': {
293
+ title: 'bandwidth',
294
+ info: 'Bandwidth of responses (<code>sent</code>) by squid. This chart may present unusual spikes, since the bandwidth is accounted at the time the log line is saved by the server, even if the time needed to serve it spans across a longer duration. We suggest to use QoS (e.g. <a href="http://firehol.org/#fireqos" target="_blank">FireQOS</a>) for accurate accounting of the server bandwidth.'
295
+ },
296
+ 'web_log.squid_responses': {
297
+ title: 'responses'
298
+ },
299
+ 'web_log.squid_requests': {
300
+ title: 'requests'
301
+ },
302
+ 'web_log.squid_hierarchy': {
303
+ title: 'hierarchy',
304
+ info: 'Performance metrics for the squid hierarchy used to serve the requests.'
305
+ },
306
+ 'web_log.squid_squid_transport': {
307
+ title: 'squid_transport',
308
+ info: 'Analysis of the protocols used to receive the requests.'
309
+ },
310
+ 'web_log.squid_squid_cache': {
311
+ title: 'squid_cache',
312
+ info: 'Performance metrics for the performance of the squid cache.'
313
+ },
314
+ 'web_log.squid_timings': {
315
+ title: 'timings',
316
+ info: 'Duration of squid requests. Unrealistic spikes may be reported, since squid logs the total time of the requests, when they complete. Especially for HTTPS, the clients get a tunnel from the proxy and exchange requests directly with the upstream servers, so squid cannot evaluate the individual requests and reports the total time the tunnel was open.'
317
+ },
318
+ 'web_log.squid_clients': {
319
+ title: 'clients'
320
+ },
321
'web_log.bandwidth': {
322
info: 'Bandwidth of requests (<code>received</code>) and responses (<code>sent</code>). <code>received</code> requires an extended log format (without it, the web server log does not have this information). This chart may present unusual spikes, since the bandwidth is accounted at the time the log line is saved by the web server, even if the time needed to serve it spans across a longer duration. We suggest to use QoS (e.g. <a href="http://firehol.org/#fireqos" target="_blank">FireQOS</a>) for accurate accounting of the web server bandwidth.'
323
},