perfsonar development work

["Luchesar V. ILIEV" <>]

Luchesar V. ILIEV wrote:
> Domenico Vicinanza wrote:
> > the format "perfSONAR-<SERVICE_ID>" as first word of the log entry is 
> > an important requirement for us because that is the variable syslog-ng 
> > associates to the responsible of the log. So it could not be a date or 
> > simply the location.
>
> I'm afraid I can't understand that. Could you please elaborate about 
> that variable and it's role for syslog-ng. (I'm not questioning your 
> choice in any way, I'd just like to better understand what you're doing.)
>
> > The other fields can be organized as you were suggesting. Our 
> > perfSONAR logentries should start with
> >
> > perfSONAR-AS ...
> > perfSONAR-LS ...
> > ...
>
> I guess today is not my day... What do AS and LS mean?

Nina has been so kind to explain these to me, so consider this one 
answered. Indeed, I should have guessed them myself. :)))

Actually, I think I see the picture now...

> > Just as a remark, we preferred for the time being to not use the log4j 
> > but adding the prefix "perfSONAR-<SERVICE_NAME>" in the syslog-ng 
> > configuration, for example, perfSONAR AS logfile:
> >
> > source aslog{
> >        pipe("/dev/aslog" log_prefix("perfSONAR-AS: ") );
> > };
> >
> > In this way if perfSONAR services need to be updated or reinstalled we 
> > do not have to set the format preferences again.

...but, while if you do this locally, it's certainly okay, how would you 
implement this on the remote sites? Do you foresee specifically 
configured syslog-ng daemon on each one of them? Sorry, perhaps I'm 
getting it all wrong, but that's my impression from what I've understood.

Cheers,
Luchesar

Attachment: signature.asc
Description: OpenPGP digital signature