Abstract: A framework and method are disclosed for providing/consuming data items. A memory structure is created within an address space allocated to a provider application. The memory structure stores performance counter data generated by the provider application. The counter provider application registers a counter provider and an associated performance counter memory structure via a set of application program interface methods. Thereafter, a counter provider consumer application, via additional application program interface methods, determines the identity of the performance counter provider, sets up a buffer to receive the counter data of the counter provider, and requests extraction of the counter data stored within the performance counter memory structure. The transfer of data from the provider application to the consumer application occurs through the system API.

Abstract: A framework and method are disclosed for carrying out request completion tracing across request identification boundaries. When a request traverses an identification boundary, an event identifies the old and new request identifications and stores this linking information in a trace event record. Thereafter, a consumer of records maintains track of request completion by incorporating the linking information to switch identifications used to track completion of the request across request identification boundaries encountered by the system while responding to the received request. A request trace event record consumer architecture with enhanced tracking capabilities based upon a specified state machine provides greater power when interpreting the trace records associated with completion of requests by a server system.