On 2014-07-14 at 15:35 -0700, David Lang wrote: > Having a well defined format is critical, but key=value ends up eating a lot > of space and is rather expensive to parse, so I'm not in agreement that it's > always the best way to format the logs.
It's a good default, being fast to set up consumption and analysis for. If performance and structure start to be an issue, then frankly text-format logs start to lose their appeal, but sure you can tune the format accordingly. Probably worth making sure that the program logs something at startup and that whatever it logs it sufficient to tell the formats apart. It's that whole "premature optimisation" thing, which applies to structuring log formats as much as for anything else, especially since non-standard formats do incur admin costs (time, etc) in setting up handling. So be sure your service justifies extra pain before doing something other than the easiest format to parse. -- My employer, Apcera Inc, is hiring sysadmin; primarily San Francisco: http://www.apcera.com/jobs/#operations-engineer (but all the mistakes in this email are made in my personal capacity) _______________________________________________ Discuss mailing list [email protected] https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss This list provided by the League of Professional System Administrators http://lopsa.org/
