System and method for tracking service requests

Patent metadata

Field	Value
Publication number	US-11356337-B2
Application number	US-202016938997-A
Country	US
Kind code	B2
Filing date	Jul 26, 2020
Priority date	Mar 24, 2009
Publication date	Jun 7, 2022
Grant date	Jun 7, 2022

Abstract

Various embodiments of a system and method for tracking service requests are described. Embodiments may include call tree generation logic configured to receive multiple request identifiers associated with a respective one of multiple service requests. Each given request identifier may include an origin identifier, a depth value, and a request stack comprising one or more interaction identifiers. The call tree generation logic may also be configured to, based on multiple request identifiers that each include an origin identifier associated with a particular root request, generating a data structure that specifies a hierarchy of services called to fulfill that particular root request. Based on one or more of the interaction identifiers and one or more of the depth values, the generated data structure may specify for each given service of the hierarchy: a parent service that called the given service, and one or more child services called by the given service.

First claim

What is claimed is:

1. A computer-implemented method, comprising:
performing, by one or more computers that implements a service in a service-oriented system:
receiving an inbound service request from a first service of the service-oriented system and an associated first request identifier, wherein the first request identifier indicates a sequence of multiple service requests issued by one service to another in the service-oriented system to fulfill a root request, the sequence ending in the inbound service request;
processing the inbound service request, including:
determining to issue an outbound service request to a second service of the service-oriented system;
generating a second request identifier for the outbound service request, wherein the second request identifier indicates a new sequence of service requests that adds the output service request to the sequence indicated by the first request identifier; and
sending the second request identifier to the second service along with the outbound service request.

2. The computer-implemented method of claim 1 , wherein:
the first request identifier includes an origin identifier associated with the root request; and
the generating of the second request identifier includes the origin identifier in the second request identifier.

3. The computer-implemented method of claim 1 , wherein:
the first request identifier includes a stack of unique interaction identifiers associated with respective service calls in the sequence; and
the generating of the second request identifier includes:
generating a new unique identifier for the outbound service request;
adding the new unique identifier to the stack to generate a new stack; and
including the new stack in the second request identifier.

4. The computer-implemented method of claim 3 , wherein the generating of the new stack includes removing an oldest interaction identifier from the stack.

5. The computer-implemented method of claim 1 , wherein:
the first request identifier includes a depth value indicating a distance between the inbound service request and the root request; and
the generating of the second request identifier includes:
incrementing the depth value to generate a new depth value; and
including the new depth value in the second request identifier.

6. The computer-implemented method of claim 1 , wherein the sending of the second request identifier to the second service along with the outbound service request includes:
embedding the second request identifier as metadata in the outbound service request.

7. The computer-implemented method of claim 1 , wherein the sending of the second request identifier to the second service along with the outbound service request includes:
embedding a pointer to the memory location of the second request identifier in the outbound service request.

8. The computer-implemented method of claim 1 , further comprising performing, by the service:
storing the first request identifier as a log record in an inbound request log associated with the service.

9. The computer-implemented method of claim 8 , further comprising performing, by the service:
storing the second request identifier as another log record in an outbound request log associated with the service.

10. The computer-implemented method of claim 8 , further comprising performing, by the service:
reporting contents of the inbound request log to a log repository.

11. A system, comprising:
one or more computers that implements a service in a service-oriented system, the service configured to:
receive an inbound service request from a first service of the service-oriented system and an associated first request identifier, wherein the first request identifier indicates a sequence of multiple service requests issued by one service to another in the service-oriented system to fulfill a root request, the sequence ending in the inbound service request;
process the inbound service request to:
determine to issue an outbound service request to a second service of the service-oriented system;
generate a second request identifier for the outbound service request, wherein the second request identifier indicates a new sequence of service requests that adds the output service request to the sequence indicated by the first request identifier; and
send the second request identifier to the second service along with the outbound service request.

12. The system of claim 11 , wherein:
the first request identifier includes an origin identifier associated with the root request; and
to generate the second request identifier, the service is configured to include the origin identifier in the second request identifier.

13. The system of claim 11 , wherein:
the first request identifier includes a stack of unique interaction identifiers associated with respective service calls in the sequence; and
to generate the second request identifier, the service is configured to:
generate a new unique identifier for the outbound service request;
add the new unique identifier to the stack to generate a new stack; and
include the new stack in the second request identifier.

14. The system of claim 13 , wherein to generate the new stack, the service is configured to remove an oldest interaction identifier from the stack.

15. The system of claim 11 , wherein:
the first request identifier includes a depth value indicating a distance between the inbound service request and the root request; and
to generate the second request identifier, the service is configured to:
increment the depth value to generate a new depth value; and
include the new depth value in the second request identifier.

16. The computer-implemented method of claim 11 , wherein the service is configured to store the first request identifier as a log record in a request log associated with the service.

17. The system of claim 16 , wherein to store the log record, the service is configured to:
include in the log record metadata associated with the inbound service request including one or more of a timestamp of the inbound service request, a quantum of work performed by the inbound service request, and one or more errors encountered during processing of the inbound service request.

18. The system of claim 16 , wherein the service is configured to report contents of the request log to a log repository.

19. The system of claim 18 , wherein the service implements a log reporting agent, and the log reporting agent is configured to periodically provide information about the request log to the log repository.

20. One or more computer readable non-transitory media storing program instructions that when executed on or across one or more processors implement a service of a service-oriented system and cause the service to:
receive an inbound service request from a first service of the service-oriented system and an associated first request identifier, wherein the first request identifier indicates a sequence of multiple service requests issued by one service to another in the service-oriented system to fulfill a root request, the sequence ending in the inbound service request;
process the inbound service request to:
determine to issue an outbound service request to a second service of the service-oriented system;
generate a second request identifier for the outbound service request, wherein the second request identifier indicates a new sequence of service requests that adds the output service request to the sequence indicated by the first request ide

Assignees

• Amazon Tech Inc

Inventors

• Beal Jeff B
• Robbins Alan Stuart
• Goetz Jeromey R
• Porter Brandon William
• Mcalister Grant Alexander Macdonald
• Ellsworth Joseph L

Classifications

• H04L65/00

  Network arrangements, protocols or services for supporting real-time applications in data packet communication (real-time or near real-time messaging, e.g. instant messaging [IM] H04L51/04; selective video distribution H04N21/00) · CPC title

• H04L67/62

  Establishing a time schedule for servicing the requests · CPC title

• H04L69/28 Primary

  Timers or timing mechanisms used in protocols · CPC title

• H04L43/106

  using time related information in packets, e.g. by adding timestamps · CPC title

• H04L41/50 Primary

  Network service management, e.g. ensuring proper service fulfilment according to agreements · CPC title