CN113434135B - Method and device for determining call repeatability of interface, storage medium and electronic device - Google Patents
Method and device for determining call repeatability of interface, storage medium and electronic device Download PDFInfo
- Publication number
- CN113434135B CN113434135B CN202110723409.6A CN202110723409A CN113434135B CN 113434135 B CN113434135 B CN 113434135B CN 202110723409 A CN202110723409 A CN 202110723409A CN 113434135 B CN113434135 B CN 113434135B
- Authority
- CN
- China
- Prior art keywords
- target
- log
- interface
- call
- determining
- 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.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/36—Software reuse
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/362—Software debugging
- G06F11/3636—Software debugging by tracing the execution of the program
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/448—Execution paradigms, e.g. implementations of programming paradigms
- G06F9/4488—Object-oriented
- G06F9/449—Object-oriented method invocation or resolution
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Telephonic Communication Services (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention discloses a method and a device for determining call repeatability of an interface, a storage medium and an electronic device, wherein the method comprises the following steps: acquiring a target chained log of a target dimension from the chained log of the service; acquiring the number of target logs of a target interface and the target traffic corresponding to the logs of the target interface from the target chained log; and determining target calling repeatability corresponding to the target interface under the target dimension according to the target log quantity and the target traffic. By adopting the technical scheme, the problems of low accuracy of determining the calling repeatability of the interface and the like in the related technology are solved.
Description
Technical Field
The present invention relates to the field of communications, and in particular, to a method and apparatus for determining call repeatability of an interface, a storage medium, and an electronic device.
Background
In the current internet of things technology, network resources need to be scientifically deployed according to the running process of the internet of things system, for example: taking the interface resource in the internet of things system as an example, the deployment position of the interface, the deployment parameters of the interface and the like are required to be adjusted according to the use condition of the interface, however, in the current use process of the interface, the repetition degree of the interface call cannot be accurately measured, which results in the lack of an important reference index when the interface resource is allocated or allocated.
Aiming at the problems of low accuracy of determining the call repeatability of the interface and the like in the related technology, no effective solution has been proposed yet.
Disclosure of Invention
The embodiment of the invention provides a method and a device for determining call repeatability of an interface, a storage medium and an electronic device, which are used for at least solving the problems of low accuracy of determining the call repeatability of the interface and the like in the related technology.
According to an embodiment of the present invention, there is provided a call repetition degree determining method of an interface, including: acquiring a target chained log of a target dimension from the chained log of the service; acquiring the number of target logs of a target interface and the target traffic corresponding to the logs of the target interface from the target chained log; and determining target calling repeatability corresponding to the target interface under the target dimension according to the target log quantity and the target traffic.
In an exemplary embodiment, obtaining, from the target chained log, a target log number of a target interface and a target traffic corresponding to the log of the target interface, including: determining the number of the target logs according to the number of the buried point logs of the target interface included in the target chained log; and determining the target traffic according to the traffic identifier corresponding to the buried point log of the target interface included in the target chained log.
In an exemplary embodiment, determining the target log number according to the number of buried point logs of the target interface included in the target chained log includes: extracting a buried point log from the logs included in the target chained log to obtain an initial buried point log set; extracting a buried point log carrying the interface name of the target interface from the initial buried point log set to obtain a target buried point log set; and determining the number of the buried point logs included in the target buried point log set to obtain the target log number.
In an exemplary embodiment, determining the target traffic according to the traffic identifier corresponding to the buried point log of the target interface included in the target chained log includes: extracting service identifiers from the buried point logs of the target interfaces to obtain an initial service identifier list; performing de-duplication operation on the initial service identification list to obtain a target service identification list; and determining the number of service identifiers included in the target service identifier list to obtain the target service volume.
In one exemplary embodiment, a target chained log of target dimensions is obtained from a chained log of traffic, including one of: acquiring a chained log of a target time period from the recorded chained log as the target chained log; and acquiring the chained log with the included traffic as the target traffic from the recorded chained log as the target chained log.
In an exemplary embodiment, after determining a target call repetition degree corresponding to the target interface in the target dimension according to the target log number and the target traffic, the method further includes at least one of: distributing network resources for the target interface according to the target call repeatability; deploying an interface algorithm for the target interface according to the target call repeatability; and adjusting the call structure of the target interface according to the target call repeatability.
In one exemplary embodiment, allocating network resources for the target interface according to the target call repetition degree includes: increasing a target number of network resources for the target interface if the target call repetition exceeds a first threshold; deploying an interface algorithm for the target interface according to the target call repetition degree comprises: under the condition that the target calling repeatability exceeds a second threshold, deploying an interface algorithm with computing power exceeding a target computing power for the target interface; the adjusting the call structure of the target interface according to the target call repeatability comprises the following steps: and under the condition that the target calling repeatability exceeds a third threshold value, the target interface is adjusted from the first calling position where the target interface is currently positioned to a second calling position with the bearing capacity smaller than the target bearing capacity.
According to another embodiment of the present invention, there is also provided an interface call repetition degree determining apparatus, including: the first acquisition module is used for acquiring a target chained log of a target dimension from the chained log of the service; the second acquisition module is used for acquiring the target log quantity of the target interface and the target traffic corresponding to the log of the target interface from the target chained log; and the determining module is used for determining the target call repeatability corresponding to the target interface under the target dimension according to the target log quantity and the target traffic.
According to yet another aspect of the embodiments of the present invention, there is also provided a computer-readable storage medium having a computer program stored therein, wherein the computer program is configured to perform the call repetition determination method of the above interface when run.
According to still another aspect of the embodiments of the present invention, there is further provided an electronic device including a memory, a processor, and a computer program stored on the memory and executable on the processor, wherein the processor executes the method for determining the call repetition degree of the interface through the computer program.
In the embodiment of the invention, a target chained log of a target dimension is obtained from chained logs of a service; acquiring the number of target logs of a target interface and the target traffic corresponding to the logs of the target interface from the target chained log; and determining the target call repeatability of the target interface under the target dimension according to the number of the target logs and the target traffic, namely extracting parameters such as the number of the target logs and the target traffic of the target interface needing to determine the call repeatability from the target logs based on a chained tracking principle by utilizing the chained logs of the service records, and performing operation by using the extracted parameters so as to accurately determine the call repeatability of the interface. By adopting the technical scheme, the problems of low accuracy of determining the calling repeatability of the interface and the like in the related technology are solved, and the technical effect of improving the accuracy of determining the calling repeatability of the interface is realized.
Drawings
The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and together with the description serve to explain the invention and do not constitute a limitation on the invention. In the drawings:
FIG. 1 is a block diagram of the hardware architecture of a computer terminal of an interface call repetition determination method according to an embodiment of the present invention;
FIG. 2 is a flow chart of a call repetition determination method of an interface according to an embodiment of the invention;
FIG. 3 is a schematic diagram of a call repetition determination method of an interface according to an embodiment of the invention;
fig. 4 is a block diagram of a call repetition degree determining apparatus of an interface according to an embodiment of the present invention.
Detailed Description
In order that those skilled in the art will better understand the present invention, a technical solution in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in which it is apparent that the described embodiments are only some embodiments of the present invention, not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the present invention without making any inventive effort, shall fall within the scope of the present invention.
It should be noted that the terms "first," "second," and the like in the description and the claims of the present invention and the above figures are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments of the invention described herein may be implemented in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
The method embodiments provided by the embodiments of the present invention may be performed in a computer terminal, or a similar computing device. Taking a computer terminal as an example, fig. 1 is a block diagram of a hardware structure of a computer terminal of an interface call repetition degree determining method according to an embodiment of the present invention. As shown in fig. 1, the computer terminal may include one or more (only one is shown in fig. 1) processors 102 (the processor 102 may include, but is not limited to, a microprocessor MCU or a processing device such as a programmable logic device FPGA) and a memory 104 for storing data, and in one exemplary embodiment, may also include a transmission device 106 for communication functions and an input-output device 108. It will be appreciated by those skilled in the art that the configuration shown in fig. 1 is merely illustrative and is not intended to limit the configuration of the computer terminal described above. For example, a computer terminal may also include more or fewer components than shown in FIG. 1, or have a different configuration than the equivalent functions shown in FIG. 1 or more than the functions shown in FIG. 1.
The memory 104 may be used to store a computer program, for example, a software program of application software and a module, such as a computer program corresponding to a call repetition rate determining method of an interface in an embodiment of the present invention, and the processor 102 executes the computer program stored in the memory 104 to perform various functional applications and data processing, that is, implement the above-mentioned method. Memory 104 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 104 may further include memory remotely located relative to the processor 102, which may be connected to the computer terminal via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The transmission means 106 is arranged to receive or transmit data via a network. Specific examples of the network described above may include a wireless network provided by a communication provider of a computer terminal. In one example, the transmission device 106 includes a network adapter (Network Interface Controller, simply referred to as NIC) that can connect to other network devices through a base station to communicate with the internet. In one example, the transmission device 106 may be a Radio Frequency (RF) module, which is used to communicate with the internet wirelessly.
In this embodiment, a method for determining call repetition of an interface is provided, which is applied to the computer terminal, and fig. 2 is a flowchart of the method for determining call repetition of an interface according to an embodiment of the present invention, where the flowchart includes the following steps:
step S202, obtaining a target chained log of a target dimension from chained logs of a service;
step S204, obtaining the target log quantity of a target interface and the target traffic corresponding to the log of the target interface from the target chained log;
step S206, determining the target calling repeatability corresponding to the target interface under the target dimension according to the target log quantity and the target traffic.
Through the steps, a target chained log of a target dimension is obtained from the chained log of the service; acquiring the number of target logs of a target interface and the target traffic corresponding to the logs of the target interface from the target chained log; and determining the target call repeatability corresponding to the target interface under the target dimension according to the target log quantity and the target traffic, namely extracting parameters such as the target log quantity and the target traffic of the target interface needing to determine the call repeatability from the target log quantity and the target traffic of the target interface based on a chained tracking principle by utilizing the chained log of the service record, and performing operation by using the extracted parameters, so that the call repeatability of the interface is accurately determined. By adopting the technical scheme, the problems of low accuracy of determining the calling repeatability of the interface and the like in the related technology are solved, and the technical effect of improving the accuracy of determining the calling repeatability of the interface is realized.
In the technical solution provided in step S202, a chained log of the service is submitted to record the processing procedure of the service during the processing procedure of the service. The system of the chained log can measure the end-to-end path of a business, and the identification of the business interface in the chained log system can be used for knowing the accurate times of interface calling under the critical path, so that the repeated calling degree of the business interface is effectively calculated.
Optionally, in this embodiment, the target dimension may be determined, but not limited to, according to an actual requirement, or various dimensions that need to determine the call repeatability of the interface may be preset as the target dimension, so that the system may automatically perform the operation of determining the call repeatability of the interface when the target dimension condition is satisfied.
Alternatively, in the present embodiment, the target dimension may include, but is not limited to: time dimension, traffic dimension, etc.
In one exemplary embodiment, the target chained log of target dimensions may be obtained from the chained log of traffic by, but is not limited to, one of the following:
in one mode, a chained log of a target time period is obtained from the recorded chained log and used as the target chained log.
Alternatively, in the present embodiment, the target period may include, but is not limited to: one day, one hour, one month, one year, N days, M years, P months, etc. Alternatively, the start time and the end time of the target period may be set, for example: the target time period may be, but is not limited to, from 2021, 1, 9, to 2021, 4, 3, 18, etc.
Alternatively, in the present embodiment, a chained log whose recording time falls within a target period may be determined as the target chained log from the recording time of the chained log, but is not limited to.
And secondly, acquiring a chained log with the included traffic as the target traffic from the recorded chained log as the target chained log.
Alternatively, in this embodiment, the target traffic may be, but not limited to, a traffic number indicating that the call repetition of the interface needs to be determined, for example: the target traffic may be, but is not limited to, 10000 traffic, 100 traffic, 5000 traffic, etc.
In the solution provided in the above step S204, whether the target interface is used may be, but is not limited to, counted by a log of whether the log contains the interface.
Optionally, in this embodiment, each service in the chained log is identified by an independent non-repeated serial number, and the service corresponding to the chained log may be determined by, but not limited to, the serial number identification carried by the chained log. Traffic may be counted by, but is not limited to, sequence number identification.
In one exemplary embodiment, the target number of logs of a target interface and the target traffic corresponding to the logs of the target interface may be obtained from the target chained log by, but not limited to: determining the number of the target logs according to the number of the buried point logs of the target interface included in the target chained log; and determining the target traffic according to the traffic identifier corresponding to the buried point log of the target interface included in the target chained log.
Optionally, in this embodiment, in the process of calling an interface, a call of the interface between any two system nodes buries two points at the calling end and the service end, so as to obtain a buries log. The number of embedded point logs of the target interface may represent the number of times the target interface is invoked.
Optionally, in this embodiment, the embedded point log of the target interface records an identifier of a corresponding service, and according to whether the chained log is the embedded point log of the target interface, the embedded point log of the target interface may be obtained from the chained log, so as to determine the number of the embedded point logs of the target interface, and according to the service identifier corresponding to the embedded point log of the target interface, the target traffic may be determined.
In one exemplary embodiment, the target log number may be determined from the number of buried point logs of the target interface included in the target chained log by, but not limited to: extracting a buried point log from the logs included in the target chained log to obtain an initial buried point log set; extracting a buried point log carrying the interface name of the target interface from the initial buried point log set to obtain a target buried point log set; and determining the number of the buried point logs included in the target buried point log set to obtain the target log number.
Optionally, in this embodiment, the initial embedded point log set includes a log in which the interface call embedded point is recorded in the target chained log.
Optionally, in this embodiment, the names of the interfaces corresponding to the burial points of the same calling end and the service end are the same, and the burial point log carrying the interface name of the target interface is obtained from the burial point log as a target burial point log set, where the number of the burial point logs included in the target burial point log set is the target log number.
In one exemplary embodiment, the target traffic may be determined, but is not limited to, according to a traffic identifier corresponding to a buried point log of the target interface included in the target chained log by: extracting service identifiers from the buried point logs of the target interfaces to obtain an initial service identifier list; performing de-duplication operation on the initial service identification list to obtain a target service identification list; and determining the number of service identifiers included in the target service identifier list to obtain the target service volume.
Alternatively, in this embodiment, the service identifier may be, but is not limited to, a uTraceId carried in a log.
Optionally, in this embodiment, the uTraceId is extracted from the buried point log of the target interface to obtain an initial uTraceId list, performing a uTraceId deduplication operation on the initial uTraceId list to obtain a target uTraceId list, and determining the number of the utraceids included in the target uTraceId list to obtain the target traffic.
In the technical solution provided in step S206, the calling repeatability of the interface may represent the number of times that an interface is repeatedly called, the calling repeatability of the interface may be calculated to determine the degree to which the interface is called, and the degree to which the interface is accurately calculated to repeatedly call may be used to ensure scientific consideration and matching on the algorithm performance and physical resource investment of the critical path, so as to ensure the reliability and stability of the overall system.
Alternatively, in this embodiment, the ratio between the log number and the service number may be determined, but is not limited to, as the target call repeatability corresponding to the target interface in the target dimension. Alternatively, but not limited to, the ratio between the number of services and the number of logs may be determined as the target call repeatability corresponding to the target interface in the target dimension.
In an exemplary embodiment, after the step S206, the system resource may be further processed with the obtained target call repetition degree through at least one of the following operations, but not limited to:
and firstly, distributing network resources for the target interface according to the target call repeatability.
Optionally, in this embodiment, in a case where the target call repetition degree exceeds a first threshold, a target number of network resources is added to the target interface.
Optionally, in this embodiment, if the call repetition degree of the target interface exceeds the first threshold, it may indicate that the call of the target interface is more frequent, and more network resources may be allocated to support the call of the target interface.
And secondly, deploying an interface algorithm for the target interface according to the target call repeatability.
Optionally, in this embodiment, in a case that the target call repetition degree exceeds a second threshold, an interface algorithm with a computing power exceeding a target computing power is deployed for the target interface.
Optionally, in this embodiment, if the call repetition degree of the target interface exceeds the second threshold, it may indicate that the call of the target interface is more frequent, and a higher-power interface algorithm may be deployed for the call of the target interface to support the call of the target interface.
And thirdly, adjusting the call structure of the target interface according to the target call repeatability.
Optionally, in this embodiment, the target interface is adjusted from a first call location where the target interface is currently located to a second call location where the load capacity is smaller than the target load capacity, where the target call repetition degree exceeds a third threshold.
Optionally, in this embodiment, if the call repetition degree of the target interface exceeds the third threshold, it may indicate that the call of the target interface is more frequent, and the call may be adjusted from the first call position with a larger bearing capacity to the second call position with a smaller bearing capacity, so as to ensure that the call position where the target interface is located can provide a higher bearing capacity for the call position where the target interface is located.
In order to better understand the procedure of the call repetition degree determining method of the interface, the following describes the implementation method flow of the call repetition degree determining procedure of the interface with reference to the alternative embodiment, but is not used for limiting the technical scheme of the embodiment of the invention.
In this embodiment, a method for determining call repetition degree of an interface is provided, fig. 3 is a schematic diagram of a process for determining call repetition degree of an interface according to an embodiment of the present invention, and as shown in fig. 3, an interface call process of a service is provided, where the service passes through the following system nodes: APP/Intelligent terminal, UWS open service, public basic service A, public basic service B, public basic service C, data access layer and database (including DB storage, redis cache and MQ server).
In a one-time distributed request link of the service, data transmitted in a network carry a service identifier uTraceId and a calling position identifier uSpanId, one call between any two nodes is carried out, two points are buried at a calling end and a service end respectively, wherein a Client end (CS) represents a buried point when a Client initiates a request, and data transmitted to a lower node are uTraceId and uSpanId. The Server Receiver (SR) represents a buried point when the Server receives the request, acquires the uTraceId and the uspan id transmitted by the request, and puts the uTraceId and the uspan id into the processing context. Server Send (SS) represents the buried point when the Server sends the request processing result to the client. Client Recieve (CR) represents the buried point where the Client receives a server response.
Each class of nodes will have an interface name, which may be denoted as biname. In the log model shown in fig. 3, SS of the same calling end and service end are the same as the biname of the SR burial point, CS of the same calling end and service end are the same as the biname of the CR burial point, and then a certain interface i (such as an interface between APP/intelligent terminal and UWS open service on the APP/intelligent terminal, an interface between APP/intelligent terminal and UWS open service on the UWS open service, an interface between UWS open service and public base service a on the public base service a, an interface between UWS open service and public base service C on the public base service C, an interface between public base service a and public base service B on the public base service B, an interface between public base service B and a data access layer on the public base service B and a data access layer, and a call volume of the data access layer on the public base layer, wherein the call volume is equal to the total call volume (Σi) is not limited to the target volume (Σi) of the total call volume (Σi).
The calling repeatability of the interface determined through the process can be used for solving the algorithm performance index requirement and the physical resource input requirement in the service processing system, so that the stability of the whole system is ensured.
From the description of the above embodiments, it will be clear to a person skilled in the art that the method according to the above embodiments may be implemented by means of software plus the necessary general hardware platform, but of course also by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present invention may be embodied essentially or in a part contributing to the prior art in the form of a software product stored in a storage medium (e.g. ROM/RAM, magnetic disk, optical disk) comprising several instructions for causing a terminal device (which may be a mobile phone, a computer, a server, or a network device, etc.) to perform the method of the various embodiments of the present invention.
FIG. 4 is a block diagram of an interface call repetition determination device according to an embodiment of the invention; as shown in fig. 4, includes:
a first obtaining module 42, configured to obtain a target chained log of a target dimension from chained logs of a service;
a second obtaining module 44, configured to obtain, from the target chained log, a target log number of a target interface and a target traffic corresponding to the log of the target interface;
and the determining module 46 is configured to determine, according to the target log number and the target traffic, a target call repeatability corresponding to the target interface in the target dimension.
Through the embodiment, the target chained log of the target dimension is obtained from the chained log of the service; acquiring the number of target logs of a target interface and the target traffic corresponding to the logs of the target interface from the target chained log; and determining the target call repeatability corresponding to the target interface under the target dimension according to the target log quantity and the target traffic, namely extracting parameters such as the target log quantity and the target traffic of the target interface needing to determine the call repeatability from the target log quantity and the target traffic of the target interface based on a chained tracking principle by utilizing the chained log of the service record, and performing operation by using the extracted parameters, so that the call repeatability of the interface is accurately determined. By adopting the technical scheme, the problems of low accuracy of determining the calling repeatability of the interface and the like in the related technology are solved, and the technical effect of improving the accuracy of determining the calling repeatability of the interface is realized.
Alternatively, in this embodiment, a chained log of the service is submitted to record the processing procedure of the service during the processing procedure of the service. The system of the chained log can measure the end-to-end path of a business, and the identification of the business interface in the chained log system can be used for knowing the accurate times of interface calling under the critical path, so that the repeated calling degree of the business interface is effectively calculated.
Optionally, in this embodiment, the target dimension may be determined, but not limited to, according to an actual requirement, or various dimensions that need to determine the call repeatability of the interface may be preset as the target dimension, so that the system may automatically perform the operation of determining the call repeatability of the interface when the target dimension condition is satisfied.
Alternatively, in the present embodiment, the target dimension may include, but is not limited to: time dimension, traffic dimension, etc.
Optionally, in this embodiment, each service in the chained log is identified by an independent non-repeated serial number, and the service corresponding to the chained log may be determined by, but not limited to, the serial number identification carried by the chained log. Traffic may be counted by, but is not limited to, sequence number identification.
Optionally, in this embodiment, the call repetition degree of the interface may represent the number of times that an interface is repeatedly called, and calculating the call repetition degree of the interface may determine the degree to which the interface is called, and accurately calculates the degree to which the interface is repeatedly called may be used to ensure scientific consideration and matching on algorithm performance and physical resource investment of the critical path, so as to ensure reliability and stability of the overall system.
Alternatively, in this embodiment, the ratio between the log number and the service number may be determined, but is not limited to, as the target call repeatability corresponding to the target interface in the target dimension. Alternatively, but not limited to, the ratio between the number of services and the number of logs may be determined as the target call repeatability corresponding to the target interface in the target dimension.
In an exemplary embodiment, the second acquisition module includes: a first determining unit, configured to determine the number of target logs according to the number of buried point logs of the target interface included in the target chained log; and the second determining unit is used for determining the target traffic volume according to the service identifier corresponding to the buried point log of the target interface included in the target chained log.
Optionally, in this embodiment, in the process of calling an interface, a call of the interface between any two system nodes buries two points at the calling end and the service end, so as to obtain a buries log. The number of embedded point logs of the target interface may represent the number of times the target interface is invoked.
Optionally, in this embodiment, the embedded point log of the target interface records an identifier of a corresponding service, and according to whether the chained log is the embedded point log of the target interface, the embedded point log of the target interface may be obtained from the chained log, so as to determine the number of the embedded point logs of the target interface, and according to the service identifier corresponding to the embedded point log of the target interface, the target traffic may be determined.
In an exemplary embodiment, the first determining unit is further configured to: extracting a buried point log from the logs included in the target chained log to obtain an initial buried point log set; extracting a buried point log carrying the interface name of the target interface from the initial buried point log set to obtain a target buried point log set; and determining the number of the buried point logs included in the target buried point log set to obtain the target log number.
Optionally, in this embodiment, the initial embedded point log set includes a log in which the interface call embedded point is recorded in the target chained log.
Optionally, in this embodiment, the names of the interfaces corresponding to the burial points of the same calling end and the service end are the same, and the burial point log carrying the interface name of the target interface is obtained from the burial point log as a target burial point log set, where the number of the burial point logs included in the target burial point log set is the target log number.
In an exemplary embodiment, the second determining unit is further configured to: extracting service identifiers from the buried point logs of the target interfaces to obtain an initial service identifier list; performing de-duplication operation on the initial service identification list to obtain a target service identification list; and determining the number of service identifiers included in the target service identifier list to obtain the target service volume.
Alternatively, in this embodiment, the service identifier may be, but is not limited to, a uTraceId carried in a log.
Optionally, in this embodiment, the uTraceId is extracted from the buried point log of the target interface to obtain an initial uTraceId list, performing a uTraceId deduplication operation on the initial uTraceId list to obtain a target uTraceId list, and determining the number of the utraceids included in the target uTraceId list to obtain the target traffic.
In an exemplary embodiment, the first acquisition module is further configured to one of: acquiring a chained log of a target time period from the recorded chained log as the target chained log; and acquiring the chained log with the included traffic as the target traffic from the recorded chained log as the target chained log.
Alternatively, in the present embodiment, a chained log whose recording time falls within a target period may be determined as the target chained log from the recording time of the chained log, but is not limited to.
Alternatively, in the present embodiment, the target traffic may be, but not limited to, a traffic number indicating that call repetition of the interface needs to be determined.
In an exemplary embodiment, the apparatus further comprises at least one of: the allocation module is used for allocating network resources for the target interface according to the target call repetition degree after determining the target call repetition degree corresponding to the target interface under the target dimension according to the target log quantity and the target traffic; the deployment module is used for deploying an interface algorithm for the target interface according to the target call repetition degree after determining the target call repetition degree corresponding to the target interface under the target dimension according to the target log quantity and the target traffic; and the adjusting module is used for adjusting the call structure of the target interface according to the target call repeatability after determining the target call repeatability corresponding to the target interface under the target dimension according to the target log quantity and the target traffic.
In an exemplary embodiment, the allocation module is configured to: increasing a target number of network resources for the target interface if the target call repetition exceeds a first threshold; the deployment module is used for: under the condition that the target calling repeatability exceeds a second threshold, deploying an interface algorithm with computing power exceeding a target computing power for the target interface; the adjusting module is used for: and under the condition that the target calling repeatability exceeds a third threshold value, the target interface is adjusted from the first calling position where the target interface is currently positioned to a second calling position with the bearing capacity smaller than the target bearing capacity.
Optionally, in this embodiment, if the call repetition degree of the target interface exceeds the first threshold, it may indicate that the call of the target interface is more frequent, and more network resources may be allocated to support the call of the target interface.
Optionally, in this embodiment, if the call repetition degree of the target interface exceeds the second threshold, it may indicate that the call of the target interface is more frequent, and a higher-power interface algorithm may be deployed for the call of the target interface to support the call of the target interface.
Optionally, in this embodiment, if the call repetition degree of the target interface exceeds the third threshold, it may indicate that the call of the target interface is more frequent, and the call may be adjusted from the first call position with a larger bearing capacity to the second call position with a smaller bearing capacity, so as to ensure that the call position where the target interface is located can provide a higher bearing capacity for the call position where the target interface is located.
An embodiment of the present invention also provides a storage medium including a stored program, wherein the program executes the method of any one of the above.
Alternatively, in the present embodiment, the above-described storage medium may be configured to store program code for performing the steps of:
s1, acquiring a target chained log of a target dimension from chained logs of a service;
s2, acquiring the target log quantity of a target interface and the target traffic corresponding to the log of the target interface from the target chained log;
and S3, determining target call repeatability corresponding to the target interface under the target dimension according to the target log quantity and the target traffic.
An embodiment of the invention also provides an electronic device comprising a memory having stored therein a computer program and a processor arranged to run the computer program to perform the steps of any of the method embodiments described above.
Optionally, the electronic apparatus may further include a transmission device and an input/output device, where the transmission device is connected to the processor, and the input/output device is connected to the processor.
Alternatively, in the present embodiment, the above-described processor may be configured to execute the following steps by a computer program:
s1, acquiring a target chained log of a target dimension from chained logs of a service;
s2, acquiring the target log quantity of a target interface and the target traffic corresponding to the log of the target interface from the target chained log;
and S3, determining target call repeatability corresponding to the target interface under the target dimension according to the target log quantity and the target traffic.
Alternatively, in the present embodiment, the storage medium may include, but is not limited to: a U-disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a removable hard disk, a magnetic disk, or an optical disk, or other various media capable of storing program codes.
Alternatively, specific examples in this embodiment may refer to examples described in the foregoing embodiments and optional implementations, and this embodiment is not described herein.
It will be appreciated by those skilled in the art that the modules or steps of the invention described above may be implemented in a general purpose computing device, they may be concentrated on a single computing device, or distributed across a network of computing devices, they may alternatively be implemented in program code executable by computing devices, so that they may be stored in a memory device for execution by computing devices, and in some cases, the steps shown or described may be performed in a different order than that shown or described, or they may be separately fabricated into individual integrated circuit modules, or multiple modules or steps within them may be fabricated into a single integrated circuit module for implementation. Thus, the present invention is not limited to any specific combination of hardware and software.
The above description is only of the preferred embodiments of the present invention and is not intended to limit the present invention, but various modifications and variations can be made to the present invention by those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the principle of the present invention should be included in the protection scope of the present invention.
Claims (8)
1. A call repetition degree determining method of an interface, comprising:
acquiring a target chained log of a target dimension from the chained log of the service;
acquiring the number of target logs of a target interface and the target traffic corresponding to the logs of the target interface from the target chained log;
determining target calling repeatability corresponding to the target interface under the target dimension according to the target log quantity and the target traffic;
the method for acquiring the target log quantity of the target interface and the target traffic corresponding to the log of the target interface from the target chained log comprises the following steps:
determining the number of the target logs according to the number of the buried point logs of the target interface included in the target chained log;
determining the target traffic according to the traffic identifier corresponding to the buried point log of the target interface included in the target chained log;
the determining the target traffic according to the service identifier corresponding to the buried point log of the target interface included in the target chained log includes:
extracting service identifiers from the buried point logs of the target interfaces to obtain an initial service identifier list;
performing de-duplication operation on the initial service identification list to obtain a target service identification list;
determining the number of service identifiers included in the target service identifier list to obtain the target service volume;
and determining the ratio between the target log quantity and the target traffic volume as the target call repeatability, or determining the ratio between the target traffic volume and the target log quantity as the target call repeatability.
2. The call repetition determination method of an interface according to claim 1, wherein determining the target log number from the number of buried point logs of the target interface included in the target chained log includes:
extracting a buried point log from the logs included in the target chained log to obtain an initial buried point log set;
extracting a buried point log carrying the interface name of the target interface from the initial buried point log set to obtain a target buried point log set;
and determining the number of the buried point logs included in the target buried point log set to obtain the target log number.
3. The method for determining call repetition of an interface according to claim 1, wherein obtaining a target chained log of a target dimension from chained logs of traffic comprises one of:
acquiring a chained log of a target time period from the recorded chained log as the target chained log;
and acquiring the chained log with the included traffic as the target traffic from the recorded chained log as the target chained log.
4. The method of claim 1, wherein after determining a target call repetition corresponding to the target interface in the target dimension according to the target log number and the target traffic, the method further comprises at least one of:
distributing network resources for the target interface according to the target call repeatability;
deploying an interface algorithm for the target interface according to the target call repeatability;
and adjusting the call structure of the target interface according to the target call repeatability.
5. The method for determining call repetition of an interface according to claim 4,
allocating network resources for the target interface according to the target call repetition degree comprises: increasing a target number of network resources for the target interface if the target call repetition exceeds a first threshold;
deploying an interface algorithm for the target interface according to the target call repetition degree comprises: under the condition that the target calling repeatability exceeds a second threshold, deploying an interface algorithm with computing power exceeding a target computing power for the target interface;
the adjusting the call structure of the target interface according to the target call repeatability comprises the following steps: and under the condition that the target calling repeatability exceeds a third threshold value, the target interface is adjusted from the first calling position where the target interface is currently positioned to a second calling position with the bearing capacity smaller than the target bearing capacity.
6. An interface call repetition degree determining apparatus, comprising:
the first acquisition module is used for acquiring a target chained log of a target dimension from the chained log of the service;
the second acquisition module is used for acquiring the target log quantity of the target interface and the target traffic corresponding to the log of the target interface from the target chained log;
the determining module is used for determining target calling repeatability corresponding to the target interface under the target dimension according to the target log quantity and the target traffic;
wherein, the second acquisition module includes: a first determining unit, configured to determine the number of target logs according to the number of buried point logs of the target interface included in the target chained log; the second determining unit is used for determining the target traffic volume according to the service identifier corresponding to the buried point log of the target interface included in the target chained log;
wherein the second determining unit is further configured to: extracting service identifiers from the buried point logs of the target interfaces to obtain an initial service identifier list; performing de-duplication operation on the initial service identification list to obtain a target service identification list; determining the number of service identifiers included in the target service identifier list to obtain the target service volume;
and determining the ratio between the target log quantity and the target traffic volume as the target call repeatability, or determining the ratio between the target traffic volume and the target log quantity as the target call repeatability.
7. A computer readable storage medium, characterized in that the computer readable storage medium comprises a stored program, wherein the program when run performs the method of any of the preceding claims 1 to 5.
8. An electronic device comprising a memory and a processor, characterized in that the memory has stored therein a computer program, the processor being arranged to execute the method according to any of the claims 1 to 5 by means of the computer program.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110723409.6A CN113434135B (en) | 2021-06-28 | 2021-06-28 | Method and device for determining call repeatability of interface, storage medium and electronic device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110723409.6A CN113434135B (en) | 2021-06-28 | 2021-06-28 | Method and device for determining call repeatability of interface, storage medium and electronic device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113434135A CN113434135A (en) | 2021-09-24 |
| CN113434135B true CN113434135B (en) | 2023-06-16 |
Family
ID=77757456
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110723409.6A Active CN113434135B (en) | 2021-06-28 | 2021-06-28 | Method and device for determining call repeatability of interface, storage medium and electronic device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113434135B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113888311A (en) * | 2021-10-14 | 2022-01-04 | 中国工商银行股份有限公司 | Risk early warning method and device, computer equipment and computer readable storage medium |
Citations (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108509323A (en) * | 2018-01-30 | 2018-09-07 | 深圳壹账通智能科技有限公司 | Method for processing business, device based on log analysis and computer equipment |
| CN109144817A (en) * | 2018-08-03 | 2019-01-04 | 江苏满运软件科技有限公司 | A kind of daily record data monitoring system and method |
| CN109753406A (en) * | 2018-12-05 | 2019-05-14 | 平安科技（深圳）有限公司 | Method for monitoring performance, device, equipment and the computer readable storage medium of interface |
| CN109800225A (en) * | 2018-12-24 | 2019-05-24 | 北京奇艺世纪科技有限公司 | Acquisition methods, device, server and the computer readable storage medium of operational indicator |
| CN110113224A (en) * | 2019-03-19 | 2019-08-09 | 深圳壹账通智能科技有限公司 | Capacity monitor method, apparatus, computer equipment and storage medium |
| CN110198227A (en) * | 2018-04-04 | 2019-09-03 | 腾讯科技（深圳）有限公司 | Processing method, device, storage medium and the electronic device of journal file |
| CN110727567A (en) * | 2019-09-09 | 2020-01-24 | 平安证券股份有限公司 | Software quality detection method and device, computer equipment and storage medium |
| CN111124906A (en) * | 2019-12-17 | 2020-05-08 | 支付宝(杭州)信息技术有限公司 | Tracking method, compiling method and device based on dynamic embedded points and electronic equipment |
| CN111158926A (en) * | 2019-12-12 | 2020-05-15 | 口碑(上海)信息技术有限公司 | Service request analysis method, device and equipment |
| CN112181782A (en) * | 2020-10-16 | 2021-01-05 | 中国工商银行股份有限公司 | Adaptive gray function issuing method and device based on AB test |
| WO2021008029A1 (en) * | 2019-07-15 | 2021-01-21 | 平安普惠企业管理有限公司 | Case execution method, apparatus and device, and computer readable storage medium |
| CN112269879A (en) * | 2020-11-02 | 2021-01-26 | 武汉烽火众智数字技术有限责任公司 | Method and equipment for analyzing middle station log based on k-means algorithm |
| CN112416557A (en) * | 2020-11-23 | 2021-02-26 | 青岛海尔科技有限公司 | Method and device for determining call relation, storage medium and electronic device |
| CN112751729A (en) * | 2020-12-30 | 2021-05-04 | 平安证券股份有限公司 | Log monitoring method, device, medium and electronic equipment |
-
2021
- 2021-06-28 CN CN202110723409.6A patent/CN113434135B/en active Active
Patent Citations (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108509323A (en) * | 2018-01-30 | 2018-09-07 | 深圳壹账通智能科技有限公司 | Method for processing business, device based on log analysis and computer equipment |
| CN110198227A (en) * | 2018-04-04 | 2019-09-03 | 腾讯科技（深圳）有限公司 | Processing method, device, storage medium and the electronic device of journal file |
| CN109144817A (en) * | 2018-08-03 | 2019-01-04 | 江苏满运软件科技有限公司 | A kind of daily record data monitoring system and method |
| CN109753406A (en) * | 2018-12-05 | 2019-05-14 | 平安科技（深圳）有限公司 | Method for monitoring performance, device, equipment and the computer readable storage medium of interface |
| CN109800225A (en) * | 2018-12-24 | 2019-05-24 | 北京奇艺世纪科技有限公司 | Acquisition methods, device, server and the computer readable storage medium of operational indicator |
| CN110113224A (en) * | 2019-03-19 | 2019-08-09 | 深圳壹账通智能科技有限公司 | Capacity monitor method, apparatus, computer equipment and storage medium |
| WO2021008029A1 (en) * | 2019-07-15 | 2021-01-21 | 平安普惠企业管理有限公司 | Case execution method, apparatus and device, and computer readable storage medium |
| CN110727567A (en) * | 2019-09-09 | 2020-01-24 | 平安证券股份有限公司 | Software quality detection method and device, computer equipment and storage medium |
| CN111158926A (en) * | 2019-12-12 | 2020-05-15 | 口碑(上海)信息技术有限公司 | Service request analysis method, device and equipment |
| CN111124906A (en) * | 2019-12-17 | 2020-05-08 | 支付宝(杭州)信息技术有限公司 | Tracking method, compiling method and device based on dynamic embedded points and electronic equipment |
| CN112181782A (en) * | 2020-10-16 | 2021-01-05 | 中国工商银行股份有限公司 | Adaptive gray function issuing method and device based on AB test |
| CN112269879A (en) * | 2020-11-02 | 2021-01-26 | 武汉烽火众智数字技术有限责任公司 | Method and equipment for analyzing middle station log based on k-means algorithm |
| CN112416557A (en) * | 2020-11-23 | 2021-02-26 | 青岛海尔科技有限公司 | Method and device for determining call relation, storage medium and electronic device |
| CN112751729A (en) * | 2020-12-30 | 2021-05-04 | 平安证券股份有限公司 | Log monitoring method, device, medium and electronic equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113434135A (en) | 2021-09-24 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106993048B (en) | Determine method and device, information recommendation method and the device of recommendation information | |
| CN112434039A (en) | Data storage method, device, storage medium and electronic device | |
| CN113434293A (en) | Method and apparatus for processing repeat request, storage medium, and electronic apparatus | |
| CN113434135B (en) | Method and device for determining call repeatability of interface, storage medium and electronic device | |
| CN112685287B (en) | Product data testing method and device, storage medium and electronic device | |
| CN111770022B (en) | Capacity expansion method, system, equipment and computer storage medium based on link monitoring | |
| CN111159031A (en) | Method for applying mobile terminal automation test, computer device and computer readable storage medium | |
| CN110472216B (en) | Method and device for determining field, storage medium and electronic device | |
| CN110087226B (en) | Flow statistical method and device, storage medium and electronic device | |
| CN104883705A (en) | Problem positioning method for data service complaints and device thereof | |
| CN114745275A (en) | Node updating method and device in cloud service environment and computer equipment | |
| CN110990381B (en) | Processing method and device of server, storage medium and electronic device | |
| CN112256658B (en) | Log record distribution method and device, storage medium and electronic device | |
| CN110750601A (en) | Interaction method and device based on connection path, storage medium and electronic device | |
| CN110677544B (en) | PCRF location script updating method, device, equipment and storage medium | |
| CN113434525A (en) | Cache data updating method and device, storage medium and electronic device | |
| CN111212432B (en) | Method, device, equipment and medium for positioning pseudo base station | |
| CN114090074A (en) | Method and device for configuring operating environment, storage medium and electronic device | |
| CN112689249A (en) | Short message sending method, device, system, storage medium and electronic equipment | |
| CN113434399B (en) | Service node log processing method and device, storage medium and electronic device | |
| CN107453946B (en) | Field management method and device and electronic equipment | |
| CN112752252B (en) | Cell home location identification method and device | |
| CN116916295B (en) | Resident base station determining method and device and electronic equipment | |
| CN113055419B (en) | Information sending method and device | |
| CN117873827A (en) | Log configuration information updating method and device, storage medium and electronic device |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |