Skip to Content.
Sympa Menu

perfsonar-dev - Re: perfSONAR error logging

Subject: perfsonar development work

List archive

Re: perfSONAR error logging


Chronological Thread 
  • From: Domenico Vicinanza <>
  • To: Nicolas Simar <>
  • Cc: Jochen Reinwand <>, Luchesar Iliev <>, ,
  • Subject: Re: perfSONAR error logging
  • Date: Fri, 06 Jun 2008 09:52:10 +0100
  • Organization: DANTE Ltd

Hi Nicolas,

exactly, in particular, if it is possible:

[perfSONAR-SERVICE_ID]
[@LOCATION]
SEVERITY% DESCRIPTION

It is important for us to have the serviceID in the first word of the log: it is the way syslog-ng is able to detect the program which caused the log and allows the proper classification in our database. For example:

perfSONAR-RRDMA srv3.ams.nl.geant2.net WARNING <description>

It is better, to ease the parsing process, not to have dots (.) as separator between location and severity, since the host names contain dots too.

Many thanks in advance,
Domenico



Nicolas Simar wrote:


Domenico Vicinanza wrote:
Hi Nicolas,

no, unfortunately it is not there. The log entries (for a request successfully processed, for example) are:
<date> <time>,<number> INFO - RequestHandler: Service received a request
<date> <time>,<number> INFO - RequestHandler: Service sent a successful response

So should we update the syslog message format :
perfSONAR
%SERVICE_ID[@LOCATION].SEVERITY%
DESCRIPTION

I am not familiar with the syslog format (%, location of text), so feel free to update it.

Nicolas

as:
2008-06-04 12:40:36,278 INFO - RequestHandler: Service received a request
2008-06-04 12:40:36,294 INFO - RequestHandler: Service sent a successful response

no matter which is the service producing them. We overtook the problem in our syslog server manually adding a prefix to the log corresponding to the name of the service, so that we can correctly process and store them.

Cheers,
Domenico


Nicolas Simar wrote:
Hi Domenico,

as you have to parse the syslog messages, shouldn't you have also have a "perfsonar" tag in addition to the service type?

(This was proposed in Zagreb, but I don't see it in the syslog format proposal).

Cheers,
Nicolas

Domenico Vicinanza wrote:
Hello,

I am writing you on behalf of the GEANT2 Service Desk. We are installing and configuring a monitoring server based on Nagios (equipped with customized plugin to check perfsonar services) and on syslog parsing (we are running syslog-ng receving, among the others, perfsonar logs).

We have a remark and a request. The remark regards the fact that there is no perfsonar service name in the log messages, when the service is dealing with a web-service request. As an example, having a look at the LS, AS or RRD-MA logs those messages are all looking the same:
2008-06-04 12:40:36,278 INFO - RequestHandler: Service received a request
2008-06-04 12:40:36,294 INFO - RequestHandler: Service sent a successful response

with no specific tag. This would be fixed in future (as far as I understood) according to the http://wiki.perfsonar.net/jra1-wiki/index.php/Service_Log_List. Could you just confirm that it is correct?

The request is related to log content. I tried this morning to simulate an error (I used a wrong schema in the request: in the eventType field), basically a wrongly formatted request to a service (pS LS), using perfsonar UI.
The error message the web service returned was perfectly reflecting the problem occurred:

<nmwg:eventType>error.ls.eventtype_not_supported</nmwg:eventType>

On the other hand the log files reported:

INFO - RequestHandler: Service received a request
INFO - RequestHandler: Service sent a successful response

Which is not true. It is true that, from a functional point of view the service was replying correctly to the response, but it is not true that the response was successful.
Our proposal is that the log should contain the error reported, something like:

ERROR - RequestHandler: Service sent an error response - Error message: error.ls.eventtype_not_supported

This would help us a lot in supporting users, debugging problems and taking the proper actions when a problem is detected.

Many thanks in advance,
Domenico







--
______________________________________________________________________

Domenico Vicinanza
Services Support Engineer

DANTE - www.dante.net

Tel: +44 (0)1223 371 300
Fax: +44 (0)1223 371 371
Email:



City House, 126-130 Hills Road
Cambridge CB2 1PQ
UK
_____________________________________________________________________




Archive powered by MHonArc 2.6.16.

Top of Page