Nonstandard klog / glog severity levels

[srstrickland]

We have some applications which use klog or glog format with "nonstandard" log levels (generally common, but technically not part of either spec), namely "D" for debug and "T" for trace. In my parsing code, I can apply VRL workarounds, but I'm wondering what the appetite would be for the 2-line change (here and here) to support parsing these? I'm happy to submit a PR, but I realize it's a bit esoteric and perhaps I should just keep my VRL hack.

D0505 17:59:40.692994   28133 klog.go:70] hello from klog  # level = debug
T0505 17:59:40.692994   28133 klog.go:70] hello from klog  # level = trace

[jszwedko]

Thanks for raising this @srstrickland. I think we'd support that, I can see why they would be common. I would just note it in the code with comments that they are non-standard.