Re: [vdsm] flowID schema

2012-02-20 Thread Keith Robertson
On 02/19/2012 05:32 AM, Ayal Baron wrote: FlowID does absolutely nothing towards that end. What is required for that (and should indeed be done) is work on improving the existing logs: 1. reduce verbosity 2. make sure that required points in the flow are logged 3. improve log messages Don't

Re: [vdsm] flowID schema

2012-02-16 Thread Saggi Mizrahi
...@redhat.com Sent: Thursday, February 16, 2012 11:07:34 AM Subject: Re: [vdsm] flowID schema - Original Message - From: Saggi Mizrahi smizr...@redhat.com To: Simon Grinberg si...@redhat.com Cc: vdsm-devel@lists.fedorahosted.org, Dan Yasny dya...@redhat.com, Ayal Baron aba

Re: [vdsm] flowID schema

2012-02-15 Thread Simon Grinberg
Grinberg si...@redhat.com, vdsm-devel@lists.fedorahosted.org Sent: Friday, February 10, 2012 4:01:01 PM Subject: Re: [vdsm] flowID schema - Original Message - From: Ayal Baron aba...@redhat.com To: Dan Yasny dya...@redhat.com Cc: Simon Grinberg si...@redhat.com, vdsm-devel

Re: [vdsm] flowID schema

2012-02-14 Thread Dan Kenigsberg
On Mon, Feb 13, 2012 at 12:06:46PM -0500, Ayal Baron wrote: - Original Message - 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

Re: [vdsm] flowID schema

2012-02-13 Thread Ayal Baron
- Original Message - On 02/12/2012 02:50 AM, Dan Kenigsberg wrote: On Thu, Feb 09, 2012 at 03:23:19PM -0500, Ayal Baron wrote: - Original Message - -1 I agree that for messaging environment having a Message ID is a must because you sometimes don't have a

Re: [vdsm] flowID schema

2012-02-13 Thread Dan Yasny
- 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

Re: [vdsm] flowID schema

2012-02-13 Thread Itamar Heim
On 02/13/2012 12:52 AM, Ayal Baron wrote: ... if the FlowID isn't logged for logs which are part of the action, it will be easy to detect the entry point. but still wouldn't make it easy to grep all related logs to a flow If the flow id is present in all lines it would make the log a lot

Re: [vdsm] flowID schema

2012-02-13 Thread Ayal Baron
- Original Message - 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

Re: [vdsm] flowID schema

2012-02-12 Thread Itamar Heim
On 02/12/2012 09:50 AM, Dan Kenigsberg wrote: On Thu, Feb 09, 2012 at 03:23:19PM -0500, Ayal Baron wrote: - Original Message - -1 I agree that for messaging environment having a Message ID is a must because you sometimes don't have a particular target so when you get a response you

Re: [vdsm] flowID schema

2012-02-12 Thread Ayal Baron
- Original Message - On 02/12/2012 09:50 AM, Dan Kenigsberg wrote: On Thu, Feb 09, 2012 at 03:23:19PM -0500, Ayal Baron wrote: - Original Message - -1 I agree that for messaging environment having a Message ID is a must because you sometimes don't have a

Re: [vdsm] flowID schema

2012-02-11 Thread Dan Kenigsberg
On Thu, Feb 09, 2012 at 03:23:19PM -0500, Ayal Baron wrote: - Original Message - -1 I agree that for messaging environment having a Message ID is a must because you sometimes don't have a particular target so when you get a response you need to know what this node is

Re: [vdsm] flowID schema

2012-02-09 Thread Lee Yarwood
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/09/2012 05:18 PM, Andrew Cathrow wrote: The question is, what problem is this really trying to solve and is there a simpler and less obtrusive solution to that problem? correlating logs between ovirt engine and potentially multiple vdsm

Re: [vdsm] flowID schema

2012-02-09 Thread Saggi Mizrahi
. I see it doing more harm the good by reinforcing bad debugging practices. - Original Message - From: Keith Robertson krobe...@redhat.com To: VDSM Project Development vdsm-devel@lists.fedorahosted.org Sent: Thursday, February 9, 2012 1:34:43 PM Subject: Re: [vdsm] flowID schema

Re: [vdsm] flowID schema

2012-02-09 Thread Ayal Baron
: Thursday, February 9, 2012 1:34:43 PM Subject: Re: [vdsm] flowID schema On 02/09/2012 12:18 PM, Andrew Cathrow wrote: - Original Message - From: Ayal Baronaba...@redhat.com To: Dan Kenigsbergdan...@redhat.com Cc: VDSM Project Developmentvdsm-devel

Re: [vdsm] flowID schema

2012-02-09 Thread Dan Yasny
From: Saggi Mizrahi smizr...@redhat.com To: Keith Robertson krobe...@redhat.com Cc: VDSM Project Development vdsm-devel@lists.fedorahosted.org Sent: Thursday, February 9, 2012 2:24:44 PM Subject: Re: [vdsm] flowID schema -1 I agree that for messaging environment having a Message ID

Re: [vdsm] flowID schema

2012-02-09 Thread Ayal Baron
- Original Message - From: Saggi Mizrahi smizr...@redhat.com To: Keith Robertson krobe...@redhat.com Cc: VDSM Project Development vdsm-devel@lists.fedorahosted.org Sent: Thursday, February 9, 2012 2:24:44 PM Subject: Re: [vdsm] flowID schema -1 I agree

Re: [vdsm] flowID schema

2012-02-06 Thread Dan Kenigsberg
On Thu, Feb 02, 2012 at 12:00:44AM -0500, Douglas Landgraf wrote: Hello, flowID is schema that we will be including in vdsm API to oVirt Engine people share the ID of engine transaction to vdsm. With this in hands, we will add the ID of transactions to our log. I would like to know

Re: [vdsm] flowID schema

2012-02-02 Thread Saggi Mizrahi
Sent: Thursday, February 2, 2012 12:00:44 AM Subject: [vdsm] flowID schema Hello, flowID is schema that we will be including in vdsm API to oVirt Engine people share the ID of engine transaction to vdsm. With this in hands, we will add the ID of transactions to our log. I would

[vdsm] flowID schema

2012-02-01 Thread Douglas Landgraf
Hello, flowID is schema that we will be including in vdsm API to oVirt Engine people share the ID of engine transaction to vdsm. With this in hands, we will add the ID of transactions to our log. I would like to know your opinion how we could do that without break our API, like include