System and method for non-intrusive context correlation across cloud services

A method for providing a non-intrusive context correlation across a plurality of cloud services, comprising:

• providing a first cloud service executing on a computer including a microprocessor, wherein the first cloud service invokes a second cloud service;
• providing a cloud service context correlator at each of the first cloud service and the second cloud service, wherein each of a first cloud service context correlator and a second cloud service context correlator includes a container request filter operable to map between execution context identifiers and thread identifiers associated with thread contexts that execute requests;
• at the first cloud service:
• setting an execution context identifier to a current thread context, and
• passing the execution context identifier to a logger for injection into first log messages at the first cloud service;
• passing the execution context identifier from the first cloud service to the second cloud service in association with a request to be processed by the first cloud service and the second cloud service;
• at the second cloud service:
• injecting the execution context identifier into second log messages at the second cloud service;
• wherein the execution context identifier is used to correlate a transaction context across a plurality of cloud services including the first cloud service and the second cloud service, as indicated by the execution context identifier injected into the first loq messages and the second loq messages at those cloud services.

A non-transitory computer readable storage medium, including instructions stored thereon which when read and executed by one or more computers cause the one or more computers to perform the steps comprising:

• providing a first cloud service executing on a computer including a microprocessor, wherein the first cloud service invokes a second cloud service;
• providing a cloud service context correlator at each of the first cloud service and the second cloud service, wherein each of a first cloud service context correlator and a second cloud service context correlator includes a container request filter operable to map between execution context identifiers and thread identifiers associated with thread contexts that execute requests;
• at the first cloud service:
• setting an execution context identifier to a current thread context, and
• passing the execution context identifier to a logger for injection into first loq messages at the first cloud service;
• passing the execution context identifier from the first cloud service to the second cloud service in association with a request to be processed by the first cloud service and the second cloud service;
• at the second cloud service:
• injecting the execution context identifier into second log messages at the second cloud service;
• wherein the execution context identifier is used to correlate a transaction context across a plurality of cloud services including the first cloud service and the second cloud service, as indicated by the execution context identifier injected into the first loq messages and the second loq messages at those cloud services.