Why not `logstash`? I think it's the target case of `logstash`. On Tue, Dec 20, 2016 at 7:35 AM Zhitao Li <[email protected]> wrote:
> 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, 2016 at 3:25 PM, James Peach <[email protected]> wrote: > > > > On Dec 19, 2016, at 2:54 PM, Zhitao Li <[email protected]> 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 > cluster, sometimes I want to comb through various loggings and present a > trace on how allocation has affected a particular framework (by its > framework id) and/or w.r.t an agent (by its agent id). > > > > Being able to systematically extract structured field values like > framework_id or agent_id, regardless of the actually logging pattern, will > be tremendously automatically from all lo valuable in such use cases. > > I think we are talking about similar things. Many servers do both > free-form error logging and structured event logging. I'm thinking of event > logging formats are customizable by the operator and allow the > interpolation of context-specific data item (eg. HTTP access logs from many > different server implementations). > > J > > > > > -- > Cheers, > > Zhitao Li > -- Regards, ---- Da (Klaus), Ma (马达), PMP® | Software Architect IBM Platform Development & Support, STG, IBM GCG +86-10-8245 4084 | [email protected] | http://k82.me
