CN114301988A - Distributed calling method and device, storage medium and electronic equipment - Google Patents
Distributed calling method and device, storage medium and electronic equipment Download PDFInfo
- Publication number
- CN114301988A CN114301988A CN202111608274.5A CN202111608274A CN114301988A CN 114301988 A CN114301988 A CN 114301988A CN 202111608274 A CN202111608274 A CN 202111608274A CN 114301988 A CN114301988 A CN 114301988A
- Authority
- CN
- China
- Prior art keywords
- calling
- call
- service
- distributed
- information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 62
- 238000003860 storage Methods 0.000 title claims abstract description 22
- 238000004590 computer program Methods 0.000 claims description 5
- 230000002085 persistent effect Effects 0.000 claims description 4
- 230000004044 response Effects 0.000 claims description 4
- 238000012546 transfer Methods 0.000 claims description 2
- 238000012544 monitoring process Methods 0.000 abstract description 11
- 230000008569 process Effects 0.000 abstract description 10
- 238000004891 communication Methods 0.000 abstract description 5
- 238000005516 engineering process Methods 0.000 abstract description 2
- 238000010586 diagram Methods 0.000 description 10
- 238000012545 processing Methods 0.000 description 10
- 238000013499 data model Methods 0.000 description 7
- 238000011144 upstream manufacturing Methods 0.000 description 4
- 230000003287 optical effect Effects 0.000 description 3
- 206010063385 Intellectualisation Diseases 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 238000007726 management method Methods 0.000 description 2
- 238000004519 manufacturing process Methods 0.000 description 2
- 239000013307 optical fiber Substances 0.000 description 2
- 230000008447 perception Effects 0.000 description 2
- 230000000644 propagated effect Effects 0.000 description 2
- 230000009897 systematic effect Effects 0.000 description 2
- 230000002159 abnormal effect Effects 0.000 description 1
- 230000009471 action Effects 0.000 description 1
- 230000006978 adaptation Effects 0.000 description 1
- 230000002776 aggregation Effects 0.000 description 1
- 238000004220 aggregation Methods 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 230000015572 biosynthetic process Effects 0.000 description 1
- 239000008280 blood Substances 0.000 description 1
- 210000004369 blood Anatomy 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000011010 flushing procedure Methods 0.000 description 1
- 239000003999 initiator Substances 0.000 description 1
- 238000009434 installation Methods 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 230000003252 repetitive effect Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 238000013024 troubleshooting Methods 0.000 description 1
Images
Landscapes
- Debugging And Monitoring (AREA)
Abstract
The disclosure provides a distributed calling method, a distributed calling device, a storage medium and electronic equipment, relates to the technical field of communication, and at least solves the problem that effective monitoring cannot be formed on end-to-end service process scenes of cross-group and province in the related technology to a certain extent. The related distributed calling method comprises the following steps: acquiring a call request initiated by a requester; acquiring calling chain information from the calling request, wherein the calling chain information comprises calling chain identification type information and application service information, and the application service information comprises application service identification; generating new call chain information, and recording the new call chain information in the call request to obtain an updated call request; and sending the updated calling request to a receiver. The embodiment of the disclosure enables the receiver to effectively monitor the end-to-end business process scene of the cross-group and province according to the calling identification information and the application service identification.
Description
Technical Field
The present disclosure relates to the field of communications technologies, and in particular, to a distributed call method and apparatus, a storage medium, and an electronic device.
Background
In order to promote network intellectualization, business ecology and operation intellectualization, four intelligent reconstructions of network, business, operation and management are implemented. An enterprise central platform with data drive as a core is created by taking an intelligent IT system as a carrier, data is changed into blood flowing in the enterprise, and a market and one-line oriented integrated intelligent operation system is constructed.
At present, the IT operation and maintenance capability mainly takes province and group headquarters as units, and an independent IT network management monitoring system is established, so that the monitoring of an IT production system and a production flow of the province/headquarters is realized. This monitoring capability is effective for monitoring in the present area. However, effective monitoring cannot be formed for an end-to-end business process scenario across a group and a province. For example, in the case of a failure of a system in a certain area, the domain-divided monitoring system can only show the operation monitoring result of the IT system in the home location where the service process is located, but cannot obtain the overall operation condition of the service process. This results in inefficient problem communication, unclear fault responsibility, and excessively long processing time in headquarters and provinces of the group, and affects the perception of the IT users on the services.
Disclosure of Invention
The present disclosure aims to provide a distributed calling method, a distributed calling device, a storage medium, and an electronic device, which at least overcome, to a certain extent, a problem in the related art that effective monitoring cannot be formed for an end-to-end service flow scenario across a group and a province.
One or more embodiments of the present disclosure provide a distributed call method, including: acquiring a call request initiated by a requester; acquiring calling chain information from the calling request, wherein the calling chain information comprises calling chain identification type information and application service information, and the application service information comprises application service identification; generating new call chain information, and recording the new call chain information in the call request to obtain an updated call request; and sending the updated calling request to a receiver.
Optionally, the application service information further includes: service port number.
Optionally, the application service identifier includes: and uniformly coding the whole network and applying the service name.
Optionally, the call chain information further includes: at least one of the following traffic fields: the service serial number, the type of the current node in the service invocation link, and the address of the invoked service.
Optionally, the call chain information further includes: at least one of the following traffic fields: the system comprises a service scene code, a service order number, a service number, order generation time, order completion time, order state and a service return result code.
Optionally, the call chain information further includes: at least one of the following traffic fields: the method comprises the steps of persistent address, network card physical address corresponding to Internet Protocol (IP) address in a network service endpoint, program error identification and error type.
Optionally, the call chain information further includes: at least one of the following traffic fields: a domain portion of a Uniform Resource Locator (URL) or host header, a hypertext transfer protocol (HTTP) method or verb, an absolute HTTP path, a URL address, an HTTP status code, a request body size, and a response body size.
Optionally, the call chain information further includes: at least one of the following traffic fields: client address in network call, server address in network call, and internal call.
One or more embodiments of the present disclosure also provide a distributed calling apparatus, including: the first acquisition module is used for acquiring a call request initiated by a requester; a second obtaining module, configured to obtain call chain information from the call request, where the call chain information includes call chain identifier information and application service information, and the application service information includes an application service identifier; the generation module is used for generating new calling chain information and recording the new calling chain information in the calling request to obtain an updated calling request; and the sending module is used for sending the updated calling request to the receiving party.
One or more embodiments of the present disclosure also provide an electronic device including: a processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to execute any one of the distributed calling methods provided by the embodiments of the present disclosure via execution of the executable instructions.
One or more embodiments of the present disclosure also provide a computer-readable storage medium on which a computer program is stored, the computer program, when executed by a processor, implementing any one of the distributed calling methods provided by the embodiments of the present disclosure.
According to the distributed calling method, the distributed calling device, the storage medium and the electronic equipment, the calling chain information is transmitted in the whole link of distributed calling, and the calling chain information has calling identification type information and application service identification, so that a receiver can effectively monitor an end-to-end business process scene which is across groups and provinces according to the calling identification type information and the application service identification.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and together with the description, serve to explain the principles of the disclosure. It is to be understood that the drawings in the following description are merely exemplary of the disclosure, and that other drawings may be derived from those drawings by one of ordinary skill in the art without the exercise of inventive faculty.
FIG. 1 is a flow diagram of a distributed invocation method in accordance with one or more embodiments of the present disclosure;
FIG. 2 is a schematic diagram of the time required to locate a full-network business IT fault using a distributed invocation method of one or more embodiments of the present disclosure;
FIG. 3 is a schematic diagram of the time required to track cross-regional flushing traffic using a distributed call method according to one or more embodiments of the present disclosure;
FIG. 4 is a schematic diagram of a call chain data model in accordance with one or more embodiments of the present disclosure;
FIG. 5 is a flow diagram of a distributed invocation method in accordance with one or more embodiments of the present disclosure;
FIG. 6 is a flow diagram of a distributed invocation apparatus in accordance with one or more embodiments of the present disclosure; and
fig. 7 is a schematic structural diagram of an electronic device according to one or more embodiments of the present disclosure.
Detailed Description
Example embodiments will now be described more fully with reference to the accompanying drawings. Example embodiments may, however, be embodied in many different forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of example embodiments to those skilled in the art. The described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.
Furthermore, the drawings are merely schematic illustrations of the present disclosure and are not necessarily drawn to scale. The same reference numerals in the drawings denote the same or similar parts, and thus their repetitive description will be omitted. Some of the block diagrams shown in the figures are functional entities and do not necessarily correspond to physically or logically separate entities. These functional entities may be implemented in the form of software, or in one or more hardware modules or integrated circuits, or in different networks and/or processor devices and/or microcontroller devices.
Fig. 1 is a flowchart of a distributed invocation method according to one or more embodiments of the present disclosure, as shown in fig. 1, the method including:
step S102: acquiring a call request initiated by a requester;
optionally, the distributed invocation method of the embodiment of the present disclosure may be executed by any node except the initial invocation end in the distributed invocation link. Accordingly, the requestor may be the initiator of the invocation request in the distributed invocation loop.
Step S104: acquiring calling chain information from the calling request, wherein the calling chain information comprises calling chain identification type information and application service information, and the application service information comprises application service identification;
optionally, in order to reflect a data model of a communication service operation full view and ensure that an IT service resource tree model for data acquisition, aggregation and final formation can be automatically generated, one or more embodiments of the disclosure select a Zipkin protocol framework as a main framework of the IT service resource tree, and redefine the protocol framework to provide a distributed call chain data model, which relates to a protocol Header field and a call chain log. The related call chain identification class information can use the existing fields of Zipkin, and can comprise traceId, spanId, parentsBand, sampledFlag and debubbFlag values. The description of the fields of the protocol Header is shown in table 1 below:
TABLE 1
Optionally, in the embodiment of the present disclosure, an application service identifier is added to the call chain information, where the application service identifier may uniquely identify the called service, the application service identifier may be provided in the form of a service name, and the service name may be output by the original system. The service name and the region where the file name of the uploaded message can be reflected can be used for obtaining which province system realizes the current service. Therefore, the method can form effective monitoring on end-to-end service flow scenes crossing the groups and the provinces.
Step S106: generating new call chain information, and recording the new call chain information in the call request to obtain an updated call request;
optionally, the current node acquires the traceId, the spanId, the parentSpanId, the sampledFlag, and the debugFlag value sent by the upstream node, and generates a new spanId. Then writing the current traceId, spanId, parentSpanid, sampledFlag and debugFlag at the forefront of route _ record, and transmitting to the next node.
Step S108: and sending the updated calling request to a receiver.
And the receiver is the next node of the current node in the distributed calling link.
According to the distributed calling method, the calling chain information is transmitted in the whole link of distributed calling, and the calling chain information has the calling identification type information and the application service identification, so that a receiving party can effectively monitor an end-to-end business flow scene which is across groups and provinces according to the calling identification type information and the application service identification.
In one or more embodiments of the present disclosure, the application service information may further include:
service port number. For example, a port may be added to the message as a field of a service port number. Based on this, the receiving side can know the order currently logged, the process for processing the order, the service for receiving the order, and the area to which the host belongs, that is, the area to which the service belongs, and which process of which host falls in which area, through the IP address and the port.
In one or more embodiments of the present disclosure, the application service identification may include:
and uniformly coding the whole network and applying the service name. Alternatively, a unified format of "systematic code, service name" may be used as the application service identifier, wherein the systematic code may be a network-wide unified code, such as a telecommunication network-wide unified code. The service name can be output by the original system. The service name and the file name of the uploaded message can reflect the region, so that the system for realizing the current service and the province of the system can be obtained, namely the service is realized by which system of which province.
In one or more embodiments of the present disclosure, to support concatenation in a service chain manner, some special KEY values are additionally defined in the application extension information to define different service fields. Based on this, the call chain information may further include: at least one of the following traffic fields:
the service serial number, the type of the current node in the service invocation link, and the address of the invoked service.
Optionally, KEY names of the service fields may be respectively represented as bc.id, bc.type, and bc.url, where bc.id is a service field shared by upstream and downstream systems in a certain service scenario, and current order information may be uniquely identified by the field, for example, a sessionid field in a group recharging scenario may uniquely identify a current recharging order; and bc.type is the node type of the link in the service call link, the value of bc.type can be c or s, c represents client service, and s represents server service. URL is a service address, is used for identifying a specific address of a called service, requires that a calling party and a called party fill in strictly consistent, is described in a URL style, and is an address of the current service when bc.type is s; type ═ c, the peer service address is used.
Based on the bc.url, bc.id and bc.type, when the original system cannot be modified (i.e. traceId cannot be transmitted to the next link), the data in the relevant system database can be read by the plug-in program, and log output is performed according to the defined bc.url, bc.id and bc.type, so as to realize the association between the upstream and downstream system services.
In one or more embodiments of the present disclosure, different service fields (with different KEY values) are also defined for different scenarios, and based on the call chain information, the method may further include: at least one of the following traffic fields:
the system comprises a service scene code, a service order number, a service number, order generation time, order completion time, order state and a service return result code. The service scene code represents the scene of the service, the KEY name of the service scene code is bz. scenario code, and if the 4G service new installation is started, the service scene code is 10111010001; the service order number is used for associating the call chain data with the service data. For example, when abnormal orders, overtime orders and other conditions occur, more detailed service information can be obtained by searching in a database or a service system through bz. Service number, used to identify service type, KEY name is bz.servNo; the order generation time is used for representing the generation time of a customer order, and the KEY name is bz. Order completion time is used for representing the completion time of a customer order, and the name of KEY is bz. The order state is used for representing the state of a customer order, and the KEY name is bz. The service return result code is used for representing a service processing result, wherein success is represented when the value is 0, timeout is represented when the value is 1, and error reporting is represented by other values.
In one or more embodiments of the present disclosure, the call chain information may further include: at least one of the following traffic fields:
the method comprises the steps of persistent address, network card physical address corresponding to Internet Protocol (IP) address in a network service endpoint, program error identification and error type.
The persistent address is used for representing an address of data stored in a hard disk, and the KEY name is bz. The KEY name of the network card physical address corresponding to the IP address in the network service endpoint (endpoint) is env.mac; the program error identifier is used for identifying when an error occurs and error content description, and the KEY is named bz. The error type is used to indicate the type of error that occurred, and the KEY name is bz.
In one or more embodiments of the present disclosure, the call chain information may further include: at least one of the following traffic fields:
a domain portion of a URL or host header, an HTTP method or verb, an absolute HTTP path, a URL address, an HTTP status code, a request message body size, and a response body message body size.
Wherein, the URL or KEY of the domain part of the host header can be expressed as http.host; KEY for HTTP methods or verbs may be denoted http.method; KEY for absolute HTTP path may be denoted HTTP. The URL address may represent the entire URL address, including the scheme, host and query parameters, and the KEY may be denoted http. KEY of HTTP status code may be denoted HTTP. KEY for the body size of the request message may be denoted http. KEY for the response body message body size may be expressed as http.
In one or more embodiments of the present disclosure, the call chain information may further include: at least one of the following traffic fields:
client address in network call, server address in network call, and internal call.
The client address in the network call may include a port and/or a URL, and the KEY may be denoted as ca; the server address in the network call may also include a port and/or a URL, etc., and KEY may be denoted as sa; internal calls are used to denote internal calls (no access to external services or components via IP, port), and KEY may be denoted as lc.
As shown in fig. 2, by applying the distributed calling method according to the embodiment of the present disclosure, the total network service IT fault location time can be shortened from more than 30 minutes to less than 3 minutes; as shown in fig. 3, the order flow may implement second-level tracing. Therefore, the distributed calling method of the embodiment of the disclosure improves the monitoring capability of the IT whole network, shortens troubleshooting time, and improves customer perception.
Optionally, the call chain log involved in the distributed call chain data model may be as shown in table 2 below:
TABLE 2
The embodiment of the disclosure expands the Zipkin log protocol to form an improved call chain data model. Fig. 4 is a schematic diagram of a call chain data model according to an embodiment of the present disclosure.
Where part 1 shown in fig. 4 is call chain identification class information. The part of the content can directly follow the Zipkin original field.
the definition of service name is standardized, and the unified format of 'system code and service name' is used, wherein the system code is the unified code of telecommunication network, and the service name can be output by the original system. The system name and the area represented by the file name of the uploaded message can be used for acquiring which province system realizes the current service.
Adding a port as a service port number. From the IP address and port, it can be known which order is currently logged, and which process of which host is handling the service that accepts the order in which area.
different service fields are defined for different service scenarios (with different key values), such as: the order number in the original system (which may change continuously in the process of flowing through different systems), the user number, the acceptance channel and the like are increased.
To support concatenation in a chain-of-service fashion, special key values are defined, such as bc.url, bc.id, bc.type, as described above.
According to bc.url, bc.id and bc.type, when the original system can not be modified, the data in the related system database can be read by the plug-in program, and the log is output according to the call chain data model shown in fig. 4.
The traffic fields referred to above are explained below by the following table 3. In table 3 below, the KEY name is a KEY name of the service field, the KEY description describes a meaning represented by the service field, and the filling requirement describes a filling requirement of each link of the distributed call on the service field.
TABLE 3
It should be noted that, as the KEY value of the newly added service field referred to in table 3 above, formal issuing may be performed in the whole network after definition, so as to uniformly collect the apertures in the whole network.
Fig. 5 is a flowchart of a distributed invocation method according to one or more embodiments of the present disclosure, where the method involves nodes including an external system 512, an SGW (Serving GateWay) 514, an SR (Service Router) 516, an internal application 518, and an external system 520, and as shown in fig. 5, the method includes:
the SR reads the traceId, the spanId, the parentSpanid, the sampledFlag and the debugbFlag values transmitted by the upstream link from the SGW application, and generates new spanIds at 1 and 2 in the figure. At 2, the current traceId, spanId, parentsspanid, sampledFlag and debugFlag are written at the head of route _ record and transmitted to the next link (i.e. SR). 1. And 2, after the call is completed, two logs, namely a server _ receive log (server _ receive) log, a server _ send log, a client _ send log (client _ receive) log and a client _ receive log (client _ send) log, are respectively output, and the reference is as follows:
sr, ss logs (server _ receive, server _ send) of the SGW;
where sr denotes the time when the external system request is received, and ss denotes the time when the external system replies. sr, ss are output in the same log, while bins are populated with bz. filling. session id (an example of bc. id above), as follows:
wherein, Timestamp is in Timestamp format and refers to message arrival time, and Duration is in Timestamp format and refers to message sending time-message arrival time.
Cs, cr logs (client _ send, client _ receive) of the SGW;
cs denotes the time when the SGW accesses the SR, and cr denotes the time when the SR replies to the SGW. cs and cr are output in the same log, and bz.Billing.sessionId is filled in the binary indications, and bz.Billing.route _ record is also required to be filled in to represent subsequent links, for example:
if the end-part calls the external system, the log is also required to be output (3 and 4 in fig. 2). At 3 in fig. 5, the SR received call gets traceId, spanId, parentSpanId, sampledFlag, debugFlag from route _ record, and generates a new spanId. And 4, generating a new spanId, and transmitting five fields of traceId, spanId, parentSpaniD, sampledFlag and debugbFlag to the next link. 3. And 4, after the method is called, respectively spitting two logs of server _ receive, server _ send, client _ send and client _ receive, and referring to the following steps:
sr (server _ receive), ss (server _ send log) of other charging network elements, wherein sr represents the moment when the last link is accessed by the previous link, and ss represents the moment when the last link returns to the previous link. sr, ss are output in the same log, and simultaneously bz. filling. session id is filled in bins, as follows:
cs (client _ send), cr (client _ receive) logs of other charging network elements, cs representing the moment of accessing the external system, and cr representing the moment of replying from the external system. cs and cr are output in the same log, and bz.Billing.sessionId is filled in the binary indications, and bz.Billing.route _ record is also required to be filled in to represent subsequent links, for example:
fig. 6 is a schematic structural diagram of a distributed call apparatus according to one or more embodiments of the present disclosure, and as shown in fig. 6, the apparatus 610 includes:
a first obtaining module 612, configured to obtain a call request initiated by a requestor;
a second obtaining module 614, configured to obtain call chain information from the call request, where the call chain information includes call chain identifier information and application service information, and the application service information includes an application service identifier;
a generating module 616, configured to generate new call chain information, record the new call chain information in the call request, and obtain an updated call request;
a sending module 618, configured to send the updated invocation request to the receiving party.
One or more embodiments of the present disclosure also provide an electronic device including: a processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to execute any one of the distributed calling methods provided by the embodiments of the present disclosure via execution of the executable instructions.
One or more embodiments of the present disclosure also provide a computer-readable storage medium on which a computer program is stored, the computer program, when executed by a processor, implementing any one of the distributed calling methods provided by the embodiments of the present disclosure.
An electronic device 700 according to this embodiment of the disclosure is described below with reference to fig. 7. The electronic device 700 shown in fig. 7 is only an example and should not bring any limitation to the functions and the scope of use of the embodiments of the present disclosure.
As shown in fig. 7, electronic device 700 is embodied in the form of a general purpose computing device. The components of the electronic device 700 may include, but are not limited to: the at least one processing unit 710, the at least one memory unit 720, and a bus 730 that couples various system components including the memory unit 720 and the processing unit 710.
Wherein the storage unit stores program code that is executable by the processing unit 710 to cause the processing unit 710 to perform steps according to various exemplary embodiments of the present disclosure as described in the above section "exemplary methods" of this specification. For example, the processing unit 710 may execute step S102 as shown in fig. 1: acquiring a call request initiated by a requester; step S104: acquiring calling chain information from the calling request, wherein the calling chain information comprises calling chain identification type information and application service information, and the application service information comprises application service identification; step S106: generating new call chain information, and recording the new call chain information in the call request to obtain an updated call request; step S108: and sending the updated calling request to a receiver.
The storage unit 720 may include readable media in the form of volatile memory units, such as a random access memory unit (RAM)7201 and/or a cache memory unit 7202, and may further include a read only memory unit (ROM) 7203.
The storage unit 720 may also include a program/utility 7204 having a set (at least one) of program modules 7205, such program modules 7205 including, but not limited to: an operating system, one or more application programs, other program modules, and program data, each of which, or some combination thereof, may comprise an implementation of a network environment.
The electronic device 700 may also communicate with one or more external devices 800 (e.g., keyboard, pointing device, bluetooth device, etc.), with one or more devices that enable a user to interact with the electronic device 700, and/or with any devices (e.g., router, modem, etc.) that enable the electronic device 700 to communicate with one or more other computing devices. Such communication may occur via an input/output (I/O) interface 750. Also, the electronic device 700 may communicate with one or more networks (e.g., a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network such as the internet) via the network adapter 760. As shown, the network adapter 760 communicates with the other modules of the electronic device 700 via the bus 730. It should be appreciated that although not shown in the figures, other hardware and/or software modules may be used in conjunction with the electronic device 700, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, among others.
In an exemplary embodiment of the present disclosure, there is also provided a computer-readable storage medium having stored thereon a program product capable of implementing the above-described method of the present specification. In some possible embodiments, various aspects of the disclosure may also be implemented in the form of a program product comprising program code for causing a terminal device to perform the steps according to various exemplary embodiments of the disclosure described in the "exemplary methods" section above of this specification, when the program product is run on the terminal device.
A program product for implementing the above method according to an embodiment of the present disclosure is described, which may employ a portable compact disc read only memory (CD-ROM) and include program code, and may be run on a terminal device, such as a personal computer. However, the program product of the present disclosure is not limited thereto, and in this document, a readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
The program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a 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 disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
A computer readable signal medium may include a propagated data signal with readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A readable signal medium may also be any readable medium that is not a readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
Program code embodied on a readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Program code for carrying out operations for the present disclosure may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device and partly on a remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., through the internet using an internet service provider).
It should be noted that although in the above detailed description several modules or units of the device for action execution are mentioned, such a division is not mandatory. Indeed, the features and functionality of two or more modules or units described above may be embodied in one module or unit, according to embodiments of the present disclosure. Conversely, the features and functions of one module or unit described above may be further divided into embodiments by a plurality of modules or units.
Moreover, although the steps of the methods of the present disclosure are depicted in the drawings in a particular order, this does not require or imply that the steps must be performed in this particular order, or that all of the depicted steps must be performed, to achieve desirable results. Additionally or alternatively, certain steps may be omitted, multiple steps combined into one step execution, and/or one step broken down into multiple step executions, etc.
Through the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein may be implemented by software, or by software in combination with necessary hardware. Therefore, the technical solution according to the embodiments of the present disclosure may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (which may be a CD-ROM, a usb disk, a removable hard disk, etc.) or on a network, and includes several instructions to enable a computing device (which may be a personal computer, a server, a mobile terminal, or a network device, etc.) to execute the method according to the embodiments of the present disclosure.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This application is intended to cover any variations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
Claims (11)
1. A distributed call method, comprising:
acquiring a call request initiated by a requester;
acquiring calling chain information from the calling request, wherein the calling chain information comprises calling chain identification type information and application service information, and the application service information comprises application service identification;
generating new call chain information, and recording the new call chain information in the call request to obtain an updated call request;
and sending the updated calling request to a receiver.
2. The distributed call method of claim 1, the application service information further comprising:
service port number.
3. The distributed invocation method according to claim 1, wherein the application service identification comprises:
and uniformly coding the whole network and applying the service name.
4. The distributed calling method according to claim 1, wherein the call chain information further comprises:
at least one of the following traffic fields:
the service serial number, the type of the current node in the service invocation link, and the address of the invoked service.
5. The distributed calling method according to claim 1, wherein the call chain information further comprises:
at least one of the following traffic fields:
the system comprises a service scene code, a service order number, a service number, order generation time, order completion time, order state and a service return result code.
6. The distributed calling method according to claim 1, wherein the call chain information further comprises:
at least one of the following traffic fields:
the method comprises the steps of persistent address, network card physical address corresponding to Internet Protocol (IP) address in a network service endpoint, program error identification and error type.
7. The distributed calling method according to claim 1, wherein the call chain information further comprises:
at least one of the following traffic fields:
a domain portion of a Uniform Resource Locator (URL) or host header, a hypertext transfer protocol (HTTP) method or verb, an absolute HTTP path, a URL address, an HTTP status code, a request body size, and a response body size.
8. The distributed calling method according to any one of claims 1 to 7, wherein the calling chain information further includes:
at least one of the following traffic fields:
client address in network call, server address in network call, and internal call.
9. A distributed call apparatus, comprising:
the first acquisition module is used for acquiring a call request initiated by a requester;
a second obtaining module, configured to obtain call chain information from the call request, where the call chain information includes call chain identifier information and application service information, and the application service information includes an application service identifier;
the generation module is used for generating new calling chain information and recording the new calling chain information in the calling request to obtain an updated calling request;
and the sending module is used for sending the updated calling request to the receiving party.
10. An electronic device, comprising:
a processor; and
a memory for storing executable instructions of the processor;
wherein the processor is configured to execute the distributed call method of any of claims 1-8 via execution of the executable instructions.
11. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, implements the distributed call method according to any one of claims 1 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111608274.5A CN114301988A (en) | 2021-12-22 | 2021-12-22 | Distributed calling method and device, storage medium and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111608274.5A CN114301988A (en) | 2021-12-22 | 2021-12-22 | Distributed calling method and device, storage medium and electronic equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114301988A true CN114301988A (en) | 2022-04-08 |
Family
ID=80970003
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111608274.5A Pending CN114301988A (en) | 2021-12-22 | 2021-12-22 | Distributed calling method and device, storage medium and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114301988A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114938387A (en) * | 2022-07-22 | 2022-08-23 | 浙江中控技术股份有限公司 | Data transmission method, device, system and storage medium |
| WO2024002232A1 (en) * | 2022-07-01 | 2024-01-04 | 中兴通讯股份有限公司 | Data processing method, apparatus and system, edge server, electronic device, and storage medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104219316A (en) * | 2014-09-12 | 2014-12-17 | 微梦创科网络科技（中国）有限公司 | Method and device for processing call request in distributed system |
| CN108173915A (en) * | 2017-12-21 | 2018-06-15 | 中国联合网络通信集团有限公司 | Call chain processing method and processing device |
| CN110708212A (en) * | 2019-09-10 | 2020-01-17 | 中国平安财产保险股份有限公司 | Method and device for tracking call link in distributed system |
| CN112363855A (en) * | 2020-11-13 | 2021-02-12 | 北京基调网络股份有限公司 | Call chain data generation method, topology generation method and system and computer equipment |
| CN112905353A (en) * | 2019-11-19 | 2021-06-04 | 中国电信股份有限公司 | Service calling information generation method and device and storage medium |
-
2021
- 2021-12-22 CN CN202111608274.5A patent/CN114301988A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104219316A (en) * | 2014-09-12 | 2014-12-17 | 微梦创科网络科技（中国）有限公司 | Method and device for processing call request in distributed system |
| CN108173915A (en) * | 2017-12-21 | 2018-06-15 | 中国联合网络通信集团有限公司 | Call chain processing method and processing device |
| CN110708212A (en) * | 2019-09-10 | 2020-01-17 | 中国平安财产保险股份有限公司 | Method and device for tracking call link in distributed system |
| CN112905353A (en) * | 2019-11-19 | 2021-06-04 | 中国电信股份有限公司 | Service calling information generation method and device and storage medium |
| CN112363855A (en) * | 2020-11-13 | 2021-02-12 | 北京基调网络股份有限公司 | Call chain data generation method, topology generation method and system and computer equipment |
Non-Patent Citations (1)
| Title |
|---|
| 熊游泳，庾玲: "基于分布式跟踪的业务调用链监控技术在湖南电信的探索和应用", 电脑知识与技术, 30 November 2020 (2020-11-30), pages 4 * |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2024002232A1 (en) * | 2022-07-01 | 2024-01-04 | 中兴通讯股份有限公司 | Data processing method, apparatus and system, edge server, electronic device, and storage medium |
| CN114938387A (en) * | 2022-07-22 | 2022-08-23 | 浙江中控技术股份有限公司 | Data transmission method, device, system and storage medium |
| CN114938387B (en) * | 2022-07-22 | 2022-11-11 | 浙江中控技术股份有限公司 | Data transmission method, device, system and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7099879B2 (en) | Real-time monitoring of service performance through the use of relational database calculation clusters | |
| US8099488B2 (en) | Real-time monitoring of service agreements | |
| US20030212778A1 (en) | UML representation of parameter calculation expressions for service monitoring | |
| CN110351283B (en) | Data transmission method, device, equipment and storage medium | |
| EP2240854B1 (en) | Method of resolving network address to host names in network flows for network device | |
| US9717011B2 (en) | Event management in telecommunications networks | |
| CN114301988A (en) | Distributed calling method and device, storage medium and electronic equipment | |
| CN112822276B (en) | Substation control layer communication method and system, electronic equipment and storage medium | |
| CN101494551A (en) | Method, apparatus and system for business cutover | |
| CN112751772B (en) | Data transmission method and system | |
| US20200042424A1 (en) | Method, apparatus and system for processing log data | |
| CN110162512A (en) | A kind of log searching method, apparatus and storage medium | |
| EA019680B1 (en) | Service access method and system | |
| CN112817539A (en) | Industrial data storage method and system, electronic device and storage medium | |
| CN103944779B (en) | A kind of WAP service features monitoring method and system | |
| CN111026566A (en) | Client service error scene three-dimensional monitoring method and device | |
| WO2022111356A1 (en) | Data migration method and system, and server and storage medium | |
| CN114124859B (en) | Intelligent customer service robot of network maintenance platform and maintenance method | |
| CN115913912A (en) | Message interception and service link diagram generation method and device | |
| CN110233747B (en) | Data reporting method and cloud platform | |
| CN102263796B (en) | Data transmission method based on simple network management protocol | |
| CN117615043B (en) | Inter-service communication method and system on edge gateway | |
| CN105763380A (en) | Network management data obtaining method and device | |
| EP1540886B1 (en) | Command processing in a telecommunications network | |
| CN117749611A (en) | Multiparty network integrated management method, system, terminal and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |