WSRFLogMessages
From CEDPS
Additional Log Messages for WSRF Services
The goal here is to try to include enough information in log messages to:
- correlate log messages involved in servicing a single request, and
- correlate log messages associated with the same resource (for example, messages associated with a request to create a GRAM job and a subsequent request to terminate that same job).
The guid is used to uniquely identify log messages associated with a request. For WSRF services, we propose adding a new resourceid identifier to uniquely identify a resource. Ideally, for each unique guid, there would be at least one log message linking that guid with a resourceid.
The purpose of the resourceid is to link log messages associated with a resource (including requests from different, unrelated clients that interact with the same resource), not to attempt to link log messages associated with the client side and server side of the same request.
Globus-Specific Recommendations
For Globus, our recommendations are that:
1. A new guid is assigned for each new request received by the container; this guid is then used for each log message associated with servicing that request, including:
- authentication
- authorization
- service-specific processing
- other locally-invoked services, e.g., if GRAM invokes an RFT service within the same container in the process of servicing a GRAM request, the RFT log messages should use the same GUID as the GRAM messages, not generate a new one.
2. Resource information is included in log messages as follows:
- When a new resource is created (e.g., by a factory service), a log message to that effect should be generated. That log message should include the standard mandatory attributes (timestamp, guid, etc.) and the resourceid and EPR of the newly-created resource.
- For each request, at least one log message should be generated that includes the guid of the request and the resourceid of the resource associated with that request.
