A service oriented architecture (SOA) provides on-demand service call debugging and call stack tracing. The service call (e.g., an api) includes a new field and optional signature value. The field is a ‘debug-requested’ field, and the optional field is a unique call-id signature. The service provider can enable debugging in accordance with the debug-requested field for this service call, and tag all debugged data with the unique call-id. If it is necessary to call other services to fulfill the request, then the service can pass the ‘debug-requested’ field and the ‘unique id’ in the call to that service. Using this mechanism, detailed debugging can be supported across an entire stack for only those requests that need it and the performance/latency impact of having debugging enabled only applies to the subset of calls which need debugging.
|
1. A method of dynamically controlling a debugging mode in a service provider, the method comprising:
receiving a request for a service to be performed by the service provider;
detecting, within the request, a debug-requested parameter controlling a debugging mode to be used while processing the request;
while processing the request, passing the debugging mode between services of the service provider so as to establish a consistent debugging behavior across services; and
logging data by services that receive the debugging mode, the logging data being in accordance with the debugging mode.
17. A system for dynamically controlling a debugging mode in a compute service provider, comprising:
a plurality of host server computers for running services in the compute service provider;
an endpoint server computer responsive to receiving an api request including a debug-requested parameter that controls a debug mode to be used while processing the api request, the endpoint server computer for generating an identifier to be passed to a set of the plurality of host server computers running the services used to respond to the api request, so as to establish a consistent debugging behavior across the set of the plurality of host server computers; and
a log database coupled to the plurality of host server computers, for storing log data in association with the identifier.
7. A computer-readable storage including instructions thereon for executing a method of dynamically controlling debugging in a service provider, the method comprising:
receiving a request for a service to be performed by the service provider;
in response to the request, reading a debug-requested parameter associated with the request; and
in accordance with the debug-requested parameter, controlling a debugging mode used by the service provider while processing the request;
wherein the service provider includes a plurality of services used for processing the request, and wherein the controlling of the debugging mode includes passing a debugging mode between the plurality of services of the service provider used to process the request so as to establish a consistent debug behavior across the plurality of services.
2. The method of
3. The method of
4. The method of
5. The method of
6. The method of
8. The computer-readable storage of
9. The computer-readable storage of
10. The computer-readable storage of
11. The computer-readable storage of
12. The computer-readable storage of
13. The computer-readable storage of
14. The computer-readable storage of
15. The computer-readable storage of
16. The computer-readable storage of
18. The system of
19. The system of
|
Cloud computing is the use of computing resources (hardware and software) which are available in a remote location and accessible over a network, such as the Internet. Users are able to buy these computing resources (including storage and computing power) as a utility on demand. Cloud computing entrusts remote services with a user's data, software and computation. Use of virtual computing resources can provide a number of advantages including cost advantages and/or ability to adapt rapidly to changing computing resource needs.
Cloud computing can be formed by a plurality of services. The details of how services operate is often hidden from external customers that interface with the services through Application Program Interfaces (APIs). Trouble shooting errors can be problematic when multiple services are involved in generating a response to an API call. For example, it can be difficult to determine which service caused an error when hundreds of services are involved in the response.
As a result, many of the services activate full-debug capability on an ongoing basis. Unfortunately, this slows each service, which can have a cumulative effect when many services are used in generating a single response to an API request.
A service-oriented architecture (SOA) provides on-demand service call debugging and call-stack tracing. The service call (e.g., an API) includes a new field and optional signature value. The field is a ‘debug-requested’ field, and the optional field is a unique call-id signature. The debug-requested field and optional signature value can be API independent meaning that it can be used with any API to assist with modifying a debug mode in the service provider as it processing the API. Upon receipt of the service call, the service provider checks to see if there is a unique call-id signature along with the ‘debug-requested’ field. If there is no unique call-id, then one can be dynamically generated. The service provider can enable debugging in accordance with the debug-requested field for this service call, and tag all debugged data with the unique call-id. If it is necessary to call other services to fulfill the request, then the service can pass the ‘debug-requested’ field and the ‘unique id’ in the call to the other services. If every service in the call stack supports this mechanism, then detailed debugging can be supported across the entire stack for just those requests that need it and the performance/latency impact of having debugging enabled only applies to the subset of calls which need debugging. One advantage of accepting the ‘debug-requested’ flag at any entry point into the call tree is that it allows services to enable debugging for a single service call only. Other service calls that do not need debugging can leave debugging switched off. Alternatively, the debug-requested field can provide a level of debugging, such as errors only, a stack trace, or a complete log. Thus, the debug-requested field allows the caller to dynamically control a debug mode within the service provider.
The services used in cloud computing are typically Web services. A web service is a software function provided at a network address over the web or the cloud. Clients initiate web service requests to servers and servers process the requests and return appropriate responses. The client web service requests are typically initiated using, for example, an API request. For purposes of simplicity, web service requests are generally described below as API requests, but it is understood that other web service requests can be made. An API request is a programmatic interface to a defined request-response message system, typically expressed in JSON or XML, which is exposed via the web—most commonly by means of an HTTP-based web server. Thus, in certain implementations, an API can be defined as a set of Hypertext Transfer Protocol (HTTP) request messages, along with a definition of the structure of response messages, which can be in an Extensible Markup Language (XML) or JavaScript Object Notation (JSON) format. The API can specify a set of functions or routines that perform an action, which includes accomplishing a specific task or allowing interaction with a software component. When a web service receives the API request from a client device, the web service can generate a response to the request and send the response to the endpoint identified in the request.
After the API request has been completed, an API response 150 can be returned to the original requester. If the service endpoint 110 generated the identifier 140, then the API response can include the identifier so that future queries into log data can be made using the identifier. Alternatively, the API response 150 can be returned asynchronously. For example, a response can be returned indicating the request 120 is being processed. The identifier can be included with the asynchronous response. A follow-up second response can be returned when the request is completed or the requestor may need to send a subsequent request for status.
Each of the services 200 can include a logging component 250. The logging components 250 can be responsive to the debugging mode 230 to log data and metadata associated with processing the API request. For example, the metadata can include the other services called, time stamp information, start/stop times, while the log data can include arguments, return values, etc. The log data and metadata can be stored using the identifier as a key so that each logging component 250 stores its data using the same identifier, which is associated with the original API request. Thus, a uniform logging system is used across disparate services within the service provider.
The particular illustrated compute service provider 400 includes a plurality of server computers 402A-402D. While only four server computers are shown, any number can be used, and large centers can include thousands of server computers. The server computers 402A-402D can provide computing resources for executing software instances 406A-406D. In one embodiment, the instances 406A-406D are virtual machines. As known in the art, a virtual machine is an instance of a software implementation of a machine (i.e. a computer) that executes applications like a physical machine. In the example of virtual machine, each of the servers 402A-402D can be configured to execute a hypervisor 408 or another type of program configured to enable the execution of multiple instances 406 on a single server. Additionally, each of the instances 406 can be configured to execute one or more applications.
It should be appreciated that although the embodiments disclosed herein are described primarily in the context of virtual machines, other types of instances can be utilized with the concepts and technologies disclosed herein. For instance, the technologies disclosed herein can be utilized with storage resources, data communications resources, and with other types of computing resources. The embodiments disclosed herein might also execute all or a portion of an application directly on a computer system without utilizing virtual machine instances.
One or more server computers 404 can be reserved for executing software components for managing the operation of the server computers 402 and the instances 406. For example, the server computer 404 can execute a management component 410. A customer can access the management component 410 to configure various aspects of the operation of the instances 406 purchased by the customer. For example, the customer can purchase, rent or lease instances and make changes to the configuration of the instances. The customer can also specify settings regarding how the purchased instances are to be scaled in response to demand. The management component can further include a policy document to implement customer policies. The policy document can include a level of debugging to be used when the debug-requested parameter is activated. An auto scaling component 412 can scale the instances 406 based upon rules defined by the customer. In one embodiment, the auto scaling component 412 allows a customer to specify scale-up rules for use in determining when new instances should be instantiated and scale-down rules for use in determining when existing instances should be terminated. The auto scaling component 412 can consist of a number of subcomponents executing on different server computers 402 or other computing devices. The auto scaling component 412 can monitor available computing resources over an internal management network and modify resources available based on need.
A deployment component 414 can be used to assist customers in the deployment of new instances 406 of computing resources. The deployment component can have access to account information associated with the instances, such as who is the owner of the account, credit card information, country of the owner, etc. The deployment component 414 can receive a configuration from a customer that includes data describing how new instances 406 should be configured. For example, the configuration can specify one or more applications to be installed in new instances 406, provide scripts and/or other types of code to be executed for configuring new instances 406, provide cache logic specifying how an application cache should be prepared, and other types of information. The deployment component 414 can utilize the customer-provided configuration and cache logic to configure, prime, and launch new instances 406. The configuration, cache logic, and other information may be specified by a customer using the management component 410 or by providing this information directly to the deployment component 414. The instance manager can be considered part of the deployment component.
Customer account information 415 can include any desired information associated with a customer of the multi-tenant environment. For example, the customer account information can include a unique identifier for a customer, a customer address, billing information, licensing information, customization parameters for launching instances, scheduling information, auto-scaling parameters, previous IP addresses used to access the account, etc.
A network 430 can be utilized to interconnect the server computers 402A-402D and the server computer 404. The network 430 can be a local area network (LAN) and can be connected to a Wide Area Network (WAN) 440 so that end users can access the compute service provider 400. It should be appreciated that the network topology illustrated in
A service 450 can receive an API request and generate an identifier in response to a debug-requested parameter within the API request. Thus, if an identifier is not received with the request, the service 450 can generate an identifier, which can be used as a key for storing log data accumulated through processing the API request. The service 450 can call other services in order to process the request. Once the response is generated, the service 450 can return the response to the caller together with the generated identifier. In this way, the debug-requested parameter can be transformed into an identifier used in storing log data.
Other general management services that may or may not be included in the compute service provider 400 include an admission control 514, e.g., one or more computers operating together as an admission control web service. The admission control 514 can authenticate, validate and unpack the API requests for service or storage of data within the compute service provider 400. An instance manager 520 controls launching and termination of instances in the network. When an instruction is received (such as through an API request) to launch an instance, the instance manager pulls resources from a capacity pool and launches the instance on a decided upon host server computer. Similar to the instance manager are the storage manager 522 and the network resource manager 524. The storage manager 522 relates to initiation and termination of storage volumes, while the network resource manager 524 relates to initiation and termination of routers, switches, subnets, etc.
The endpoint 512 can be coupled to a service 530, which can call other services 532, 534, etc. Any number N (where N is any integer) of services can be called. Assuming that a debug-requested parameter is activated in the API, the services 530, 532, 534 store their respective log data in a log data database 540. Each log service can use the same identifier in order to store the data. An example entry is shown as including other services called, time stamps associated with the calls, start and stop times, arguments and return values, and log data generally. As the log data database 540 is a single repository including the identifier, it can be easy searched for all log data related to the same API call. For example, each API request can have its own unique identifier so that all log data associated with the API request can be retrieved.
Each host 640 has underlying hardware 650 including one or more CPUs 652, memory 654, disk I/O 656, network I/O 658, etc. Running a layer above the hardware 650 is an operating system 670. The service layer 680 can be an application including a log component 682 used for logging data associated with processing an API request. For example, the log component 682 can obtain access to the hardware 650 through the operating system 670 to record data such as CPU cycles, memory use of memory 654, Disk I/O use from Disk I/O hardware 656 or network I/O use from network I/O hardware 658. The log component 682 can access the log data database 540 using the structure of
In process block 810, a request for a service to be performed can be received. As previously described, the request can be an API request. Additionally, the request can be from a customer of the service provider or from a service internal to the service provider. In process block 820, a debug-requested parameter associated with the request can be read. The debug-requested parameter can be read from the request itself or from a policy document, wherein the policy document is a document stored by the service provider and associated with a customer of the request. In any event, the debug-requested parameter can be used to control a debugging mode used in processing the request. In addition or alternatively, the request can include an identifier that can be passed between the services. In process block 830, the debugging mode is controlled in accordance with the debug-requested parameter. Controlling the debugging mode can include passing the debugging mode between services of the service provider used to process the request, so as to establish a consistent debug behavior across all services. Additionally, controlling the debugging mode can include logging information associated with the request for each service used to process the request. The information that can be logged can include metadata associated with the request and log data associated with the request. Examples of controlling the debugging mode can include turning the debugging mode off, turning the debugging mode on, or adjusting a level of the debugging mode, wherein the debugging mode includes graduated levels.
It will be recognized that the services of the service provider can have debugging turned off until dynamic requests are made requesting debugging while generating a response to an API. Once the requests are processed, the debugging can be switched back off. In this way, the services can minimize unwanted debugging data, but can switch debugging on to a desired level in response to a request to do so.
Additionally, it will be recognized that the identifier can be used later via internal or external service requests to retrieve all log data associated with the API request. In a particular example, the log data and metadata can be retrieved using the identifier as a key. Various details regarding how the API was processed can be determined from the log data and metadata, such as through a visual display. For example, a graphical presentation can indicate each of the services called in the request, a total amount of memory used, CPU cycles used, network I/O used, disk I/O used, etc. Each of these parameters can be displayed or otherwise saved for later use. Additionally, timing information can be extracted, such as a total time to process the API request or a time for each service to process the request. Other uses of the log data can vary depending on the design.
With reference to
A computing system may have additional features. For example, the computing environment 900 includes storage 940, one or more input devices 950, one or more output devices 960, and one or more communication connections 970. An interconnection mechanism (not shown) such as a bus, controller, or network interconnects the components of the computing environment 900. Typically, operating system software (not shown) provides an operating environment for other software executing in the computing environment 900, and coordinates activities of the components of the computing environment 900.
The tangible storage 940 may be removable or non-removable, and includes magnetic disks, magnetic tapes or cassettes, CD-ROMs, DVDs, or any other medium which can be used to store information in a non-transitory way and which can be accessed within the computing environment 900. The storage 940 stores instructions for the software 980 implementing one or more innovations described herein.
The input device(s) 950 may be a touch input device such as a keyboard, mouse, pen, or trackball, a voice input device, a scanning device, or another device that provides input to the computing environment 900. The output device(s) 960 may be a display, printer, speaker, CD-writer, or another device that provides output from the computing environment 900.
The communication connection(s) 970 enable communication over a communication medium to another computing entity. The communication medium conveys information such as computer-executable instructions, audio or video input or output, or other data in a modulated data signal. A modulated data signal is a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media can use an electrical, optical, RF, or other carrier.
Although the operations of some of the disclosed methods are described in a particular, sequential order for convenient presentation, it should be understood that this manner of description encompasses rearrangement, unless a particular ordering is required by specific language set forth below. For example, operations described sequentially may in some cases be rearranged or performed concurrently. Moreover, for the sake of simplicity, the attached figures may not show the various ways in which the disclosed methods can be used in conjunction with other methods.
Any of the disclosed methods can be implemented as computer-executable instructions stored on one or more computer-readable storage media (e.g., one or more optical media discs, volatile memory components (such as DRAM or SRAM), or non-volatile memory components (such as flash memory or hard drives)) and executed on a computer (e.g., any commercially available computer, including smart phones or other mobile devices that include computing hardware). The term computer-readable storage media does not include communication connections, such as signals and carrier waves. Any of the computer-executable instructions for implementing the disclosed techniques as well as any data created and used during implementation of the disclosed embodiments can be stored on one or more computer-readable storage media. The computer-executable instructions can be part of, for example, a dedicated software application or a software application that is accessed or downloaded via a web browser or other software application (such as a remote computing application). Such software can be executed, for example, on a single local computer (e.g., any suitable commercially available computer) or in a network environment (e.g., via the Internet, a wide-area network, a local-area network, a client-server network (such as a cloud computing network), or other such network) using one or more network computers.
For clarity, only certain selected aspects of the software-based implementations are described. Other details that are well known in the art are omitted. For example, it should be understood that the disclosed technology is not limited to any specific computer language or program. For instance, the disclosed technology can be implemented by software written in C++, Java, Perl, JavaScript, Adobe Flash, or any other suitable programming language. Likewise, the disclosed technology is not limited to any particular computer or type of hardware. Certain details of suitable computers and hardware are well known and need not be set forth in detail in this disclosure.
It should also be well understood that any functionality described herein can be performed, at least in part, by one or more hardware logic components, instead of software. For example, and without limitation, illustrative types of hardware logic components that can be used include Field-programmable Gate Arrays (FPGAs), Program-specific Integrated Circuits (ASICs), Program-specific Standard Products (ASSPs), System-on-a-chip systems (SOCs), Complex Programmable Logic Devices (CPLDs), etc.
Furthermore, any of the software-based embodiments (comprising, for example, computer-executable instructions for causing a computer to perform any of the disclosed methods) can be uploaded, downloaded, or remotely accessed through a suitable communication means. Such suitable communication means include, for example, the Internet, the World Wide Web, an intranet, software applications, cable (including fiber optic cable), magnetic communications, electromagnetic communications (including RF, microwave, and infrared communications), electronic communications, or other such communication means.
The disclosed methods, apparatus, and systems should not be construed as limiting in any way. Instead, the present disclosure is directed toward all novel and nonobvious features and aspects of the various disclosed embodiments, alone and in various combinations and subcombinations with one another. The disclosed methods, apparatus, and systems are not limited to any specific aspect or feature or combination thereof, nor do the disclosed embodiments require that any one or more specific advantages be present or problems be solved.
In view of the many possible embodiments to which the principles of the disclosed invention may be applied, it should be recognized that the illustrated embodiments are only preferred examples of the invention and should not be taken as limiting the scope of the invention. Rather, the scope of the invention is defined by the following claims. We therefore claim as our invention all that comes within the scope of these claims.
Patent | Priority | Assignee | Title |
10824489, | Sep 30 2017 | Oracle International Corporation | Dynamic node rebalancing between container platforms |
10838788, | Sep 30 2017 | Oracle International Corporation | Real-time debugging instances in a deployed container platform |
10963283, | Dec 27 2018 | Nutanix, Inc | Configuration management for hybrid cloud |
11132241, | Sep 30 2017 | Oracle International Corporation | API registry in a container platform for automatically generating client code libraries |
11681573, | Sep 30 2017 | Oracle International Corporation | API registry in a container platform providing property-based API functionality |
11755393, | Sep 30 2017 | Oracle International Corporation | API registry in a container platform for automatically generating client code libraries |
Patent | Priority | Assignee | Title |
6446221, | May 19 1999 | ARM Limited | Debug mechanism for data processing systems |
6892324, | Jul 19 2000 | AVAGO TECHNOLOGIES GENERAL IP SINGAPORE PTE LTD | Multi-channel, multi-service debug |
6934937, | Mar 30 2000 | AVAGO TECHNOLOGIES INTERNATIONAL SALES PTE LIMITED | Multi-channel, multi-service debug on a pipelined CPU architecture |
6993585, | Dec 22 2000 | Unisys Corporation | Method and system for handling transaction requests from workstations to OLTP enterprise server systems utilizing a common gateway |
7992133, | Feb 14 2006 | AUREA SOFTWARE, INC | Techniques for debugging distributed applications |
8135572, | Jan 23 2007 | Microsoft Technology Licensing, LLC | Integrated debugger simulator |
8689186, | Dec 20 2006 | Oracle America, Inc | Execution of a BPEL process by simulating partners |
20030233634, | |||
20040148548, | |||
20070244904, | |||
20090135731, |
Executed on | Assignor | Assignee | Conveyance | Frame | Reel | Doc |
Mar 26 2014 | Amazon Technologies, Inc. | (assignment on the face of the patent) | / | |||
Apr 29 2014 | HIGGINS, CHRIS | Amazon Technologies, Inc | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 032965 | /0076 |
Date | Maintenance Fee Events |
Oct 14 2019 | REM: Maintenance Fee Reminder Mailed. |
Mar 30 2020 | EXP: Patent Expired for Failure to Pay Maintenance Fees. |
Date | Maintenance Schedule |
Feb 23 2019 | 4 years fee payment window open |
Aug 23 2019 | 6 months grace period start (w surcharge) |
Feb 23 2020 | patent expiry (for year 4) |
Feb 23 2022 | 2 years to revive unintentionally abandoned end. (for year 4) |
Feb 23 2023 | 8 years fee payment window open |
Aug 23 2023 | 6 months grace period start (w surcharge) |
Feb 23 2024 | patent expiry (for year 8) |
Feb 23 2026 | 2 years to revive unintentionally abandoned end. (for year 8) |
Feb 23 2027 | 12 years fee payment window open |
Aug 23 2027 | 6 months grace period start (w surcharge) |
Feb 23 2028 | patent expiry (for year 12) |
Feb 23 2030 | 2 years to revive unintentionally abandoned end. (for year 12) |