Service calling link generation method and device, equipment, medium and vehicle

Abstract

The invention relates to a service calling link generation method and device, equipment, a medium and a vehicle. According to the method, the tracking identifier of the service request can be created in response to the service request of the application; in response to the fact that at least one system service needed by the service request is called, a service calling identifier of each called system service is generated, and each service calling identifier corresponds to the tracking identifier; according to the sequence of calling the system services, sorting the at least one service calling identifier corresponding to the tracking identifier, constructing a service calling link of the service request, constructing the service calling link of the service request of the application program, and calling the service request of the application program through the service calling link. The complete calling path and the calling process of the system service of the service request of the application program can be determined, and great convenience is provided for subsequent abnormal system service positioning.

Description

Technical Field

[0001] The present disclosure relates to the field of computer technology, and in particular to a method, apparatus, device, medium, and vehicle for generating a service call link. Background Art

[0002] Currently, when an application is running in a computer system, it calls various system services (such as file system services, memory management services, device driver services, etc.) to ensure the normal operation of the application.

[0003] When an abnormality occurs in a system service called during the operation of an application, it is necessary to locate and diagnose the abnormal system service to eliminate the abnormal system service and ensure the normal operation of the application. In related technologies, abnormal system services are usually identified through the log files of the computer system. However, log files can only connect all log point events in series by time and cannot obtain the calling path of the application to the system service. Therefore, it is impossible to determine which application called the abnormal system service through log files. It is necessary to start from the entry service called by the application and check the called services in turn. Only after checking multiple unnecessary services can the abnormal system service be accurately located, resulting in low positioning efficiency and accuracy.

[0004] Therefore, the calling path of the application to the system service is crucial to the location of abnormal system services. A method for generating a service call link is urgently needed to solve the current technical problems. Summary of the Invention

[0005] In order to solve the above technical problems, the present disclosure provides a method, apparatus, device, medium and vehicle for generating a service call link.

[0006] A first aspect of the present disclosure provides a method for generating a service call link, comprising:

[0007] In response to a service request from an application, create a tracking identifier for the service request;

[0008] In response to at least one system service required by the service request being called, generating a service call identifier for each called system service, each service call identifier corresponding to a tracking identifier;

[0009] According to the order in which each system service is called, at least one service call identifier corresponding to the tracking identifier is sorted to construct a service call link for the service request.

[0010] A second aspect of the present disclosure provides a device for generating a service call link, including:

[0011] A creation module, configured to create a tracking identifier of the service request in response to a service request of an application program;

[0012] A generation module, configured to generate a service call identifier for each system service that is called in response to at least one system service required by a service request, and each service call identifier corresponds to a tracing identifier.

[0013] A construction module, configured to sort at least one service call identifier corresponding to the tracing identifier according to the order in which each system service is called, and construct a service call chain of the service request.

[0014] A third aspect of the present disclosure provides a computer device, including:

[0015] A memory and a processor, wherein a computer program is stored in the memory, and when the computer program is executed by the processor, the method for generating a service call chain in the first aspect described above can be implemented.

[0016] A fourth aspect of the present disclosure provides a computer-readable storage medium, in which a computer program is stored, and when the computer program is executed by a processor, the method for generating a service call chain in the first aspect described above can be implemented.

[0017] A fifth aspect of the present disclosure provides a vehicle, including the service call chain generation device in the second aspect described above and / or the computer device in the third aspect described above and / or the computer-readable storage medium in the fourth aspect described above, and the method for generating a service call chain in the first aspect described above can be implemented.

[0018] The technical solution provided by the present disclosure has the following advantages compared with the prior art:

[0019] The present disclosure can create a tracing identifier for a service request in response to a service request of an application program; generate a service call identifier for each system service that is called in response to at least one system service required by the service request, and each service call identifier corresponds to the tracing identifier; sort at least one service call identifier corresponding to the tracing identifier according to the order in which each system service is called, and construct a service call chain of the service request, and can construct a service call chain of the service request of the application program. Through the service call chain, the complete call path and call process of the system service of the service request of the application program can be determined, which provides great convenience for subsequent abnormal system service positioning. Description of the Drawings

[0020] The drawings here are incorporated into the specification and form a part of this specification, showing embodiments consistent with the present disclosure, and are used together with the specification to explain the principles of the present disclosure.

[0021] To more clearly illustrate the technical solutions in the embodiments of the present disclosure or the prior art, the following will briefly introduce the accompanying drawings required for the description of the embodiments or the prior art. Obviously, for those of ordinary skill in the art, without creative efforts, other drawings can also be obtained based on these drawings.

[0022] Figure 1 is a flowchart of a method for generating a service call link provided by an embodiment of the present disclosure;

[0023] Figure 2a is a schematic diagram of a service call link provided by an embodiment of the present disclosure;

[0024] Figure 2b is another schematic diagram of a service call link provided by an embodiment of the present disclosure;

[0025] Figure 3 is a flowchart of a method for locating an abnormal system service provided by an embodiment of the present disclosure;

[0026] Figure 4 is a schematic structural diagram of a device for generating a service call link provided by an embodiment of the present disclosure;

[0027] Figure 5 is a schematic structural diagram of a computer device provided by an embodiment of the present disclosure. Detailed implementation manners

[0028] In order to more clearly understand the above objects, features, and advantages of the present disclosure, the following will further describe the solutions of the present disclosure. It should be noted that, without conflict, the embodiments of the present disclosure and the features in the embodiments can be combined with each other.

[0029] In the following description, many specific details are set forth to fully understand the present disclosure, but the present disclosure can also be implemented in other ways different from those described herein; obviously, the embodiments in the specification are only a part of the embodiments of the present disclosure, rather than all of the embodiments.

[0030] It should be understood that the steps recorded in the method embodiments of the present disclosure can be executed in different orders and / or in parallel. In addition, the method embodiments may include additional steps and / or omit the steps shown. The scope of the present disclosure is not limited in this regard.

[0031] It should be noted that in this document, relational terms such as "first" and "second" are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the terms "comprise", "include" or any other variant thereof are intended to cover non-exclusive inclusion, such that a process, method, article or device comprising a series of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article or device. Without further limitation, an element defined by the statement "comprising an..." does not exclude the presence of additional identical elements in the process, method, article or device comprising the element.

[0032] It should be noted that the modification of "one" and "multiple" mentioned in this disclosure is illustrative rather than restrictive. Those skilled in the art should understand that unless otherwise clearly specified in the context, it should be understood as "one or more".

[0033] The method for generating a service call link provided by an embodiment of the present disclosure can be executed by a computer device, which can be understood as any device with processing and computing capabilities. The device may include, but is not limited to, mobile terminals such as smart phones, laptop computers, tablet computers (PADs), vehicle-mounted terminals (such as vehicle-mounted navigation terminals), wearable devices, etc., and fixed electronic devices such as digital TVs and desktop computers.

[0034] To better understand the inventive concept of the embodiments of the present disclosure, the technical solutions of the embodiments of the present disclosure will be described below in conjunction with exemplary embodiments.

[0035] Figure 1 is a flowchart of a method for generating a service call link provided by an embodiment of the present disclosure. As Figure 1 shown, the method for generating a service call link provided in this embodiment includes the following steps:

[0036] Step 110: Create a tracking identifier for the service request in response to the service request of the application program.

[0037] In an embodiment of the present disclosure, when the application program in the computer device is running, it can send a service request to the operating system in the computer device. The service request may at least include the service identifier of the first system service requested by the application program. The link tracking system in the computer device can create a tracking identifier for the service request in response to the service request of the application program.

[0038] The tracking identifier of the service request can be understood as an identifier that can uniquely mark the entire service request process, and the service request corresponds to the tracking identifier one by one.

[0039] System services can be understood as programs, routines, or processes that execute operating system functions in a computer device to support the normal operation of application programs. For example, system services can include file system services, memory management services, device driver services, etc.

[0040] Step 120: In response to at least one system service required by a service request being called, generate a service call identifier for each called system service, and each service call identifier corresponds to a trace identifier.

[0041] In the embodiments of the present disclosure, when an application program runs in the system, the application program itself knows which system services it needs to call, and the system services that need to be called when the application program runs are determined during the development of the application program. The service request of the application program needs to call at least one system service. For example, the system service can be called through Inter-Process Communication (IPC). The link tracing system in the computer device can generate a service call identifier for each called system service in response to at least one system service required by the service request being called. Among them, the service call identifier of each system service called by the service request corresponds to the trace identifier of the service request.

[0042] The service call identifier of a system service can be understood as representing the position of the application program's current call to this system service in the entire service call link.

[0043] The service call identifier can include the called time period of the system service and the service identifier of the system service. The service identifier can be understood as a unique identifier that can represent the system service.

[0044] Step 130: Sort at least one service call identifier corresponding to the trace identifier in the order of the system services being called, and construct a service call link for the service request.

[0045] In the embodiments of the present disclosure, after obtaining the trace identifier of the service request and the service call identifier of each called system service, the link tracing system in the computer device can sort at least one service call identifier corresponding to the trace identifier in the order of the system services being called, and construct a service call link for the service request.

[0046] The service call link can be understood as the call path of the service request of the application program to at least one system service in terms of time sequence.

[0047] For example, as Figure 2a shown Figure 2aA schematic diagram of a service call link provided by an embodiment of the present disclosure. In response to a service request of an application, a link tracing system in a computer device can create a tracing identifier 0a1234 for the service request. When system service A is the first system service called for the service request of the application, the service call identifier of system service A constructed by the link tracing system in the computer device is 0, representing the root node of the entire service call link. If system service A needs to call system service B, system service C, and system service D, the link tracing system in the computer device will construct the service call identifier 0.1 of system service B, the service call identifier 0.2 of system service C, and the service call identifier 0.3 of system service D after the service call identifier 0. If system service C also calls system service E and system service F when processing the service request, the link tracing system in the computer device will construct the service call identifier 0.2.1 of system service E and the service call identifier 0.2.2 of system service F after the service call identifier 0.2 of system service C. Among them, all service call identifiers correspond to the tracing identifier of the service request. Thus, at least one service call identifier corresponding to the tracing identifier can be sorted according to the order in which each system service is called, and the service call link of the service request can be constructed. The service call identifier of the system service can help track and organize the path structure of the service call link.

[0048] For another example, Figure 2a the schematic diagram of the service call link can be converted into Figure 2b the service call link timing diagram shown in Figure 2b As shown in the figure, in terms of timing, the service request first calls system service A, and system service A then calls system service B, system service C, and system service D. System service C calls system service E and system service F.

[0049] For another example, taking the example of an application completing a file data reading operation, the process of the service call link generation method is described as follows:

[0050] The application in the computer device can send a service request to the operating system in the computer device. This service request needs to call the file system service to read a file data. The link tracing system in the computer device can construct the tracing identifier of this service request and can, in response to the service request, call the file system service to generate the service call identifier of the file system service;

[0051] After the file system service in the operating system receives the service request, it can call the memory management system service to obtain enough buffers to read the file. The link tracing system can, in response to the file system service calling the memory management system service, generate the service call identifier of the memory management system service;

[0052] Then, the file system service reads the file data on the disk by calling the device driver system service. The link tracing system can generate a service call identifier for the device driver system service in response to the file system service calling the device driver system service;

[0053] After the device driver finishes reading the file data, the file system service can copy the file data to the buffer applied for previously and call the data transmission system service to send the file data to the application program. The link tracing system can generate a service call identifier for the data transmission system service in response to the file system service calling the data transmission system service;

[0054] Finally, the application program receives the file data to be read and completes a file data reading operation. The link tracing system can construct a service call link for the service request based on the tracing identifier of the service request and each system service called by the service request.

[0055] In the embodiments of the present disclosure, in response to a service request of an application program, a tracing identifier of the service request can be created; in response to at least one system service required by the service request being called, a service call identifier for each called system service can be generated, and each service call identifier corresponds to the tracing identifier; according to the order in which each system service is called, at least one service call identifier corresponding to the tracing identifier is sorted to construct a service call link for the service request, and a service call link for the service request of the application program can be constructed. Through the service call link, the complete call path and call process of the system service of the service request of the application program can be determined, which provides great convenience for subsequent abnormal system service positioning.

[0056] In some embodiments of the disclosure, in step 110 above, in response to a service request of an application program, creating a tracing identifier of the service request may include steps 1101-1102:

[0057] Step 1101: In response to a service request of an application program, obtain the program identifier of the application program, the request time of the service request, the sequence number of the service request, and the process identifier for executing the service request.

[0058] In the embodiments of the present disclosure, in response to a service request of an application program, the link tracing system in the computer device can obtain the program identifier of the application program, the request time of the service request, and the process identifier for executing the service request.

[0059] The program identifier of the application program can be understood as an identifier that can uniquely represent the application program.

[0060] The request time of the service request can be understood as the start time when the operating system in the computer device responds to the service request.

[0061] The serial number of the service request can be understood as the serial number for the operating system to execute the service request, which can be understood as an incrementing sequence in the operating system. For example, it increments from 1000 to 9000 and then loops back to 1000.

[0062] The process identifier of the service request can be understood as the identifier that can uniquely represent the process of the operating system in the computer device executing the service request. The process identifier can be used to avoid the situation of tracking identifier conflicts in a single-machine multi-process environment.

[0063] Step 1102, generate a tracking identifier for the service request based on the program identifier of the application, the request time of the service request, the serial number of the service request, and the process identifier of the service request execution.

[0064] In the embodiments of the present disclosure, the link tracking system in the computer device can generate a tracking identifier for the service request based on the program identifier of the application, the request time of the service request, the serial number of the service request, and the process identifier of the service request execution.

[0065] For example, the program identifier of the application, the request time of the service request, the serial number of the service request, and the process identifier of the service request execution can be combined to generate the tracking identifier for the service request.

[0066] For example, the tracking identifier of the service request can be 0ab1234c|14030000002|1006|56696.

[0067] Among them, the first 8 bits (0ab1234c): refer to the program identifier of the application, represented in hexadecimal, which can be used to determine the starting point of the service request.

[0068] The middle 13 bits (14030000002): represent the time stamp corresponding to the request time of the service request.

[0069] The next 4 bits (1006): represent the serial number of the service request.

[0070] The last 5 bits (56696): represent the process identifier of the operating system executing the service request.

[0071] In some other embodiments of the present disclosure, in step 120 above, in response to at least one system service required for the service request being called, generating a service call identifier for each called system service may include steps 1201-1202:

[0072] Step 1201, in response to at least one system service required for the service request being called, obtain the service identifier of each called system service and the called period of each system service.

[0073] In the embodiments of the present disclosure, the link tracing system in a computer device can monitor the invocation of system services. In response to the invocation of at least one system service required for a service request, the link tracing system can obtain the service identifiers of the invoked system services, and record the period between the start invocation time and the end invocation time of the system service, so as to obtain the invoked period of each system service.

[0074] The invoked period can be understood as the period between the start invocation time and the end invocation time of the system service.

[0075] Step 1202: Generate a service invocation identifier for each system service based on the service identifiers of the invoked system services and the invoked periods of the system services.

[0076] In the embodiments of the present disclosure, the link tracing system in a computer device can generate a service invocation identifier for each system service based on the service identifiers of the invoked system services and the invoked periods of the system services.

[0077] For example, the service identifier of the invoked system service and the invoked period of the system service can be combined to generate the service invocation identifier of the system service.

[0078] In some embodiments of the present disclosure, in step 130 above, sorting at least one service invocation identifier corresponding to the tracing identifier in the order of the sequence of invocation of each system service to construct the service invocation link of the service request may include steps 1301 - 1303:

[0079] Step 1301: Obtain the start time of the service request from the tracing identifier of the service request.

[0080] Step 1302: Obtain the invoked period of the system service from the service invocation identifier of the system service.

[0081] Step 1303: Sort the service identifiers corresponding to the tracing identifier in the order of the start time and the invoked period to obtain the service invocation link of the service request.

[0082] In other embodiments, in step 130 above, sorting at least one service invocation identifier corresponding to the tracing identifier in the order of the sequence of invocation of each system service to construct the service invocation link of the service request may include steps 1311 - 1314:

[0083] Step 1311: For each system service, obtain the invoked period of the system service from the service invocation identifier of the system service.

[0084] Step 1312: For each system service, obtain the status information of the system service during the called period from the log data of the system service.

[0085] In the embodiments of the present disclosure, in the operating system of a computer device, each system service has a corresponding log file, and the log data of the system service during the running process is recorded in the log file, which may include information such as the running start time, running end time, status, etc.

[0086] For each system service, the link tracing system in the computer device can obtain the status information of the system service during the called period from the log data of the system service.

[0087] The status information may include normal status information and abnormal status information. In some embodiments, the status information can be represented by a status identifier.

[0088] Step 1313: Determine the status information of the system service during the called period as the status information corresponding to the service call identifier of the system service.

[0089] In the embodiments of the present disclosure, after obtaining the status information of the system service during the called period, the link tracing system in the computer device can determine the status information of the system service during the called period as the status information of the service call identifier of the system service.

[0090] Step 1314: Sort at least one service call identifier corresponding to the tracing identifier and the status information corresponding to the service call identifier in the order of the sequence in which each system service is called, and construct a service call link of the service request.

[0091] In the embodiments of the present disclosure, the link tracing system in the computer device can sort at least one service call identifier corresponding to the tracing identifier and the status information corresponding to the service call identifier in the order of the sequence in which each system service is called, and construct a service call link of the service request.

[0092] Thus, the service call link of the service request may include the status information of each system service required by the service request during the called period.

[0093] In some embodiments of the present disclosure, after sorting at least one service call identifier corresponding to the tracing identifier in the order of the sequence in which each system service is called and constructing the service call link of the service request, the computer device can locate the abnormal system service based on the service call link of the service request, and specifically, it can execute Figure 3 The flowchart of a method for locating an abnormal system service provided, as Figure 3 shown, the method for locating an abnormal system service provided in this embodiment includes the following steps:

[0094] Step 310: For each system service included in the service call link, obtain the called period of the system service from the service call identifier of the system service.

[0095] Step 320: For each system service included in the service call link, obtain the status information of the system service during the called period from the log data of the system service.

[0096] In the embodiments of the present disclosure, in the operating system of a computer device, each system service has a corresponding log file, and the log data of the system service during the running process is recorded in the log file, which may include information such as the running start time, running end time, status, etc.

[0097] For each system service included in the service call link, the link tracing system in the computer device can obtain the status information of the system service during the called period from the log data of the system service.

[0098] The status information may include normal status information and abnormal status information. In some embodiments, the status information may be represented by a status identifier.

[0099] Step 330: In response to the existence of abnormal status information in the status information of each system service, determine the abnormal system service corresponding to the abnormal status information in the service call link.

[0100] In the embodiments of the present disclosure, after obtaining the status information of each system service included in the service call link, the link tracing system in the computer device can, in response to the existence of abnormal status information in the status information of each system service, determine the abnormal system service corresponding to the abnormal status information in the service call link.

[0101] Thus, the system service in an abnormal state can be quickly and accurately located based on the service call link of the service request.

[0102] In other embodiments of the present disclosure, after sorting at least one service call identifier corresponding to the tracing identifier and the status information corresponding to the service call identifier in the order of the calling sequence of each system service and constructing the service call link of the service request, the computer device can, in response to the existence of abnormal status information in the service call link, determine the abnormal system service corresponding to the abnormal status information in the service call link.

[0103] Thus, the system service in an abnormal state can be quickly and accurately located based on the service call link of the service request.

[0104] Figure 4FIG. 0 is a schematic structural diagram of a service call link generation device provided by an embodiment of the present disclosure. This device can be understood as the above computer device or some functional modules in the above computer device. As Figure 4 shown, the service call link generation device 400 includes:

[0105] A creation module 410, configured to create a tracking identifier for a service request in response to a service request of an application;

[0106] A generation module 420, configured to generate a service call identifier for each system service that is called in response to at least one system service required by the service request, and each service call identifier corresponds to the tracking identifier;

[0107] A construction module 430, configured to sort at least one service call identifier corresponding to the tracking identifier in the order in which each system service is called, and construct a service call link for the service request.

[0108] Optionally, the above creation module includes:

[0109] A first acquisition sub-module, configured to acquire the program identifier of the application, the request time of the service request, the serial number of the service request, and the process identifier for executing the service request in response to the service request of the application;

[0110] A first construction sub-module, configured to generate a tracking identifier for the service request based on the program identifier, the request time, and the process identifier.

[0111] Optionally, the above generation module includes:

[0112] A second acquisition sub-module, configured to acquire the service identifier of each system service that is called and the called period of each system service in response to at least one system service required by the service request;

[0113] A second construction sub-module, configured to generate a service call identifier for each system service based on the service identifier and the called period.

[0114] Optionally, the above construction module includes:

[0115] A third acquisition sub-module, configured to acquire the start time of the service request from the tracking identifier;

[0116] A fourth acquisition sub-module, configured to acquire the called period of the system service from the service call identifier of the system service;

[0117] A sorting sub-module, configured to sort the service identifiers corresponding to the tracking identifier in the chronological order of the start time and the called period, and obtain a service call link for the service request.

[0118] Optionally, the above building blocks include:

[0119] A fifth acquisition sub-module, configured to, for each system service, acquire the called period of the system service from the service call identifier of the system service;

[0120] A sixth acquisition sub-module, configured to, for each system service, acquire the status information of the system service during the called period from the log data of the system service;

[0121] A determination sub-module, configured to determine the status information of the system service during the called period as the status information corresponding to the service call identifier of the system service;

[0122] A third building sub-module, configured to sort at least one service call identifier corresponding to the trace identifier and the status information corresponding to the service call identifier according to the order in which each system service is called, and build a service call link of the service request.

[0123] Optionally, the above service call link generation device includes:

[0124] A first acquisition module, configured to, for each system service included in the service call link, acquire the called period of the system service from the service call identifier of the system service;

[0125] A second acquisition module, configured to, for each system service included in the service call link, acquire the status information of the system service during the called period from the log data of the system service;

[0126] A first determination module, configured to, in response to the existence of abnormal status information in the status information of each system service, determine an abnormal system service corresponding to the abnormal status information in the service call link.

[0127] The service call link generation device provided by the embodiments of the present disclosure can implement the methods of any of the above embodiments, and its execution manner and beneficial effects are similar, and will not be described in detail here.

[0128] The embodiments of the present disclosure further provide a computer device, which includes a processor and a memory. Among them, a computer program is stored in the memory, and when the computer program is executed by the processor, the methods of any of the above embodiments can be implemented, and its execution manner and beneficial effects are similar, and will not be described in detail here.

[0129] Figure 5 is a schematic structural diagram of a computer device provided by the embodiments of the present disclosure, as Figure 5As shown, the computer device 500 may include a processor 510 and a memory 520. Among them, a computer program 521 is stored in the memory 520. When the computer program 521 is executed by the processor 510, the method provided in any of the above embodiments can be implemented. The execution manner and beneficial effects are similar and will not be elaborated here.

[0130] Of course, for simplicity, Figure 5 only some of the components related to the present invention in the computer device 500 are shown, and components such as a bus, an input / output interface, an input device, and an output device are omitted. In addition, according to specific application scenarios, the computer device 500 may further include any other appropriate components.

[0131] The embodiments of the present disclosure provide a computer-readable storage medium. A computer program is stored in the storage medium. When the computer program is executed by a processor, the method provided in any of the above embodiments can be implemented. The execution manner and beneficial effects are similar and will not be elaborated here.

[0132] The above computer-readable storage medium may adopt any combination of one or more readable media. The readable media may be a readable signal medium or a readable storage medium. The readable storage medium may include, for example, but is not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the above. More specific examples (non-exhaustive list) of the readable storage medium include: an electrical connection having one or more wires, a portable disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above.

[0133] The above computer program may be written in any combination of one or more programming languages to write program code for performing the operations of the embodiments of the present disclosure. The programming languages include object-oriented programming languages such as Java and C++, and also include conventional procedural programming languages such as the "C" language or similar programming languages. The program code may be executed entirely on the user's computer device, partially on the user device, executed as an independent software package, partially on the user's computer device and partially on a remote computer device, or entirely on a remote computer device or server.

[0134] The embodiments of the present disclosure provide a vehicle. The vehicle may include the above-described service call link generation device and / or the above-described computer device and / or the above-described computer-readable storage medium, and the method provided in any of the above embodiments can be implemented. The execution manner and beneficial effects are similar and will not be elaborated here.

[0135] The above description is only a preferred embodiment of the present disclosure and an explanation of the applied technical principles. Those skilled in the art should understand that the scope of disclosure involved in the present disclosure is not limited to the technical solutions formed by the specific combination of the above technical features, and should also cover other technical solutions formed by any combination of the above technical features or their equivalent features without departing from the above disclosure concept. For example, the technical solutions formed by mutually replacing the above features with the technical features (but not limited to) having similar functions disclosed in the present disclosure.

[0136] In addition, although the operations are depicted in a particular order, this should not be construed as requiring that the operations be performed in the particular order shown or in sequential order. In certain environments, multitasking and parallel processing may be advantageous. Similarly, although several specific implementation details are included in the above discussion, these should not be construed as limiting the scope of the present disclosure. Certain features described in the context of separate embodiments may also be implemented combinatorially in a single embodiment. Conversely, the various features described in the context of a single embodiment may also be implemented separately or in any suitable sub-combination in multiple embodiments.

[0137] The above are only specific implementation manners of the present disclosure, enabling those skilled in the art to understand or implement the present disclosure. Various modifications to these embodiments will be obvious to those skilled in the art, and the general principles defined herein can be implemented in other embodiments without departing from the spirit or scope of the present disclosure. Therefore, the present disclosure will not be limited to the embodiments described herein, but rather to the broadest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for generating a service call link, characterized in that Including: Responding to a service request of an application, creating a tracking identifier for the service request; Responding to at least one system service required by the service request being called, generating a service call identifier for each called system service, each of the service call identifiers corresponding to the tracking identifier; Sorting at least one service call identifier corresponding to the tracking identifier according to the order in which the system services are called, and constructing a service call link for the service request.

2. The method according to claim 1, wherein The step of responding to a service request of an application and creating a tracking identifier for the service request includes: Responding to a service request of an application, obtaining the program identifier of the application, the request time of the service request, the serial number of the service request, and the process identifier for executing the service request; Generating a tracking identifier for the service request based on the program identifier, the request time, and the process identifier.

3. The method according to claim 1, characterized in that The step of responding to at least one system service required by the service request being called and generating a service call identifier for each called system service includes: Responding to at least one system service required by the service request being called, obtaining the service identifier of each called system service and the called period of each system service; Generating a service call identifier for each system service based on the service identifier and the called period.

4. The method according to claim 1, wherein The step of sorting at least one service call identifier corresponding to the tracking identifier according to the order in which the system services are called and constructing a service call link for the service request includes: Obtaining the start time of the service request from the tracking identifier; Obtaining the called period of the system service from the service call identifier of the system service; Sorting each service identifier corresponding to the tracking identifier according to the chronological order of the start time and the called period, and obtaining the service call link for the service request.

5. The method according to claim 1, wherein The step of sorting at least one service call identifier corresponding to the tracking identifier according to the order in which the system services are called and constructing a service call link for the service request includes: For each system service, obtaining the called period of the system service from the service call identifier of the system service; For each system service, obtaining the status information of the system service during the called period from the log data of the system service; Determining the status information of the system service during the called period as the status information corresponding to the service call identifier of the system service; Sorting at least one service call identifier corresponding to the tracking identifier and the status information corresponding to the service call identifier according to the order in which the system services are called, and constructing a service call link for the service request.

6. The method according to claim 1, characterized in that After the step of sorting at least one service call identifier corresponding to the tracking identifier according to the order in which the system services are called and constructing a service call link for the service request, the method further includes: For each of the system services included in the service call link, obtain the called period of the system service from the service call identifier of the system service; For each of the system services included in the service call link, obtain the status information of the system service during the called period from the log data of the system service; In response to the existence of abnormal status information in the status information of each of the system services, determine the abnormal system service corresponding to the abnormal status information in the service call link.

7. An apparatus for generating a service call link, characterized in that Comprising: A creation module, configured to create a tracking identifier for the service request in response to a service request of an application; A generation module, configured to generate a service call identifier for each called system service in response to at least one system service required by the service request being called, and each of the service call identifiers corresponds to the tracking identifier; A construction module, configured to sort at least one service call identifier corresponding to the tracking identifier in the order of the system services being called, and construct a service call link of the service request.

8. A computer device, characterized in that, Comprising: A memory and a processor, wherein a computer program is stored in the memory, and when the computer program is executed by the processor, the method for generating a service call link according to any one of claims 1-6 is implemented.

9. A computer-readable storage medium, characterized in that, A computer program is stored in the storage medium, and when the computer program is executed by a processor, the method for generating a service call link according to any one of claims 1-6 is implemented.

10. A vehicle, characterized in that, Comprising the service call link generation device according to claim 7 and / or the computer device according to claim 8 and / or the computer-readable storage medium according to claim 9, and implementing the method for generating a service call link according to any one of claims 1-6.

Images