----- Original Message -----
> From: "Itamar Heim" <ih...@redhat.com>
> To: "Ayal Baron" <aba...@redhat.com>
> Cc: "VDSM Project Development" <vdsm-devel@lists.fedorahosted.org>
> Sent: Monday, 13 February, 2012 6:55:41 PM
> Subject: Re: [vdsm] flowID schema
> 
> On 02/13/2012 02:28 PM, Ayal Baron wrote:
> >
> ...
> >>> is that it (ab)uses an http header for carrying FlowID,
> >> Yes, it certainly does appear to overload it.  I would be nice to
> >> have
> >> something formal given to it by engine, but I can appreciate the
> >> difficulty implementing such a scheme.
> >
> > Technically I disagree, this is a cross cutting concern which has
> > nothing to do with any specific call hence it should be passed as
> > a header, that is actually rather elegant.
> >
> > To the specific matter at hand though. what would really be nice is
> > solving the real problem properly, and not contaminating the API
> > and the log with things which have marginal benefit if at all.
> 
> going back to the 'grep' issue.
> vdsm logs are verbose. they are multi-threaded as well.
> I think this should be more than just about finding the entry point
> of
> the flow, then identifying for this specific log format how to trace
> it,
> which would require writing a log analyzer with plugins for each
> component.
> having all lines which are relevant to a flow with a flowid logged in
> them would make it much easier to get all (or most) of relevant parts
> of the flow 

+1

> (most, since something orthogonal to the flow may have
> happened
> affecting it, like loss of network)
> _______________________________________________
> vdsm-devel mailing list
> vdsm-devel@lists.fedorahosted.org
> https://fedorahosted.org/mailman/listinfo/vdsm-devel
> 

-- 



Regards, 

Dan Yasny 
Red Hat Israel 
+972 9769 2280
_______________________________________________
vdsm-devel mailing list
vdsm-devel@lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/vdsm-devel

Reply via email to