perfsonar development work

[Brian Tierney <>]

Hi all:

I am working on a Grid Troubleshooting project where for logging we
agreed on a syslog format where everything is 'name=value' pairs.
We felt that this was the best compromise of easy to parse and easy to 
read.

We also said that each log line should have a required 
'event=eventname', where eventname should be similar to a java class name.

I recommend that perfSONAR logs use this format as well.

For more information.

http://www.cedps.net/index.php/LoggingBestPractices

This format is the same as the EGEE "Middleware Security Audit Logging 
Guidelines": http://edms.cern.ch/document/793208

Cheers.


Luchesar V. ILIEV wrote:
> Hi guys,
>
> This mail is addressed to all pS service developers. As you know, last 
> week in Zagreb we discussed the issues of monitoring the deployed pS 
> services to ensure they are operating as intended, and really serving 
> the end-users' requests up to the users' satisfaction.
>
> As a next step in this process (having used so far ICMP, HTTP GET, and 
> perfSONAR EchoRequest/EchoResponse messages,) in order to achieve more 
> in-depth monitoring, which could, in turn, provide a more true-to-life 
> view on the functioning of the services, we've decided in Zagreb to 
> utilize the well-known and widely-used mechanism of sysloging.
>
> I've the task to prepare a proposal for a common format of the syslog 
> messages, or (depending on your feedback) at least some guidelines, 
> which would ensure having consistency amongst the different service's 
> messages' general structure.
>
> Therefore, I'd like to ask you to provide me either with a full list of 
> the possible messages that the service you're working on could 
> eventually write to the log, or provide me with information on the 
> structure of the (different types of these) messages.
>
> It could be helpful to have also some indication about the severity of 
> each message (from your point of view, of course): e.g., debug, 
> information, warning, error, critical failure, etc. As decided in 
> Zagreb, you have to synchronize this with the Service Desk -- if you 
> could do this beforehand, it would be great. If not, I would be OK with 
> your own (from service developer's point of view) classification.
>
> I'll appreciate if you could send me your feedback before the end of 
> next business week: that is, 25th of April inclusive.
>
> If there's something unclear in my e-mail and specifically about my 
> request, please do contact me.
>
> Many thanks in advance,
>
> Cheers,
> Luchesar