Browse Prior Art Database

HIERARCHICAL TRACKING FOR CLOUD COMPUTING

IP.com Disclosure Number: IPCOM000222852D
Publication Date: 2012-Oct-25
Document File: 5 page(s) / 29K

Publishing Venue

The IP.com Prior Art Database

Related People

Yao Yuan: AUTHOR

Abstract

Hierarchical tracking techniques for a cloud computing environment are provided. The concept of a CallPath is introduced. The CallPath identifies the location of each function call in a call tree. Base on a UniqueID (which identifies a function call) and CallPath, each cloud service request can be identified, and the order between cloud service requests can be tracked.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 55% of the total text.

Page 01 of 5

HIERARCHICAL TRACKING FOR CLOUD COMPUTING

AUTHORS:

Yao Yuan

CISCO SYSTEMS, INC.

ABSTRACT

    Hierarchical tracking techniques for a cloud computing environment are provided. The concept of a CallPath is introduced. The CallPath identifies the location of each function call in a call tree. Base on a UniqueID (which identifies a function call) and CallPath, each cloud service request can be identified, and the order between cloud service requests can be tracked.

DETAILED DESCRIPTION

    Cloud computing requires a variety of functional modules to provide full functionality. These functional modules can run on different machines, deployed in multiple data centers around the world. In order for cloud computing systems to be stable and operate efficiently, it is necessary to track a customer's service request for the following information:


(1) The calling sequence between various modules.


(2) The performance of each module and its distribution.

    (3) When an outage occurs, how quickly is it navigated to the corresponding exception module.

    A commonly used method is a 'fixed tracking code'. A client generates a tracking code and adds it to the request packet. When the back-end modules need to call other modules, this tracking code is added to the request packet. A characteristic of the 'fixed tracking code' method is the calls between the various modules use the same tracking code. Figure 1 below shows an example of the fixed tracking code method, in which all calls use the same tracking code tc123.

Copyright 2012 Cisco Systems, Inc. 1


Page 02 of 5

Generate a tracking code Named tc123

A

tc123

tc123

B

C

D

tc123

tc123

tc123

tc123

tc123

E

F

G

H

I

tc123

J

Figure 1

    Techniques are presented herein for the composition and operating mechanism of a hierarchical tracking code. The tracking code consists of two parts: UniqueID, and CallPath.

    (1) UniqueID identifies a function call, for example, it can use a randomly generated UUID.

    (2) CallPath identifies the location of each call in the call tree. A function call is viewed as a node, and the sub function call as a sub node.

    CallPath consists of a set of CallSequences. A CallSequence is the number of sub nodes according to the time.

Copyright 2012 Cisco Systems, Inc. 2


Page 03 of 5

Figure 2 below is an example of a CallPath.

A

0

1

2

B

C

D

0_0

0_1

2_0

2_1

2_2

E

F

G

H

I

2_1_0

J

Figure 2

The operating mechanism is as follows.
(Step 1) Client generates an original tracking code, which contains the UniqueID. (Step 2) Client adds the original tracking co...