CN112416557B - Method and device for determining call relation, storage medium and electronic device - Google Patents

Method and device for determining call relation, storage medium and electronic device Download PDF

Info

Publication number
CN112416557B
CN112416557B CN202011325790.2A CN202011325790A CN112416557B CN 112416557 B CN112416557 B CN 112416557B CN 202011325790 A CN202011325790 A CN 202011325790A CN 112416557 B CN112416557 B CN 112416557B
Authority
CN
China
Prior art keywords
log
call
calling
identifier
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
Application number
CN202011325790.2A
Other languages
Chinese (zh)
Other versions
CN112416557A (en
Inventor
师建伟
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Qingdao Haier Technology Co Ltd
Haier Smart Home Co Ltd
Original Assignee
Qingdao Haier Technology Co Ltd
Haier Smart Home Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Qingdao Haier Technology Co Ltd, Haier Smart Home Co Ltd filed Critical Qingdao Haier Technology Co Ltd
Priority to CN202011325790.2A priority Critical patent/CN112416557B/en
Publication of CN112416557A publication Critical patent/CN112416557A/en
Application granted granted Critical
Publication of CN112416557B publication Critical patent/CN112416557B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • 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/46—Multiprogramming arrangements
    • G06F9/48—Program initiating; Program switching, e.g. by interrupt
    • G06F9/4806—Task transfer initiation or dispatching
    • G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
    • G06F9/4881—Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
    • G06F11/3466—Performance evaluation by tracing or monitoring
    • G06F11/3476—Data logging
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/21—Design, administration or maintenance of databases
    • G06F16/219—Managing data history or versioning

Abstract

The invention provides a method and a device for determining a call relation, a storage medium and an electronic device, wherein the method comprises the following steps: acquiring a call log set generated by an object set, wherein each call log in the call log set is a log generated by an object in the object set in a call process, and each call log comprises a call identifier and an identity identifier; and determining a calling relationship among the objects in the object set according to a calling identifier and an identity identifier in the calling log set, wherein the calling identifier is used for identifying a sub-calling process in a calling process, the identity identifier is used for identifying the identity of the object generating the calling log in the sub-calling process, and the calling process comprises at least one sub-calling process. The method and the device can solve the technical problem of low efficiency of determining the calling relationship between the objects in the related technology, and improve the efficiency of determining the calling relationship between the objects.

Description

Method and device for determining call relation, storage medium and electronic device
Technical Field
The invention relates to the field of computers, in particular to a method and a device for determining a call relation, a storage medium and an electronic device.
Background
In the related art, there are often complex calling relationships between multiple systems and between objects within the same system. Taking the system as a business system as an example, one object (including but not limited to an interface) may be called by an object of an external system and an object in the same system as a called end, or may be called by an object of an external system and an object in the same system as a calling end. The method has the advantages that the calling amount, the calling time consumption and the calling success and failure times of each object are obtained, and the method plays a vital role in maintaining the stability of the whole system.
In the related art, when analyzing a call relation of an object and performing statistics on related information, a hard-coding method of codes inside a system is generally adopted, and codes for analyzing the call relation between the objects are written into a program code of a calling end in a hard-coding manner, so that the method has higher requirements on a calling logic of the calling end, and a large number of codes need to be written, thereby resulting in higher complexity and lower efficiency; moreover, because a large amount of rewriting is performed on the program code in this manner, the stability and performance of the object itself will be affected, and even if the stability and performance are severe, an error caused by analyzing the object call relation code written into the program code will cause the whole object to be unusable; and when the system structure is complex (for example, mutual calling of a plurality of external systems occurs), more codes need to be written, so that the code architecture is damaged, the development efficiency is influenced, and a large amount of manpower and material resources are consumed.
Aiming at the technical problem that the efficiency of determining the calling relationship between the objects is low in the related technology, an effective technical scheme is not provided.
Disclosure of Invention
The embodiment of the invention provides a method and a device for determining a call relation, a storage medium and an electronic device, which are used for at least solving the technical problem of low efficiency of determining the call relation between objects in the related art.
According to an embodiment of the present invention, there is provided a method for determining a call relation, including: acquiring a call log set generated by an object set, wherein each call log in the call log set is a log generated by an object in the object set in a call process, and each call log comprises a call identifier and an identity identifier; and determining a calling relationship between objects in the object set according to a calling identifier and an identity identifier in the calling log set, wherein the calling identifier is used for identifying a sub-calling process in a calling process, the identity identifier is used for identifying the identity of an object generating the calling log in the sub-calling process, and the calling process comprises at least one sub-calling process.
Optionally, the determining, according to the invocation identifier and the identity identifier in the invocation log set, an invocation relationship between objects in the object set includes: determining that the calling process comprises a sub-calling process under the condition that the calling identifications in the calling log set are the same; determining a first log and a second log in the call log set, wherein an identity in the first log is used for indicating that an identity of a first object generating the first log in the call process is a call end, and an identity in the second log is used for indicating that an identity of a second object generating the second log in the call process is a called end; determining a calling relationship between objects in the set of objects includes the first object calling the second object in the one calling process.
Optionally, the method further comprises: determining a target initiation log and a target reception log in the first log, wherein the first log comprises a plurality of logs, the plurality of logs comprises the target initiation log and the target reception log, a timestamp in the target initiation log is a minimum value of timestamps in the first log, and a timestamp in the target reception log is a maximum value of timestamps in the first log; determining a difference between a timestamp in the receive log and a timestamp in the initiate log; and determining the difference value as the calling time of the first object for calling the second object.
Optionally, the method further comprises: determining the number of initiation logs in the first log, wherein each initiation log is used for indicating that each initiation log is a log generated when the first object initiates the call to the second object; and determining the number as the calling times of the first object calling the second object.
Optionally, the determining, according to the invocation identifier and the identity identifier in the invocation log set, an invocation relationship between objects in the object set includes: under the condition that the call log set comprises a first call identifier and a second call identifier, extracting a prefix of the first call identifier to obtain a first prefix, and extracting a prefix of the second call identifier to obtain a second prefix, wherein each call identifier comprises a prefix, and the prefix of each call identifier is used for identifying a call process to which a sub-call process identified by each call identifier belongs; determining that two calling processes exist in the objects in the object set under the condition that the first prefix and the second prefix are different; and determining the calling relationship of the objects in the object set in a first calling process and the calling relationship of the objects in the object set in a second calling process according to the calling identifiers and the identity identifiers in the calling log set, wherein the first calling process is the calling process of the first prefix identifier, and the second calling process is the calling process of the second prefix identifier.
Optionally, the determining, according to the invocation identifier and the identity identifier in the invocation log set, a call relationship of the object in the object set in the first invocation process includes: determining that the first calling process comprises a sub-calling process under the condition that the calling identifications with the first prefix in the calling log set are the same; determining a third log and a fourth log in the call log set, wherein prefixes of call identifiers in the third log and the fourth log are both the first prefix, an identity in the third log is used for indicating that an identity of a third object generating the third log in the first call process is a call end, and an identity in the fourth log is used for indicating that an identity of a fourth object generating the fourth log in the first call process is a called end; determining that the third object invokes the fourth object in the first invocation process.
Optionally, each of the call identifiers further includes a suffix, where the suffix of each call identifier is used to identify one of the sub-call procedures in the call procedure to which the suffix belongs, where determining, according to the call identifier and the identity identifier in the call log set, a call relationship of an object in the object set in the first call procedure includes: determining that the first calling process comprises a plurality of sub-calling processes under the condition that the calling identifications with the first prefix in the calling log set are different; determining a first set of the call log sets, wherein the prefix of the call identifier of each call log in the first set is the first prefix, and repeating the following steps until a current set is empty, the current set is initialized to the first set, and a fifth object, a sixth object and a current object are initialized to be empty: determining whether a current set is empty, and if the current set is not empty, determining a fifth log and a sixth log in the current set, wherein suffixes of calling identifiers of the fifth log and the sixth log are the same, and the length of the suffixes of the calling identifiers of the fifth log and the sixth log is the maximum value of the length of the suffixes of the calling identifiers of the calling logs in the current set; the identity identifier recorded in the fifth log is used for indicating that the identity of the object generating the fifth log in the current sub-calling process is a calling end, and the identity identifier recorded in the sixth log is used for indicating that the object generating the sixth log is determined as the fifth object and the object generating the sixth log is determined as the sixth object under the condition that the identity of the object generating the sixth log in the current sub-calling process is a called end, wherein the current sub-calling process is a sub-calling process identified by a suffix of the calling identity of the fifth log; determining that the fifth object calls the sixth object in the current sub-call process; determining the fifth object as the current object; deleting a target log in the current set, and determining the obtained log set as the current set, wherein the suffix of the calling identifier of the target log is the same as the suffix of the calling identifier of the fifth log.
Optionally, before the determining the fifth object as the current object, the method further includes: under the condition that the current object is not empty, and under the condition that the sixth object is the same as a business system to which the current object belongs and the subsystem to which the sixth object belongs is the same, determining that the sixth object calls the current object in the first calling process, and the call of the sixth object to the current object is an internal call in the same subsystem, wherein each calling log further comprises the business system and the subsystem to which the object generating each calling log belongs, and each business system comprises at least one subsystem.
According to another embodiment of the present invention, there is provided an apparatus for determining a call relation, including: the system comprises an acquisition module, a storage module and a processing module, wherein the acquisition module is used for acquiring a call log set generated by an object set, each call log in the call log set is a log generated by an object in the object set in a call process, and each call log comprises a call identifier and an identity identifier; and the determining module is used for determining a calling relationship between objects in the object set according to a calling identifier and an identity identifier in the calling log set, wherein the calling identifier is used for identifying a sub-calling process in a calling process, the identity identifier is used for identifying the identity of an object generating the calling log in the sub-calling process, and the calling process comprises at least one sub-calling process.
Optionally, the determining module is further configured to: determining that the calling process comprises a sub-calling process under the condition that the calling identifications in the calling log set are the same; determining a first log and a second log in the call log set, wherein an identity in the first log is used for indicating that the identity of a first object generating the first log in the call process is a call end, and an identity in the second log is used for indicating that the identity of a second object generating the second log in the call process is a called end; determining a calling relationship between objects in the set of objects includes the first object calling the second object in the one calling process.
Optionally, the determining module is further configured to: determining a target initiation log and a target reception log in the first log, wherein the first log comprises a plurality of logs, the plurality of logs comprises the target initiation log and the target reception log, a timestamp in the target initiation log is a minimum value of timestamps in the first log, and a timestamp in the target reception log is a maximum value of timestamps in the first log; determining a difference between a timestamp in the receive log and a timestamp in the initiate log; and determining the difference value as the time consumed for the first object to call the second object.
Optionally, the determining module is further configured to: determining the number of initiation logs in the first logs, wherein each initiation log is used for indicating that each initiation log is a log generated when the first object initiates the call of the second object; and determining the number as the calling times of the first object calling the second object.
Optionally, the determining module is further configured to: under the condition that the call log set comprises a first call identifier and a second call identifier, extracting a prefix of the first call identifier to obtain a first prefix, and extracting a prefix of the second call identifier to obtain a second prefix, wherein each call identifier comprises a prefix, and the prefix of each call identifier is used for identifying a call process to which a sub-call process identified by each call identifier belongs; determining that two calling processes exist in the objects in the object set under the condition that the first prefix and the second prefix are different; and determining the calling relationship of the objects in the object set in a first calling process and the calling relationship of the objects in the object set in a second calling process according to the calling identifiers and the identity identifiers in the calling log set, wherein the first calling process is the calling process of the first prefix identifier, and the second calling process is the calling process of the second prefix identifier.
Optionally, the determining module is further configured to: determining that the first calling process comprises a sub-calling process under the condition that the calling identifications with the first prefix in the calling log set are the same; determining a third log and a fourth log in the call log set, wherein prefixes of call identifiers in the third log and the fourth log are both the first prefix, an identity in the third log is used for indicating that an identity of a third object generating the third log in the first call process is a call end, and an identity in the fourth log is used for indicating that an identity of a fourth object generating the fourth log in the first call process is a called end; determining that the third object invokes the fourth object in the first invocation process.
Optionally, each of the call identifiers further includes a suffix, and the suffix of each of the call identifiers is used to identify one of the sub-call procedures in the one of the call procedures, where the determining module is further configured to: determining that the first calling process comprises a plurality of sub-calling processes under the condition that the calling identifications with the first prefix in the calling log set are different; determining a first set of the call log sets, wherein the prefix of the call identifier of each call log in the first set is the first prefix, and repeating the following steps until a current set is empty, the current set is initialized to the first set, and a fifth object, a sixth object and a current object are initialized to be empty: determining whether a current set is empty, and if the current set is not empty, determining a fifth log and a sixth log in the current set, wherein suffixes of calling identifications of the fifth log and the sixth log are the same, and the length of suffixes of the calling identifications of the fifth log and the sixth log is the maximum value of the length of the calling identification suffixes of the calling logs in the current set; the identity identifier recorded in the fifth log is used for indicating that the identity of the object generating the fifth log in the current sub-calling process is a calling end, and the identity identifier recorded in the sixth log is used for indicating that the object generating the sixth log is determined as the fifth object and the object generating the sixth log is determined as the sixth object under the condition that the identity of the object generating the sixth log in the current sub-calling process is a called end, wherein the current sub-calling process is a sub-calling process identified by a suffix of the calling identity of the fifth log; determining that the fifth object calls the sixth object in the current sub-call process; determining the fifth object as the current object; deleting a target log in the current set, and determining the obtained log set as the current set, wherein the suffix of the calling identifier of the target log is the same as the suffix of the calling identifier of the fifth log.
Optionally, the determining module is further configured to: before the fifth object is determined as the current object, if the current object is not empty, if the sixth object is the same as a business system to which the current object belongs and the subsystem to which the current object belongs is the same, determining that the sixth object calls the current object in the first calling process, and the call of the sixth object to the current object is an internal call in the same subsystem, wherein each calling log further comprises the business system and the subsystem to which the object generating each calling log belongs, and each business system comprises at least one subsystem.
Alternatively, according to another embodiment of the present invention, a storage medium is provided, in which a computer program is stored, wherein the computer program is arranged to perform the above method when executed.
Alternatively, according to another embodiment of the present invention, there is provided an electronic apparatus, including a memory in which a computer program is stored and a processor configured to execute the computer program to perform the above method.
According to the method and the device, a call log set generated by an object set is obtained, wherein each call log in the call log set is a log generated by an object in the object set in a call process, and each call log comprises a call identifier and an identity identifier; and determining a calling relationship between objects in the object set according to a calling identifier and an identity identifier in the calling log set, wherein the calling identifier is used for identifying a sub-calling process in a calling process, the identity identifier is used for identifying the identity of an object generating the calling log in the sub-calling process, and the calling process comprises at least one sub-calling process. The object generates the call logs in the calling process, and each call log comprises the call identifier and the identity identifier, so that the call relationship between the objects can be determined according to the call identifiers and the identity identifiers in the call logs, the technical problem that the efficiency of determining the call relationship between the objects in the related technology is low can be solved, the efficiency of determining the call relationship between the objects is improved, the stability of a system cannot be influenced, and the stability and the code architecture of the system can be maintained.
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 application, illustrate embodiment(s) of the invention and together with the description serve to explain the invention without limiting the invention. In the drawings:
FIG. 1 is a flow chart of a method for determining a call relation according to an embodiment of the present invention;
FIG. 2 is a diagram illustrating a calling process according to an embodiment of the present invention;
FIG. 3 is a diagram illustrating a calling process according to another embodiment of the present invention;
FIG. 4 is a schematic diagram of a call log according to an embodiment of the invention;
FIG. 5 is a schematic diagram of a call log according to another embodiment of the invention;
FIG. 6 is a diagram of a calling process according to yet another embodiment of the present invention;
FIG. 7 is a diagram of a calling process according to yet another embodiment of the present invention;
FIG. 8 is a diagram illustrating an application environment of a call relation determining method according to an embodiment of the present invention;
fig. 9 is a schematic diagram of a call relation determined by the method for determining a call relation according to the embodiment of the present invention;
fig. 10 is a block diagram of the structure of a call relation determination apparatus according to an embodiment of the present invention;
fig. 11 is a schematic structural diagram of an alternative electronic device according to an embodiment of the invention.
Detailed Description
The invention will be described in detail hereinafter with reference to the accompanying drawings in conjunction with embodiments. It should be noted that the embodiments and features of the embodiments in the present application may be combined with each other without conflict.
It should be noted that the terms "first," "second," and the like in the description and claims of the present invention and in the drawings described above are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order.
An embodiment of the present invention provides a method for determining a call relation, and fig. 1 is a flowchart of a method for determining a call relation according to an embodiment of the present invention, as shown in fig. 1, including:
step S102, obtaining a call log set generated by an object set, wherein each call log in the call log set is a log generated by an object in the object set in a call process, and each call log comprises a call identifier and an identity identifier;
step S104, determining a calling relationship between objects in the object set according to a calling identifier and an identity identifier in the calling log set, wherein the calling identifier is used for identifying a sub-calling process in a calling process, the identity identifier is used for identifying the identity of an object generating the calling log in the sub-calling process, and the calling process comprises at least one sub-calling process.
According to the method and the device, a call log set generated by an object set is obtained, wherein each call log in the call log set is a log generated by an object in the object set in a call process, and each call log comprises a call identifier and an identity identifier; and determining a calling relationship between objects in the object set according to a calling identifier and an identity identifier in the calling log set, wherein the calling identifier is used for identifying a sub-calling process in a calling process, the identity identifier is used for identifying the identity of an object generating the calling log in the sub-calling process, and the calling process comprises at least one sub-calling process. The object generates the call logs in the calling process, and each call log comprises the call identifier and the identity identifier, so that the call relationship between the objects can be determined according to the call identifiers and the identity identifiers in the call logs, the technical problem that the efficiency of determining the call relationship between the objects in the related technology is low can be solved, the efficiency of determining the call relationship between the objects is improved, the stability of a system cannot be influenced, and the stability and the code architecture of the system can be maintained.
In the above embodiments, the calling procedure refers to a complete calling procedure at a time, and one calling procedure may include at least one sub-calling procedure. As shown in fig. 2, two calling procedures (i.e., two complete calling procedures) are included. For the calling process 1, the calling process only includes a sub-calling process, namely, the object 1 calls the object 2, and the sub-calling process is the calling process 1 itself; for the calling procedure 2, two sub-calling procedures are included, namely, the calling of the object 3 by the object 1, and the calling of the object 4 by the object 3.
In the calling process shown in fig. 3, when the object 1 initiates a call to the object 2, a call identifier is generated: 123.0.1, and generating an initiation log in which the following information is recorded: "an identifier 1,123.0.1 and a timestamp 1", where the identifier 1 is an identity identifier, an object used for identifying the log generation is a calling end, 123.0.1 is a calling identifier, a prefix of the calling identifier is 123, and the timestamp is a timestamp for generating the initiation log; the object 1 sends the generated calling identifier to the object 2, and after receiving the call of the object 1, the object 2 generates a receiving log, wherein the receiving log records the following information: "mark 2,123.0.1, timestamp 2", mark 2 is used to mark that the object generating the receiving log is the called end, and timestamp 2 is the time of generating the receiving log. After the object 2 calculates the calling result, the calling reception is returned to the object 1, and the initiating log is generated, and after the object 1 receives the calling result, the receiving log is generated.
Determining a calling relationship between objects in the object set according to the calling identifier and the identity identifier in the calling log set, including: determining that the calling process comprises a sub-calling process under the condition that the calling identifications in the calling log set are the same; determining a first log and a second log in the call log set, wherein an identity in the first log is used for indicating that the identity of a first object generating the first log in the call process is a call end, and an identity in the second log is used for indicating that the identity of a second object generating the second log in the call process is a called end; determining a calling relationship between objects in the set of objects includes the first object calling the second object in the one calling process.
In the above embodiment, in a case where the call identifiers in the call log set are all the same, it is determined that all the call logs in the call log set are logs related to the same sub-call procedure in the same call procedure, that is, only one call procedure exists in the objects in the object set.
Optionally, the foregoing embodiment is further configured to implement the following technical solution: determining a target initiation log and a target reception log in the first log, wherein the first log comprises a plurality of logs, the plurality of logs comprises the target initiation log and the target reception log, a timestamp in the target initiation log is a minimum value of timestamps in the first log, and a timestamp in the target reception log is a maximum value of timestamps in the first log; determining a difference between a timestamp in the receive log and a timestamp in the initiate log; and determining the difference value as the calling time of the first object for calling the second object.
By the embodiment, the calling time consumption in the calling process can be determined according to the analysis of the calling log, and relevant codes for counting the calling time consumption are not required to be written into program codes in a hard coding mode, so that the complexity of determining the calling time consumption is reduced, the efficiency of determining the calling time consumption is improved, and the stability of the system is maintained.
It should be noted that, the above embodiment may also implement the following technical solutions: determining the number of initiation logs in the first logs, wherein each initiation log is used for indicating that each initiation log is a log generated when the first object initiates the call of the second object; and determining the number as the calling times of the first object calling the second object.
In the above embodiment, the call log further records a type identifier, and the type identifier in the call log generated by the call terminal includes: first type identification: for indicating initiation of calls to other objects, and a second type identifier: the system is used for indicating to receive the calling result returned by other objects; the type identification in the call log generated by the called terminal comprises the following steps: the third type identification: for indicating the receipt of calls for other objects, and a fourth type identification: for indicating the result of the initiated call. Therefore, with the above embodiment, all logs in the first log having the first type identifier may be determined as the initiation logs in the first log, and the number of the initiation logs may be determined as the number of times that the first object invokes the second object.
As an optional implementation manner, the determining, according to the call identifier and the identity identifier in the call log set, a call relationship between objects in the object set includes: under the condition that the call log set comprises a first call identifier and a second call identifier, extracting a prefix of the first call identifier to obtain a first prefix, and extracting a prefix of the second call identifier to obtain a second prefix, wherein each call identifier comprises a prefix, and the prefix of each call identifier is used for identifying a call process to which a sub-call process identified by each call identifier belongs; determining that two calling processes exist in the objects in the object set under the condition that the first prefix and the second prefix are different; and determining the calling relationship of the objects in the object set in a first calling process and the calling relationship of the objects in the object set in a second calling process according to the calling identifiers and the identity identifiers in the calling log set, wherein the first calling process is the calling process of the first prefix identifier, and the second calling process is the calling process of the second prefix identifier.
In the above embodiment, the call with different prefixes identifies the identified sub-calling procedure as a sub-calling procedure in a different calling procedure. As shown in FIG. 4, the call log set comprises a call log with a first call identifier 123.0.1 and a call log with a second call identifier 456.0.1, and two different complete call procedures exist between the object sets due to the different prefixes (i.e., 123 and 456) of the two call identifiers.
As an optional implementation manner, the determining, according to the call identifier and the identity identifier in the call log set, a call relationship of the object in the object set in the first call process includes: determining that the first calling process comprises a sub-calling process under the condition that the calling identifications with the first prefix in the calling log set are the same; determining a third log and a fourth log in the call log set, wherein prefixes of call identifiers in the third log and the fourth log are both the first prefix, an identity in the third log is used for indicating that an identity of a third object generating the third log in the first call process is a call end, and an identity in the fourth log is used for indicating that an identity of a fourth object generating the fourth log in the first call process is a called end; determining that the third object invokes the fourth object in the first invocation process.
In the above embodiment, a similar manner to determining the calling relationship of the object in the object set in the first calling process may be adopted to determine the calling relationship of the object in the object set in the second calling process, and the determination manner is similar, so that details are not described herein again.
As an optional implementation manner, each of the call identifiers further includes a suffix, and the suffix of each of the call identifiers is used to identify one of the sub-call procedures in the one of the call procedures to which the suffix belongs, where the determining, according to the call identifier and the identity identifier in the call log set, a call relationship of an object in the object set in the first call procedure includes: determining that the first calling process comprises a plurality of sub-calling processes under the condition that the calling identifications with the first prefix in the calling log set are different; determining a first set of the call log sets, wherein the prefix of the call identifier of each call log in the first set is the first prefix, and repeating the following steps until a current set is empty, the current set is initialized to the first set, and a fifth object, a sixth object and a current object are initialized to be empty: determining whether a current set is empty, and if the current set is not empty, determining a fifth log and a sixth log in the current set, wherein suffixes of calling identifications of the fifth log and the sixth log are the same, and the length of suffixes of the calling identifications of the fifth log and the sixth log is the maximum value of the length of the calling identification suffixes of the calling logs in the current set; the identity identifier recorded in the fifth log is used for indicating that the identity of the object generating the fifth log in the current sub-calling process is a calling end, and the identity identifier recorded in the sixth log is used for indicating that the object generating the sixth log is determined as the fifth object and the object generating the sixth log is determined as the sixth object under the condition that the identity of the object generating the sixth log in the current sub-calling process is a called end, wherein the current sub-calling process is a sub-calling process identified by a suffix of the calling identity of the fifth log; determining that the fifth object calls the sixth object in the current sub-call process; determining the fifth object as the current object; deleting a target log in the current set, and determining the obtained log set as the current set, wherein the suffix of the calling identifier of the target log is the same as the suffix of the calling identifier of the fifth log.
Wherein, prior to the determining the fifth object as the current object, the method further comprises: under the condition that the current object is not empty, under the condition that a business system to which the sixth object and the current object belong are the same and a subsystem to which the sixth object and the current object belong is the same, determining that the sixth object calls the current object in the first calling process, and the calling of the sixth object to the current object is an internal calling in the same subsystem, wherein each calling log further comprises the business system and the subsystem to which the object for generating each calling log belongs, and each business system comprises at least one subsystem.
In the above embodiment, the system may be divided according to different service types, service contents, and the like to obtain a plurality of systems; for each system, a plurality of subsystems may be partitioned according to different functions provided by the system, wherein the functions provided by the different subsystems are different. Each object in the set of objects has an affiliated system and an affiliated subsystem under that system, the objects including but not limited to systems, subsystems, and interfaces. As an optional embodiment, each call log further includes a system to which an object that generates the call log belongs, a subsystem to which the object belongs, and an object identifier, that is, the call log further includes the following information: "belonging system, belonging subsystem, object identification". Wherein the object identification includes, but is not limited to, an object name or other data used to identify the object. As shown in fig. 5, the call identifier of each call log further includes a suffix, for example: 0.1, and 0.1.1. Since the prefixes of the call identifiers in fig. 5 are all 123, it is determined that the call logs belong to the same complete call procedure, and the call identifiers with different suffixes correspond to different sub-call procedures in the complete call procedure. As shown in fig. 6, based on the above embodiment, it can be determined that the object 3 calls the object 4 in one sub-call process, the object 2 calls the object 3 in one sub-call process, the object 1 calls the object 2 in one sub-call process, and the object 2 and the object 3 belong to the same subsystem under the same system, so that it is determined that the object 2 calls the object 3 as an internal call of the same subsystem.
The following explains the determination method of the call relationship in the above embodiment with reference to an example, but is not intended to limit the technical solution of the embodiment of the present invention.
As shown in FIG. 7, in a complete calling process, the node 1 initiates a call to the node 2, wherein the node 2 nests the calling nodes 3, the CS and the CR are respectively logs generated when the calling end initiates the call and receives the call result, and the SR and the SS are respectively logs generated when the called end receives the call and initiates the call result. In a complete calling process, the whole link is identified by the same Identification (ID) (i.e. the prefix in the above embodiment), and then the same link can be identified according to the ID during data processing, so as to analyze the upstream and downstream in the calling process.
In the complete calling process, a sub-calling process is identified by suffixes, wherein each new sub-calling process is initiated with a new identifier (e.g., "1") added to the suffix of the calling identifier. Taking fig. 7 as an example, where the object includes a node, the call identifier in the call log generated by the node 1 is id.0.1, and the call identifier in the initiation log generated by the node 2 is id.0.1.1, where when the node 2 initiates a call to the node 3, the suffix of the received call identifier sent by the node 1 is added with an identifier bit "1", so as to obtain a call identifier with a new suffix: id.0.1.1.
In the above embodiment, taking a node as an interface as an example, each node generates a call log in a call process, where a system, a subsystem and an interface name to which the node belongs are recorded, and a call relationship between an upstream interface and a downstream interface can be analyzed subsequently according to the information. Optionally, the call log further includes the following information: a time stamp.
Through the embodiment, the upstream and downstream relation among the object sets can be determined. Taking fig. 6 as an example, in the above embodiment, it may be determined that the objects in the object set have the following types of upstream and downstream relationships:
direct upstream and downstream relationship: object 1 and object 2, object 2 and object 3, and object 3 and object 4, are in direct upstream and downstream relationship;
indirect upstream and downstream relationship: there is an indirect upstream-downstream relationship between object 2 and object 4.
The above embodiment can process and analyze the upstream and downstream call relation of the huge data volume in real time, and can be applied to the application environment shown in fig. 8. As shown in fig. 8, the system logs are written out uniformly to the open source stream processing platform Kafka, which can serve as a high-throughput data buffer. The Flink real-time program 1 reads each system log, executes the determination method of the call relationship in the above embodiment, analyzes call data (including but not limited to information such as a call end, a called end, and a corresponding timestamp in each call process), and writes the call data into a database (including but not limited to MySQL). Alternatively, the time consumption of each call may be counted according to the call data written in the database. Meanwhile, in order to maintain the calling relationship, a dictionary table needs to be established, but because duplication removal is needed when the dictionary table data is written into MySQL, huge pressure is caused on MySQL, in the embodiment, the dictionary table data is written back to Kafka, the Flink real-time program 2 is used for duplication removal of the data, and the duplicated calling data is written into MySQL.
Alternatively, the real-time program may be a Spark, spark stream program, or other program or component that employs a caching component to provide data caching and collection services.
As an example, the objects in the above embodiments include, but are not limited to, subsystems, interfaces, etc. objects in the system. With the above embodiment, as an example, the invocation relationship shown in fig. 9 may be determined, where the system in fig. 9 includes, but is not limited to, an application service system (AppServer), an IFTTT system, and other systems.
Optionally, the number of times of being called, the time consumed for calling, and the success rate information of each interface may be further calculated in the above embodiment.
By the embodiment, the decoupling between the interface calling process and the analysis interface calling relation is realized, so that the upstream and downstream calling relation and the analysis interface calling condition can be automatically maintained even if the complexity of the system is increased, and the upstream and downstream analysis of the large-call-quantity multi-system calling is supported; in the embodiment, based on chain log analysis, the interface only needs to print logs asynchronously, the influence on the original system is very little, and the influence on the architecture and the performance of the original system is very little, so that the determination of complex calling relations among a plurality of systems can be realized; when the data volume is huge, the embodiment can still carry out real-time analysis without manual participation; because the interface calling process is decoupled from the analysis of the interface calling relationship, the later maintenance workload of the program is greatly reduced, and the expandability of the system is greatly improved.
As described above, the present invention is only a specific embodiment of the present invention, but the scope of the present invention is not limited thereto, and when the drag editing operation is performed, the selection and drag of the content in the circle are not limited to operations such as right double click, etc., because the corresponding editing tool is opened and recognized for various contents in various content formats when editing the content, among circles of various content formats. The protection scope of the present invention shall be subject to the protection scope of the claims.
Through the above description of the embodiments, those skilled in the art can clearly understand that the method according to the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but the former is a better implementation mode in many cases. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which is stored in a storage medium (e.g., ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal device (e.g., a mobile phone, a computer, a server, or a network device) to execute the method according to the embodiments of the present invention.
According to another embodiment of the present invention, a device for determining a call relationship is provided, where the device is used to implement the foregoing embodiment and preferred embodiments, and details are not repeated after the description is given. As used below, the term "module" may be a combination of software and/or hardware that implements a predetermined function. Although the means described in the embodiments below are preferably implemented in software, an implementation in hardware, or a combination of software and hardware is also possible and contemplated.
Fig. 10 is a block diagram of a structure of a call relation determination apparatus according to an embodiment of the present invention, the apparatus including:
an obtaining module 92, configured to obtain a call log set generated by an object set, where each call log in the call log set is a log generated by an object in the object set in a call process, and each call log includes a call identifier and an identity identifier;
a determining module 94, configured to determine a calling relationship between objects in the object set according to a calling identifier and an identity identifier in the call log set, where the calling identifier is used to identify a sub-calling procedure in a calling procedure, and the identity identifier is used to identify an identity of an object generating the call log in the sub-calling procedure, where the calling procedure includes at least one of the sub-calling procedures.
According to the method and the device, a call log set generated by an object set is obtained, wherein each call log in the call log set is a log generated by an object in the object set in a call process, and each call log comprises a call identifier and an identity identifier; and determining a calling relationship between objects in the object set according to a calling identifier and an identity identifier in the calling log set, wherein the calling identifier is used for identifying a sub-calling process in a calling process, the identity identifier is used for identifying the identity of an object generating the calling log in the sub-calling process, and the calling process comprises at least one sub-calling process. The object generates the call logs in the calling process, and each call log comprises the call identifier and the identity identifier, so that the call relationship between the objects can be determined according to the call identifiers and the identity identifiers in the call logs, the technical problem that the efficiency of determining the call relationship between the objects in the related technology is low can be solved, the efficiency of determining the call relationship between the objects is improved, the stability of a system cannot be influenced, and the stability and the code architecture of the system can be maintained.
In the above embodiment, the determining module 94 is further configured to: determining that the calling process comprises a sub-calling process under the condition that the calling identifications in the calling log set are the same; determining a first log and a second log in the call log set, wherein an identity in the first log is used for indicating that an identity of a first object generating the first log in the call process is a call end, and an identity in the second log is used for indicating that an identity of a second object generating the second log in the call process is a called end; determining a calling relationship between objects in the set of objects includes the first object calling the second object in the one calling process.
Wherein the determining module 94 is further configured to: determining a target initiation log and a target reception log in the first log, wherein the first log comprises a plurality of logs, the plurality of logs comprises the target initiation log and the target reception log, a timestamp in the target initiation log is a minimum value of timestamps in the first log, and a timestamp in the target reception log is a maximum value of timestamps in the first log; determining a difference between a timestamp in the receive log and a timestamp in the initiate log; and determining the difference value as the calling time of the first object for calling the second object.
Optionally, the determining module 94 is further configured to: determining the number of initiation logs in the first logs, wherein each initiation log is used for indicating that each initiation log is a log generated when the first object initiates the call of the second object; and determining the number as the calling times of the first object calling the second object.
Based on the above embodiment, the determining module 94 is further configured to: under the condition that the call log set comprises a first call identifier and a second call identifier, extracting a prefix of the first call identifier to obtain a first prefix, and extracting a prefix of the second call identifier to obtain a second prefix, wherein each call identifier comprises a prefix, and the prefix of each call identifier is used for identifying a call process to which a sub-call process identified by each call identifier belongs; determining that two calling processes exist in the objects in the object set under the condition that the first prefix and the second prefix are different; and determining the calling relationship of the objects in the object set in a first calling process and the calling relationship of the objects in the object set in a second calling process according to the calling identifiers and the identity identifiers in the calling log set, wherein the first calling process is the calling process of the first prefix identifier, and the second calling process is the calling process of the second prefix identifier.
In an optional embodiment, the determining module is further configured to: determining that the first calling process comprises a sub-calling process under the condition that the calling identifications with the first prefix in the calling log set are the same; determining a third log and a fourth log in the call log set, wherein prefixes of call identifiers in the third log and the fourth log are both the first prefix, an identity in the third log is used for indicating that an identity of a third object generating the third log in the first call process is a call end, and an identity in the fourth log is used for indicating that an identity of a fourth object generating the fourth log in the first call process is a called end; determining that the third object invokes the fourth object in the first invocation process.
Wherein each call identifier further comprises a suffix, and the suffix of each call identifier is used for identifying one sub-call procedure in the one call procedure to which the call identifier belongs, and the determining module is further configured to: determining that the first calling process comprises a plurality of sub-calling processes under the condition that the calling identifications with the first prefix in the calling log set are different; determining a first set of the call log sets, wherein the prefix of the call identifier of each call log in the first set is the first prefix, and repeating the following steps until a current set is empty, the current set is initialized to the first set, and a fifth object, a sixth object and a current object are initialized to be empty: determining whether a current set is empty, and if the current set is not empty, determining a fifth log and a sixth log in the current set, wherein suffixes of calling identifications of the fifth log and the sixth log are the same, and the length of suffixes of the calling identifications of the fifth log and the sixth log is the maximum value of the length of the calling identification suffixes of the calling logs in the current set; the identity identifier recorded in the fifth log is used for indicating that the identity of the object generating the fifth log in the current sub-calling process is a calling end, and the identity identifier recorded in the sixth log is used for indicating that the object generating the sixth log is determined as the fifth object and the object generating the sixth log is determined as the sixth object under the condition that the identity of the object generating the sixth log in the current sub-calling process is a called end, wherein the current sub-calling process is a sub-calling process identified by a suffix of the calling identity of the fifth log; determining that the fifth object calls the sixth object in the current sub-call process; determining the fifth object as the current object; deleting a target log in the current set, and determining the obtained log set as the current set, wherein the suffix of the calling identifier of the target log is the same as the suffix of the calling identifier of the fifth log.
It should be noted that, the determining module is further configured to: before the fifth object is determined as the current object, if the current object is not empty, if the sixth object is the same as a business system to which the current object belongs and the subsystem to which the current object belongs is the same, determining that the sixth object calls the current object in the first calling process, and the call of the sixth object to the current object is an internal call in the same subsystem, wherein each calling log further comprises the business system and the subsystem to which the object generating each calling log belongs, and each business system comprises at least one subsystem.
An embodiment of the present invention further provides a storage medium including a stored program, wherein the program executes any one of the methods described above.
Alternatively, in this embodiment, the storage medium may be configured to store program codes for performing the following steps:
s1, acquiring a call log set generated by an object set, wherein each call log in the call log set is a log generated by an object in the object set in a call process, and each call log comprises a call identifier and an identity identifier;
s2, determining a calling relation among objects in the object set according to a calling identifier and an identity identifier in the calling log set, wherein the calling identifier is used for identifying a sub-calling process in a calling process, the identity identifier is used for identifying the identity of an object generating the calling log in the sub-calling process, and the calling process comprises at least one sub-calling process.
Optionally, in this embodiment, the storage medium may include, but is not limited to: various media capable of storing program codes, such as a usb disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a removable hard disk, a magnetic disk, or an optical disk.
Optionally, for a specific example in this embodiment, reference may be made to the examples described in the above embodiment and optional implementation, and this embodiment is not described herein again.
Embodiments of the present invention also provide an electronic device comprising a memory having a computer program stored therein and a processor arranged to run the computer program to perform the steps of any of the above method embodiments.
Optionally, the electronic apparatus may further include a transmission device and an input/output device, wherein the transmission device is connected to the processor, and the input/output device is connected to the processor.
Optionally, in this embodiment, the processor may be configured to execute the following steps by a computer program:
s1, acquiring a call log set generated by an object set, wherein each call log in the call log set is a log generated by an object in the object set in a call process, and each call log comprises a call identifier and an identity identifier;
s2, determining a calling relation among objects in the object set according to a calling identifier and an identity identifier in the calling log set, wherein the calling identifier is used for identifying a sub-calling process in a calling process, the identity identifier is used for identifying the identity of an object generating the calling log in the sub-calling process, and the calling process comprises at least one sub-calling process.
Fig. 11 is a schematic structural diagram of an alternative electronic device according to an embodiment of the invention. Alternatively, it can be understood by those skilled in the art that the structure shown in fig. 11 is only an illustration, and the electronic device may also be a terminal device such as a smart phone (e.g., an Android phone, an iOS phone, etc.), a tablet computer, a palm computer, a Mobile Internet Device (MID), a PAD, and the like. Fig. 11 is a diagram illustrating the structure of the electronic device. For example, the electronic device may also include more or fewer components (e.g., network interfaces, etc.) than shown in FIG. 11, or have a different configuration than shown in FIG. 11.
The memory 1002 may be configured to store software programs and modules, such as program instructions/modules corresponding to the method for determining a call relation and the device for determining a call relation in the embodiment of the present invention, and the processor 1004 executes various functional applications and data processing by running the software programs and modules stored in the memory 1002, that is, implementing the method for determining a call relation. The memory 1002 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 1002 may further include memory located remotely from the processor 1004, which may be connected to the terminal over a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof. As an example, the memory 1002 may include, but is not limited to, the obtaining module 92, the determining module 94 of the determining device of the call relation. In addition, other module units in the device for determining a call relationship may also be included, but are not limited to these, and are not described in detail in this example.
Optionally, the transmission device 1006 is used for receiving or transmitting data via a network. Examples of the network may include a wired network and a wireless network. In one example, the transport device 1006 includes a Network adapter (NIC) that can be connected to a router via a Network cable to communicate with the internet or a local area Network. In one example, the transmission device 1006 is a Radio Frequency (RF) module, which is used for communicating with the internet in a wireless manner.
In addition, the electronic device further includes: a display 1008 for displaying a screen; and a connection bus 1010 for connecting the respective module parts in the above-described electronic apparatus.
Optionally, for a specific example in this embodiment, reference may be made to the examples described in the above embodiment and optional implementation, and this embodiment is not described herein again.
It will be apparent to those skilled in the art that the modules or steps of the present invention described above may be implemented by a general purpose computing device, they may be centralized on a single computing device or distributed across a network of multiple computing devices, and alternatively, they may be implemented by program code executable by a computing device, such that they may be stored in a storage device and executed by a computing device, and in some cases, the steps shown or described may be performed in an order different than that described herein, or they may be separately fabricated into individual integrated circuit modules, or multiple ones of them may be fabricated into a single integrated circuit module. Thus, the present invention is not limited to any specific combination of hardware and software.
The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, or improvement made within the principle of the present invention should be included in the protection scope of the present invention.

Claims (10)

1. A method for determining a call relation, comprising:
acquiring a call log set generated by an object set, wherein each call log in the call log set is a log generated by an object in the object set in a call process, and each call log comprises a call identifier and an identity identifier;
determining a calling relationship between objects in the object set according to a calling identifier and an identity identifier in the calling log set, wherein the calling identifier is used for identifying a sub-calling process in a calling process, the identity identifier is used for identifying the identity of an object generating the calling log in the sub-calling process, and the calling process comprises at least one sub-calling process;
determining a calling relationship between objects in the object set according to the calling identifier and the identity identifier in the calling log set, including:
under the condition that the call log set comprises a first call identifier and a second call identifier, extracting a prefix of the first call identifier to obtain a first prefix, and extracting a prefix of the second call identifier to obtain a second prefix, wherein each call identifier comprises a prefix, and the prefix of each call identifier is used for identifying a call process to which the sub-call process identified by each call identifier belongs;
determining that two calling processes exist in the objects in the object set under the condition that the first prefix and the second prefix are different;
and determining the calling relationship of the objects in the object set in a first calling process and the calling relationship of the objects in the object set in a second calling process according to the calling identifiers and the identity identifiers in the calling log set, wherein the first calling process is the calling process of the first prefix identifier, and the second calling process is the calling process of the second prefix identifier.
2. The method of claim 1, wherein determining the calling relationship between the objects in the object set according to the calling identifier and the identity identifier in the call log set comprises:
determining that the calling process comprises a sub-calling process under the condition that the calling identifications in the calling log set are the same;
determining a first log and a second log in the call log set, wherein an identity in the first log is used for indicating that an identity of a first object generating the first log in the call process is a call end, and an identity in the second log is used for indicating that an identity of a second object generating the second log in the call process is a called end;
determining the calling relationship between the objects in the set of objects comprises the first object calling the second object in the one calling process.
3. The method of claim 2, further comprising:
determining a target initiation log and a target reception log in the first log, wherein the first log comprises a plurality of logs, the plurality of logs comprises the target initiation log and the target reception log, a timestamp in the target initiation log is a minimum value of timestamps in the first log, and a timestamp in the target reception log is a maximum value of timestamps in the first log;
determining a difference between a timestamp in the receive log and a timestamp in the initiate log;
and determining the difference value as the time consumed for the first object to call the second object.
4. The method of claim 3, further comprising:
determining the number of initiation logs in the first logs, wherein each initiation log is used for indicating that each initiation log is a log generated when the first object initiates the call of the second object;
and determining the number as the calling times of the first object calling the second object.
5. The method according to claim 1, wherein the determining, according to the call identifier and the identity identifier in the call log set, the call relationship of the object in the object set in the first call process comprises:
determining that the first calling process comprises a sub-calling process under the condition that the calling identifications with the first prefix in the calling log set are the same;
determining a third log and a fourth log in the call log set, wherein prefixes of call identifiers in the third log and the fourth log are both the first prefix, an identity in the third log is used for indicating that an identity of a third object generating the third log in the first call process is a call end, and an identity in the fourth log is used for indicating that an identity of a fourth object generating the fourth log in the first call process is a called end;
determining that the third object invokes the fourth object in the first invocation process.
6. The method according to claim 1, wherein each of the call identifiers further includes a suffix, and the suffix of each of the call identifiers is used to identify one of the sub-call procedures in the one of the call procedures, and wherein the determining the call relation of the object in the object set in the first call procedure according to the call identifier and the identity identifier in the call log set comprises:
determining that the first calling process comprises a plurality of sub-calling processes under the condition that the calling identifications with the first prefix in the calling log set are different;
determining a first set of the call log sets, wherein the prefix of the call identifier of each call log in the first set is the first prefix, and repeating the following steps until a current set is empty, the current set is initialized to the first set, and a fifth object, a sixth object and a current object are initialized to be empty:
determining whether a current set is empty, and if the current set is not empty, determining a fifth log and a sixth log in the current set, wherein suffixes of calling identifications of the fifth log and the sixth log are the same, and the length of suffixes of the calling identifications of the fifth log and the sixth log is the maximum value of the length of the calling identification suffixes of the calling logs in the current set;
when the identity recorded in the fifth log is used for indicating that the identity of the object generating the fifth log in the current sub-calling process is a calling end, and the identity recorded in the sixth log is used for indicating that the identity of the object generating the sixth log in the current sub-calling process is a called end, determining the object generating the fifth log as the fifth object and determining the object generating the sixth log as the sixth object, wherein the current sub-calling process is a sub-calling process identified by a suffix of the calling identity of the fifth log;
determining that the fifth object calls the sixth object in the current sub-call process;
determining the fifth object as the current object;
deleting a target log in the current set, and determining the obtained log set as the current set, wherein the suffix of the calling identifier of the target log is the same as the suffix of the calling identifier of the fifth log.
7. The method of claim 6, wherein prior to said determining said fifth object as said current object, said method further comprises:
under the condition that the current object is not empty, and under the condition that the sixth object is the same as a business system to which the current object belongs and the subsystems to which the sixth object belongs are the same, determining that the sixth object calls the current object in the first calling process, and the call of the sixth object to the current object is an internal call in the same subsystem, wherein each calling log further comprises the business system and the subsystem to which the object generating each calling log belongs, and each business system comprises at least one subsystem.
8. An apparatus for determining call relation, comprising:
the system comprises an acquisition module, a storage module and a processing module, wherein the acquisition module is used for acquiring a call log set generated by an object set, each call log in the call log set is a log generated by an object in the object set in a call process, and each call log comprises a call identifier and an identity identifier;
a determining module, configured to determine, according to a call identifier and an identity identifier in the call log set, a call relationship between objects in the object set, where the call identifier is used to identify a sub-call procedure in a call procedure, the identity identifier is used to identify an identity of an object that generates a call log in the sub-call procedure, and the call procedure includes at least one of the sub-call procedures;
the determining module determines the calling relationship among the objects in the object set according to the calling identifier and the identity identifier in the calling log set in the following way:
under the condition that the call log set comprises a first call identifier and a second call identifier, extracting a prefix of the first call identifier to obtain a first prefix, and extracting a prefix of the second call identifier to obtain a second prefix, wherein each call identifier comprises a prefix, and the prefix of each call identifier is used for identifying a call process to which a sub-call process identified by each call identifier belongs;
determining that two calling processes exist in the objects in the object set under the condition that the first prefix and the second prefix are different;
and determining the calling relationship of the objects in the object set in a first calling process and the calling relationship of the objects in the object set in a second calling process according to the calling identifiers and the identity identifiers in the calling log set, wherein the first calling process is the calling process of the first prefix identifier, and the second calling process is the calling process of the second prefix identifier.
9. A storage medium, in which a computer program is stored, wherein the computer program is arranged to perform the method of any of claims 1 to 7 when executed.
10. 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 of any of claims 1 to 7 by means of the computer program.
CN202011325790.2A 2020-11-23 2020-11-23 Method and device for determining call relation, storage medium and electronic device Active CN112416557B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202011325790.2A CN112416557B (en) 2020-11-23 2020-11-23 Method and device for determining call relation, storage medium and electronic device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202011325790.2A CN112416557B (en) 2020-11-23 2020-11-23 Method and device for determining call relation, storage medium and electronic device

Publications (2)

Publication Number Publication Date
CN112416557A CN112416557A (en) 2021-02-26
CN112416557B true CN112416557B (en) 2022-12-30

Family

ID=74777458

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202011325790.2A Active CN112416557B (en) 2020-11-23 2020-11-23 Method and device for determining call relation, storage medium and electronic device

Country Status (1)

Country Link
CN (1) CN112416557B (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113434135B (en) * 2021-06-28 2023-06-16 青岛海尔科技有限公司 Method and device for determining call repeatability of interface, storage medium and electronic device

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020184612A1 (en) * 2001-06-01 2002-12-05 Hunt Joseph R. Runtime configurable caching for component factories
CN103049438A (en) * 2011-10-11 2013-04-17 镇江精英软件科技有限公司 Method for managing data access port
CN107133047A (en) * 2017-05-12 2017-09-05 微梦创科网络科技（中国）有限公司 A kind of project operation measure of criterions method and device
CN107688899A (en) * 2017-08-22 2018-02-13 北京潘达互娱科技有限公司 Business process monitoring method and device
CN109327353B (en) * 2018-09-29 2022-01-11 创新先进技术有限公司 Service flow determination method and device and electronic equipment
CN109753406B (en) * 2018-12-05 2022-06-17 平安科技（深圳）有限公司 Interface performance monitoring method, device, equipment and computer readable storage medium
CN110083581B (en) * 2019-03-12 2024-04-05 平安科技（深圳）有限公司 Log tracing method and device, storage medium and computer equipment
CN110727567B (en) * 2019-09-09 2024-02-02 平安证券股份有限公司 Method, device, computer equipment and storage medium for detecting software quality

Also Published As

Publication number Publication date
CN112416557A (en) 2021-02-26

Similar Documents

Publication Publication Date Title
CN109034993B (en) Account checking method, account checking equipment, account checking system and computer readable storage medium
CN109033471B (en) Information asset identification method and device
CN111400127B (en) Service log monitoring method and device, storage medium and computer equipment
CN105786998A (en) Database middleware system and method for processing data through database middleware system
CN112559475B (en) Data real-time capturing and transmitting method and system
CN111694644A (en) Message processing method and device based on robot operating system and computer equipment
CN111367760A (en) Log collection method and device, computer equipment and storage medium
CN114500690A (en) Interface data processing method and device, electronic equipment and storage medium
CN110928851A (en) Method, device and equipment for processing log information and storage medium
CN107203464B (en) Method and device for positioning service problem
CN116132553A (en) Big data transmission optimization method and system
CN111090268A (en) Data acquisition method and device based on thread division and data acquisition equipment
CN112416557B (en) Method and device for determining call relation, storage medium and electronic device
CN109783330B (en) Log processing method, log display method, and related device and system
CN114416485A (en) Data processing method and device
CN112559525B (en) Data checking system, method, device and server
CN110442439B (en) Task process processing method and device and computer equipment
CN111193631B (en) Information processing method, system, and computer-readable storage medium
CN111694721A (en) Fault monitoring method and device for microservice
CN111367916A (en) Data storage method and device
CN115412592A (en) Service processing system and method
CN111314805B (en) Debugging method and device for intercommunication OMCI (OMCI) messages of GPON (gigabit passive optical network) system
CN104253718A (en) Network test method and device
CN114092246A (en) Problem positioning method and device for financial transaction link
CN113434604A (en) Time sequence database synchronization method, system, equipment 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
GR01 Patent grant
GR01 Patent grant