Re: Cloud Logging Format

Hi Juegen.
Some answers are in-line
--Gene

-----Original Message-----
From: Juergen Schoenwaelder [mailto:[email protected]]
Sent: Tuesday, April 03, 2012 11:57 PM
To: Gene Golovinsky
Cc: Romascanu, Dan (Dan); [email protected]; Benoit Claise;
[email protected]
Subject: Re: [OPS-AREA] Cloud Logging Format

On Tue, Apr 03, 2012 at 10:23:37AM -0700, Gene Golovinsky wrote:
> Dan, thanks a lot!
> Any more comments/discussions on the draft itself will be highly
> helpful as well.

Let me repeat the question I asked at the meeting. From reading the draft,
it was not clear how the new SDEs are added to syslog messages.
Is it reasonable to assume that the originator of a syslog message has the
relevant information?
[Gene Golovinsky] Yes, the originator of the message, the actual logging
entity should be aware of the information populated into the Syslog
message

If not, what does it take to distribute the necessary information to the
originators? Or is the idea that proxies add SDEs while forwarding syslog
messages?
[Gene Golovinsky] Yes again. As a request for service (API call)  travels
through processing nodes those nodes add SDs to the message. Each node is
aware of the context and can add appropriate SD.

I like to see how this can reasonably implemented and deployed.
[Gene Golovinsky] I am not sure I understand this. It has been actually
implemented and deployed by several vendors in their "cloud"
implementations.

I probably also have question what precisely the semantics of the prosed
SDEs are but that perhaps becomes clear once I understand where the
knowledge for which service/customer a log message is being created is
coming from and which component is expected to do the tagging.

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>