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. On Mon, Dec 19, 2016 at 9:58 AM, James Peach <[email protected]> wrote: > > > On Dec 19, 2016, at 9:43 AM, Zhitao Li <[email protected]> wrote: > > > > Hi, > > > > I'm looking at how to better utilize ElasticSearch to perform log > analysis for logs from Mesos. It seems like ElasticSearch would generally > work better for structured logging, but Mesos still uses glog thus all logs > produced are old-school unstructured lines. > > > > I wonder whether anyone has brought the conversation of making Mesos > logs easier to process, or if anyone has experience to share. > > Are you trying to stitch together sequences of events? I that case, would > direct event logging be more useful? > > J -- Cheers, Zhitao Li
