Displaying #traffic-server/2015-12-29.log:

Tue Dec 29 00:32:50 2015  biilmann:Joined the channel
Tue Dec 29 02:08:50 2015  biilmann:Joined the channel
Tue Dec 29 03:22:35 2015  biilmann:Joined the channel
Tue Dec 29 03:33:37 2015  es:Joined the channel
Tue Dec 29 03:55:16 2015  biilmann:Joined the channel
Tue Dec 29 04:54:26 2015  es:Joined the channel
Tue Dec 29 07:01:08 2015  micko:Joined the channel
Tue Dec 29 12:03:04 2015  niq:Joined the channel
Tue Dec 29 13:58:18 2015  dustywusty:Joined the channel
Tue Dec 29 14:10:05 2015  dustywusty:Joined the channel
Tue Dec 29 14:20:22 2015  adrian__:Joined the channel
Tue Dec 29 14:22:16 2015  adrian-vellance:Joined the channel
Tue Dec 29 14:33:15 2015  adrian-vellance:Hey all, I was wondering if somebody could answer a 'Log Field Slicing' question:
Tue Dec 29 14:33:59 2015  adrian-vellance:I have this in my logs as format: " %<cqtd> %<cqhm> %<cqup> %<cqus> %<pssc> %<pscl> "
Tue Dec 29 14:34:25 2015  adrian-vellance:which gives me something like this: "2015-12-29 GET vellance/static/fonts/opensans_600.woff http 304 0"
Tue Dec 29 14:34:51 2015  adrian-vellance:but what I want is something like this: "2015-12-29 GET vellance static fonts/opensans_600.woff http 304 0"
Tue Dec 29 14:35:39 2015  adrian-vellance:so the first two field of the URI should be split into two separate columns. Is that possible, or can I only split on word length?
Tue Dec 29 14:36:01 2015  adrian-vellance:(Or am I in completly the wrong channel?)
Tue Dec 29 15:19:31 2015  dcarlin:bluuurgh: I don't think log field slicing will do what you want
Tue Dec 29 15:20:27 2015  dcarlin:its primarily used for long strings, you can truncate the string
Tue Dec 29 15:23:59 2015  bluuurgh:bummer… thx
Tue Dec 29 15:37:50 2015  es:Joined the channel
Tue Dec 29 15:42:36 2015  es1:Joined the channel
Tue Dec 29 15:57:41 2015  psp1:Joined the channel
Tue Dec 29 16:00:36 2015  jumby:Joined the channel
Tue Dec 29 16:01:56 2015  psp:Joined the channel
Tue Dec 29 16:33:38 2015  biilmann:Joined the channel
Tue Dec 29 16:44:57 2015  biilmann:Joined the channel
Tue Dec 29 17:21:28 2015  biilmann:Joined the channel
Tue Dec 29 18:11:09 2015  niq:Joined the channel
Tue Dec 29 18:37:27 2015  biilmann:Joined the channel
Tue Dec 29 18:54:21 2015  biilmann:Joined the channel
Tue Dec 29 18:57:50 2015  biilmann:so what's the best way to suggest a new API method?
Tue Dec 29 18:58:11 2015  biilmann:working on lazy loading SNI certificates from a plugin
Tue Dec 29 18:59:28 2015  biilmann:but found that right now all the logic for actually applying the records.config settings to a new SSL_CTX is scattered around SSLUtils.cc
Tue Dec 29 18:59:52 2015  biilmann:so it would be great to have an API method for creating a new fully configured SSL CTX
Tue Dec 29 19:00:15 2015  biilmann:made this proof of context:
Tue Dec 29 19:00:18 2015  biilmann:https://github.com/apache/trafficserver/compare/master...biilmann:ssl-ctx#diff-3837fe784d08b461e5f6de6124114eb1R1653
Tue Dec 29 19:00:43 2015  biilmann:that works - but would want to clean it up a bit before I would consider it ready to merge in
Tue Dec 29 20:01:06 2015  biilmann:Joined the channel
Tue Dec 29 20:17:51 2015  niq:Joined the channel
Tue Dec 29 20:35:29 2015  kichan:zwoop , what's our current proposed plan for the spring summit ?
Tue Dec 29 20:49:14 2015  PSUdaemon:i don't think there is an official one
Tue Dec 29 20:49:29 2015  PSUdaemon:the best idea i have heard is to do it along with ACNA
Tue Dec 29 20:49:43 2015  PSUdaemon:seemed like a lot of people could justify the trip more when attached to the conf
Tue Dec 29 21:30:52 2015  biilmann:PSUdaemon: was it you that were interested in lazy loading SNI certs via plugins as well?
Tue Dec 29 21:42:40 2015  kichan:yeah
Tue Dec 29 23:01:13 2015  biilmann:Joined the channel
Tue Dec 29 23:11:35 2015  PSUdaemon:biilmann: maybe it was jpeach? or ... reveller?
Tue Dec 29 23:21:40 2015  biilmann:ahh, true - was reveller :)

Comments