Re: Structured logging for Mesos (or c++ glog)

Hi Otis, Thanks for the good summary. The conversation is mostly about 1) in this thread, because right now Mesos logs are not really structured, or at least most of it. On Tue, Dec 20, 2016 at 6:57 AM, Otis Gospodnetić < otis.gospodne...@gmail.com> wrote: > Hi Zhitao, > > When people talk

Re: Structured logging for Mesos (or c++ glog)

Hi Zhitao, When people talk about structure and logging it typically means two things: 1) make the log format a known/standard format where all its elements are known, and thus it's easy to parse them; a log event can still be a single line, but it can also be multi-line or JSON or some other

Re: Structured logging for Mesos (or c++ glog)

Why not `logstash`? I think it's the target case of `logstash`. On Tue, Dec 20, 2016 at 7:35 AM Zhitao Li wrote: > Great. > > I also found this old thread >

Re: Structured logging for Mesos (or c++ glog)

Great. I also found this old thread http://search-hadoop.com/m/Mesos/0Vlr6meKs116T2k1?subj=Mapped+diagnostics+context+Adding+internal+Mesos+IDs+as+context+to+the+logs on dev list, which seems no consensus has been made. Maybe we can talk about this in the next community sync? On Mon, Dec 19,

Re: Structured logging for Mesos (or c++ glog)

> On Dec 19, 2016, at 2:54 PM, Zhitao Li wrote: > > Hi James, > > Stitching events together is only one possible use cases, and I'm not exactly > sure what you meant by directly event logging. > > Taking the hierarchical allocator for example. In a multi-framework

Re: Structured logging for Mesos (or c++ glog)

Charles, Thanks for sharing the pattern. If my reading is right, this will extract the entire message line as one string. What I'm looking for is: on top of extracting the entire message line, also break it into structured fields automatically. On Mon, Dec 19, 2016 at 1:59 PM, Charles Allen <