Link trace method, device, and computer system

Abstract

Embodiments of the present application disclose a link tracking method, device and computer system. The method comprises: collecting call logs generated by a plurality of applications in a process of processing a call request; respectively analyzing the call logs collected in a plurality of time windows to determine a plurality of different system link forms; and comparing analysis results in adjacent time windows to determine information of a system link that has changed. Through the embodiments of the present application, changes in the system link can be found more timely and effectively.

Description

Technical Field

[0001] This application relates to the field of link tracing technology, and in particular to link tracing methods, apparatus and computer systems. Background Technology

[0002] In large-scale business systems, multiple functions are typically provided, each potentially involving various system links. For example, a product information service system might offer functions like adding items to a cart and placing an order. The order placement function could include a standard order link, or a link for placing orders using coupons, and so on. In practice, as the system's business processes improve, these system links frequently undergo various changes, including the addition or deletion of links, and fluctuations in traffic. Continuing with the order placement example, suppose initially only the standard order link and the coupon-based order link were available. Later, a function to select or modify the address before placing an order was added, thus creating a new system link. Alternatively, after a new function is launched, it might be discovered that the traffic for coupon-based orders is significantly higher than that for standard orders, and so on. Timely monitoring of system link changes allows for understanding changes in the system's business dynamics and can also facilitate proactive risk prediction. For instance, if a newly added coupon-based order link relies on a coupon system, an early warning can be issued if the coupon system malfunctions and cannot provide services. Therefore, timely understanding of changes in system links can, to a certain extent, ensure system stability.

[0003] However, in practice, changes to system links are usually driven by developers, while tracking these changes is typically done by operations personnel. One existing technique requires communication between operations and development staff, with developers informing operations of specific system link changes, including which functions exist in the system and which links exist within those functions. However, this approach is inefficient and heavily reliant on the accuracy of the developers' descriptions. In practice, developers often lack accuracy in their verbal descriptions of specific functions or links, frequently omitting features, links, or making errors in the description of nodes and timing relationships within a link. This can lead to oversights by operations personnel during link tracking.

[0004] Another existing technology provides a distributed tracing system for operations personnel. Developers can provide operations personnel with the application name, service name, and method name at specific function entry points. Operations personnel can then input this information into the distributed tracing system. During the processing of business requests, the distributed tracing system records the process, and operations personnel can analyze changes in the distributed tracing network based on this information. However, this approach requires operations personnel to actively identify changes in the distributed tracing network, and it cannot quickly detect changes in the system's distributed tracing network. Furthermore, it requires the personnel performing distributed tracing identification to be very familiar with the system, and even then, the identification efficiency is relatively low, making it difficult to respond to changes in the system's distributed tracing network.

[0005] Therefore, how to detect changes in system links more promptly and effectively has become a technical problem that needs to be solved by those skilled in the art. Summary of the Invention

[0006] This application provides a link tracing method, apparatus, and computer system, which can detect changes in system links more promptly and effectively.

[0007] This application provides the following solution:

[0008] A link tracing method, comprising:

[0009] Collect call logs generated by multiple applications during the process of processing call requests;

[0010] The call logs collected in multiple time windows were analyzed to determine several different system link patterns;

[0011] By comparing the analysis results in adjacent time windows, information about the changed system links can be determined.

[0012] A link tracing method, comprising:

[0013] During the processing of call requests, call logs are generated;

[0014] The call logs are provided to the link tracing system so that the link tracing system can analyze the call logs collected in multiple time windows, determine multiple different system link patterns, and determine the information of the changed system links by comparing the calculation results in adjacent time windows.

[0015] A link optimization method, comprising:

[0016] Collect call logs generated by multiple applications during the process of processing call requests;

[0017] The call logs collected in multiple time windows were analyzed to determine several different system link patterns;

[0018] By comparing the calculation results in adjacent time windows, information about the changed system links can be determined;

[0019] The changed system links are then optimized.

[0020] A method for determining the system link configuration, comprising:

[0021] Collect call logs generated by multiple applications during the process of processing call requests;

[0022] By analyzing the collected call logs, several different system link patterns were identified.

[0023] A system link analysis method, comprising:

[0024] Collect call logs generated by multiple applications during the process of processing call requests;

[0025] By analyzing the collected call logs, several different system link patterns were identified;

[0026] By comparing the call log information collected in multiple time windows, we can determine the new applications that have been added relative to the previous time window.

[0027] By analyzing the call logs of the newly added application, the impact of the newly added application on the system link can be determined.

[0028] A method for disseminating event information, comprising:

[0029] Collect call logs generated by multiple applications during the process of processing call requests;

[0030] The call logs collected in multiple time windows were analyzed to determine several different system link patterns;

[0031] By comparing the calculation results in adjacent time windows, the system links where traffic changes and the corresponding time information are determined, and the activity information that caused the traffic change is also determined.

[0032] The system link where the traffic changes, the corresponding time information, and the activity information are provided to the target client so that the target client can deliver the activity information at the specified time.

[0033] A link tracing device, comprising:

[0034] The log collection unit is used to collect call logs generated by multiple applications during the process of processing call requests;

[0035] The log analysis unit is used to analyze call logs collected in multiple time windows to determine multiple different system link patterns;

[0036] The comparison unit is used to determine information about changed system links by comparing analysis results in adjacent time windows.

[0037] A link tracing device, comprising:

[0038] The log generation unit is used to generate call logs during the processing of call requests;

[0039] The log providing unit is used to provide the call logs to the link tracing system, so that the link tracing system can analyze the call logs collected in multiple time windows, determine multiple different system link patterns, and determine the information of the changed system links by comparing the calculation results in adjacent time windows.

[0040] A link optimization device, comprising:

[0041] The log collection unit is used to collect call logs generated by multiple applications during the process of processing call requests;

[0042] The log analysis unit is used to analyze call logs collected in multiple time windows to determine multiple different system link patterns;

[0043] The comparison unit is used to determine the information of the changed system links by comparing the calculation results in adjacent time windows;

[0044] The link optimization unit is used to optimize the changed system links.

[0045] A device for determining the configuration of a system link, comprising:

[0046] The log collection unit is used to collect call logs generated by multiple applications during the process of processing call requests;

[0047] The log analysis unit is used to analyze the collected call logs to determine multiple different system link patterns.

[0048] A system link analysis device, comprising:

[0049] The log collection unit is used to collect call logs generated by multiple applications during the process of processing call requests;

[0050] The log analysis unit is used to determine multiple different system link patterns by analyzing the collected call logs;

[0051] The comparison unit is used to determine the new applications that have been added relative to the previous time window by comparing the call log information collected in multiple time windows.

[0052] The impact analysis unit is used to determine the impact of the newly added application on the system link by analyzing the call logs of the newly added application.

[0053] An activity information dissemination device, comprising:

[0054] The log collection unit is used to collect call logs generated by multiple applications during the process of processing call requests;

[0055] The log analysis unit is used to analyze call logs collected in multiple time windows to determine multiple different system link patterns;

[0056] The comparison unit is used to determine the system links whose traffic has changed and the corresponding time information by comparing the calculation results in adjacent time windows, and to determine the activity information that caused the traffic change;

[0057] An information providing unit is used to provide the target client with the system link where the traffic changes, the corresponding time information, and the activity information, so that the target client can deliver the activity information at the specified time.

[0058] A computer system, comprising:

[0059] One or more processors; and

[0060] A memory associated with the one or more processors, the memory storing program instructions that, when read and executed by the one or more processors, perform the following operations:

[0061] Collect call logs generated by multiple applications during the process of processing call requests;

[0062] The call logs collected in multiple time windows were analyzed to determine several different system link patterns;

[0063] By comparing the analysis results in adjacent time windows, information about the changed system links can be determined.

[0064] According to the specific embodiments provided in this application, the following technical effects are disclosed:

[0065] This application's embodiments enable the collection of call logs generated by multiple applications during the processing of call requests. Call logs collected across multiple time windows are aggregated and recursively processed to determine multiple different system link configurations. By comparing the results of calculations in adjacent time windows, information about changed system links can be identified. This information can be provided to operations personnel to promptly grasp changes in system links and business scenarios, confirm the status of business systems dependent on various system links, and provide timely warnings in case of faults, thereby ensuring system stability.

[0066] In the preferred implementation, the specific system entry points can be determined by calculating the call logs, as well as the changes in the specific link branches under various system entry points, thereby enabling operators to better understand various business scenarios more comprehensively.

[0067] Of course, any product implementing this application does not necessarily need to achieve all of the advantages described above at the same time. Attached Figure Description

[0068] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0069] Figure 1 This is a schematic diagram of the system architecture provided in the embodiments of this application;

[0070] Figure 2 This is a flowchart of the first method provided in the embodiments of this application;

[0071] Figure 3-1 , 3-2 This is a schematic diagram of the link changes provided in the embodiments of this application;

[0072] Figure 4-1 , 4-2 This is a schematic diagram illustrating an example of link change provided in an embodiment of this application;

[0073] Figure 5 This is a flowchart of the second method provided in the embodiments of this application;

[0074] Figure 6 This is a flowchart of the third method provided in the embodiments of this application;

[0075] Figure 7 This is a flowchart of the fourth method provided in the embodiments of this application;

[0076] Figure 8 This is a flowchart of the fifth method provided in the embodiments of this application;

[0077] Figure 9 This is a flowchart of the sixth method provided in the embodiments of this application;

[0078] Figure 10 This is a schematic diagram of the first device provided in the embodiments of this application;

[0079] Figure 11 This is a schematic diagram of the second device provided in the embodiments of this application;

[0080] Figure 12 This is a schematic diagram of the third device provided in the embodiments of this application;

[0081] Figure 13 This is a schematic diagram of the fourth device provided in the embodiments of this application;

[0082] Figure 14 This is a schematic diagram of the fifth device provided in the embodiments of this application;

[0083] Figure 15 This is a schematic diagram of the sixth device provided in the embodiments of this application;

[0084] Figure 16 This is a schematic diagram of the computer system provided in the embodiments of this application. Detailed Implementation

[0085] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0086] This application provides a more automated method for link tracing. By deploying a link tracing system, call logs generated by the application during request processing can be collected. Then, by aggregating and recursively calculating these logs, multiple different system link branch patterns can be identified. By comparing the calculation results in adjacent time windows, system link changes can be determined. This eliminates the need for users to manually input application names, service names, method names, etc., at the function entry point to obtain information about system link changes, enabling alerts and other processing. Therefore, efficiency is improved and labor costs are reduced.

[0087] In practical implementation, from a system architecture perspective, such as Figure 1As shown, a system link tracing system can be deployed. This system can collect call logs from multiple applications, then perform aggregation and recursive calculations to ultimately determine the changes in the system link. The system link tracing system can be deployed on a single server, or on the server hosting multiple applications or one of those applications, etc.

[0088] The specific implementation schemes provided in the embodiments of this application will be described in detail below.

[0089] First, this application provides a system link tracing method, see [link to relevant documentation]. Figure 2 The method may specifically include:

[0090] S201: Collect call logs generated by multiple applications during the process of processing call requests;

[0091] The applications mentioned here can be multiple applications under the same business unit. That is, multiple applications may be deployed under the same business unit. These applications may call each other during the process of handling call requests, thus forming a specific system link. Therefore, the system link can be traced by tracing the call relationships between applications. Specifically, the multiple applications may include multiple applications in the commodity object information service system, and of course, may also include multiple applications in other systems or platforms.

[0092] The specific call logs can be generated within a specific application, and may include trace logs, etc. Trace is used by RabbitMQ (an open-source message broker and queue server used to share data between completely different applications via common protocols) to record every message sent, making it easier for RabbitMQ developers to debug and troubleshoot.

[0093] In this embodiment, specific applications can collect log information such as traces after generating them, and submit it to the system tracing system for calculation. In this way, the tracing system can collect logs generated by multiple specific applications. Since these logs are typically generated during application invocation, the upstream and downstream relationships between applications during invocation can be determined through calculation of this log information, thereby forming a specific system link.

[0094] It's important to note that during the actual processing of a call request, the request is handled by a specific method within a specific service of a specific application. Therefore, the collected call logs will include not only the name of the called application but also the specific method within that service of that application. Furthermore, during the call to a specific method of a specific service within an application, the call request may also carry parameters. For example, when calling the method for placing an order using a coupon, the request might include specific coupon information as a parameter. This parameter information, along with the return value from the called party, can also be recorded in the call logs and collected by the tracing system. Subsequently, when necessary, this parameter and return value information can be provided to operations personnel to provide them with detailed tracing information, allowing them to more intuitively identify specific scenario information, and so on.

[0095] S202: Analyze the call logs collected in multiple time windows to determine the different system link branch patterns;

[0096] After collecting specific call logs from multiple applications, the collected logs can be analyzed and calculated. In practice, operations personnel can pre-configure the required time window information in the system; for example, it can be set to a week, a day, or an hour, etc., depending on specific needs. After setting the time window information, the tracing system can analyze the collected call log information within different time windows. Specifically, it can aggregate and recursively calculate the call logs to determine the mutual calls between applications within the same time window. Furthermore, each application can be treated as a node in the chain and linked together according to the call sequence to determine a specific system chain. For example, when calculating the logs of four applications, namely Application 1, Application 2, Application 3, and Application 4, it is found that method M1 under service S1 in Application 1 calls method 2 under service 2 in Application 2. Then, service 2 and method 2 in Application 2 call service 4 and method 4 in Application 4. Thus, a system chain can be determined as: Application 1 (service 1, method 1) -> Application 2 (service 2, method 2) -> Application 4 (service 4, method 4), and so on.

[0097] It should be noted that the system link may include multiple nodes, each corresponding to one of the applications, and at least some nodes have upstream and downstream dependencies. By analyzing the above call logs, the upstream and downstream dependencies between nodes can be determined, thereby identifying the specific system link.

[0098] In addition, the multiple applications may belong to the same business unit in the target business system, and different system links correspond to different application scenarios under the same business unit, forming a network structure between the nodes of different system links.

[0099] S203: By comparing the analysis results in adjacent time windows, determine the information of the system links that have changed.

[0100] After aggregating and recursively calculating the call logs within different time windows, we can determine which system links exist within each time window. Then, by comparing the calculation results of adjacent time windows, we can determine the changes in system links. For example, if a new link is found in a certain time window as Application 1 (Service 1, Method 1) -> Application 2 (Service 2, Method 3), then this link can be identified as a new link, and we can notify the operations staff.

[0101] In addition to newly added system links compared to the previous time window, specific change information can also include system links that no longer appear in the new time window, i.e., links that were deleted compared to the previous time window. Furthermore, in practical implementation, this can also include links whose traffic has changed significantly compared to the previous time window. Regarding system link traffic, it can primarily be expressed as the number of times the same system link appears repeatedly within the same time window. If a system link appears frequently within a certain time window, it indicates that the traffic on that link is relatively high. If the change in traffic of a system link compared to the previous time window exceeds a certain threshold, this information can also be notified to operations personnel, and so on.

[0102] In specific implementation, multiple system entry points can be determined based on the calculation results. Then, when statistically analyzing changes in system links, the changes in various link branches under the same system entry point can be statistically analyzed separately. Specifically, system link branches with the same system entry point within the same time window can be grouped, and information on system link branches that have changed within the groups corresponding to the same system entry point between adjacent time windows can be determined. The information on system link branches that have changed can specifically include: information on system link branches that have been added, deleted, or whose percentage change exceeds a threshold compared to the previous time window.

[0103] For example, when calculating the logs of four applications (Application 1, Application 2, Application 3, and Application 4), an entry point, Application 1 (Service 1, Method 1), is found through recursive calculation. Within the first time window, two link branch patterns are identified, such as... Figure 3-1As shown, these are link 1: Application 1 (Service 1, Method 1) -> Application 2 (Service 2, Method 2) -> Application 4 (Service 4, Method 4), and link 2: Application 1 (Service 1, Method 1) -> Application 3 (Service 3, Method 3); and the two branch patterns determined within the second time window are as follows: Figure 3-2 As shown, these are link 3: Application 1 (Service 1, Method 1) -> Application 2 (Service 2, Method 3), and link 2: Application 1 (Service 1, Method 1) -> Application 3 (Service 3, Method 3). The calculation results show that compared to the previous time window, system link 3 was added, and system link 1 was deleted. Furthermore, the addition and deletion of these links caused changes in link traffic. For example, in the first time window, the traffic of link 1 was F1, and the traffic of link 2 was F2; ​​in the second time window, link 1 was deleted, link 3 was added, and the traffic of link 3 became F3, while the traffic of link 2 became F4. It is evident that although link 2 was neither deleted nor added between the two time windows, its traffic changed because other links under the same system entry point were deleted or added. For example, the addition of a link for paying with coupons changed the traffic of the ordinary payment link, and so on. Therefore, this change information should be communicated to operations personnel. Additionally, if no new or deleted link branches occur between two adjacent time windows, the traffic situation of different link branches under the same system entry point can still be calculated. Specifically, the number of times the same link branch under the same system entry point appears within the same time window can be counted. Then, the proportion of different link branches under the same system entry point within that event window can be calculated, and this proportion can be used as the traffic proportion of a specific link branch. If it is found that the proportion of a certain link branch under a certain system entry point has changed significantly compared to the previous time window within a certain time window, the relevant operations personnel and associated clients can also be notified, and so on.

[0104] In practical implementation, the specific applications involved in each link can be determined based on the actual scenario. For example, in a transaction scenario within a commodity object information service system, the specific applications involved may include commodity object transaction applications, payment applications, etc. If coupon payments are supported, coupon applications may also be involved. Changes in the specific link may be reflected in changes to the payment link. For example, ... Figure 4-1As shown, within the first time window, there is only one payment chain. That is, after initiating a payment request through the product object transaction application, the application can call the payment method under the specific payment service of the payment application to complete the payment, thus forming a payment chain between the product object transaction application and the payment application. In the next time window, because the developers added a new payment method for users—namely, using coupons for payment—the specific payment chain becomes as follows: Figure 4-2 As shown, there are now two paths, with a new payment path added: "Product Transaction Application -> Coupon Application -> Payment Application". Furthermore, this new path will affect the traffic of the original path 1; for example, it may experience a significant decrease, etc.

[0105] Furthermore, in practical implementation, after identifying the system entry points, this information can be provided to the clients associated with the operations personnel. This allows operations personnel to know the exact number of system entry points, which serves as the "denominator" for the system entry point count. This information can then be used to obtain all application-related information from the management centers of these architectural components, and as a reference denominator for system link analysis and business scenario analysis, ensuring the completeness of the analysis. In other words, in this embodiment, operations personnel may not know the total number of system entry points beforehand. However, this embodiment allows for the analysis of specific system entry points and their provision to operations personnel. This enables them to analyze the specific link branches under each system entry point, preventing any system entry point from being missed. The system entry points described in this embodiment can include various forms, such as microservices, scheduled tasks, web services, and messaging. Each specific system entry point can be implemented through a specific method within a specific service in an application. The triggering methods for system entry points can include user operation triggering, timed triggering, etc.

[0106] Furthermore, as mentioned earlier, the collected call logs can also include parameter information carried in the specific call request, as well as the return value information of the specific called application after processing the call request. This parameter and return value information can typically reflect business scenario information to a certain extent. For example, if the parameters include the user's selected coupon type information, and the return value includes price information before and after the discount, etc., it can be determined that the business scenario corresponding to this link is related to payment using coupons, and so on. Therefore, in the preferred embodiment of this application, if a system link changes, this parameter and return value information can also be sampled, and while providing change information, this parameter and return value information can also be provided to operations personnel, making it easier and faster for operations personnel to analyze system links and business scenarios.

[0107] In summary, through the embodiments of this application, it is possible to collect call logs generated by multiple applications during the processing of call requests, and to aggregate and recursively calculate call logs collected in multiple time windows to determine multiple different system link patterns. Then, by comparing the calculation results in adjacent time windows, the information of the changed system links can be identified. This information can be provided to operations personnel, enabling them to promptly grasp changes in system links and business scenarios, confirm the status of business systems dependent on various system links, and provide timely warnings in case of failures, thereby ensuring system stability.

[0108] In the preferred implementation, the specific system entry points can be determined by calculating the call logs, as well as the changes in the specific link branches under various system entry points, thereby enabling operators to better understand various business scenarios more comprehensively.

[0109] Example 2

[0110] This second embodiment provides a link tracing method from a specific application perspective. See [link to example]. Figure 5 The method may specifically include:

[0111] S501: Generate call logs during the process of processing call requests;

[0112] S502: The call logs are provided to the link tracing system so that the link tracing system can analyze the call logs collected in multiple time windows, determine multiple different system link patterns, and determine the information of the changed system links by comparing the calculation results in adjacent time windows.

[0113] For the parts of this embodiment that are not described in detail, please refer to the description in the aforementioned embodiment one, which will not be repeated here.

[0114] Example 3

[0115] In the aforementioned Embodiments 1 and 2, various system link patterns can be identified by analyzing the call logs of multiple applications, and system links that have changed relative to the previous time window can be identified. After identifying the changed system links, the specific change information can be provided to the specific operations personnel, who can then further analyze the applications included in the specific links. The above method is a non-real-time system link processing method. However, in this Embodiment 3, the system link discovery and tracking method can be directly deployed to specific business systems, making the link tracking system a link optimization system. After discovering specific changed system links, the link optimization system can directly optimize the related applications in the system links, thereby achieving real-time link optimization.

[0116] Specifically, Embodiment 3 of this application provides a link optimization method, see [link to embodiment]. Figure 6 The method may specifically include:

[0117] S601: Collect call logs generated by multiple applications during the process of processing call requests;

[0118] S602: Analyze the call logs collected in multiple time windows to determine multiple different system link patterns;

[0119] S603: By comparing the calculation results in adjacent time windows, determine the information of the changed system links;

[0120] S604: Optimize the changed system links.

[0121] Steps S601 to S603 may be the same as steps S201 to S203 in Embodiment 1, and will not be described in detail here.

[0122] Upon detecting changes in system links, optimization can be performed in real time. Specifically, for newly added system links compared to the previous time window, it can be determined whether the servers corresponding to the applications included in the newly added system link are operating normally. If not, corresponding prompts can be generated and provided to the relevant application administrators. For system links deleted compared to the previous time window, it can be determined whether the resources occupied by the deleted system link have been released. If not, the corresponding resources can be released. For system links with increased traffic compared to the previous time window, it can be determined whether the server load capacity corresponding to each application included in the system link is sufficient. If insufficient load capacity is found, additional servers or virtual machines can be deployed.

[0123] Example 4

[0124] In the foregoing embodiments, after collecting the application's call logs, the system link structure can be determined, which is then primarily used to analyze changes in the system link structure. However, in practical applications, there may be needs to analyze only the system link structure. In such cases, the method provided in this application's embodiments can also be used to determine the system link structure. Therefore, this fourth embodiment provides a method for determining the system link structure, see [link to previous embodiment]. Figure 7 The method may specifically include:

[0125] S701: Collects call logs generated by multiple applications during the process of processing call requests;

[0126] S702: By analyzing the collected call logs, multiple different system link configurations can be determined.

[0127] In practice, multiple system entry points can be determined based on the analysis results of the call logs; in this way, the information of the system link branches included under the same system entry point can be determined.

[0128] Example 5

[0129] In the aforementioned embodiments, after collecting call logs from multiple applications, the primary purpose is to determine the specific system link structure. It can also analyze changes in the system link and even optimize changed system links, etc. In this fifth embodiment, based on the discovered system link, newly added applications can be identified using the collected call logs. Then, by analyzing the call logs of these applications, the impact of the applications on the system link can be determined. For details, see [link to specific examples]. Figure 8 This fifth embodiment provides a system link analysis method, which may specifically include:

[0130] S801: Collects call logs generated by multiple applications during the process of processing call requests;

[0131] S802: By analyzing the collected call logs, multiple different system link configurations can be determined;

[0132] S803: By comparing the call log information collected in multiple time windows, determine the new applications that have been added relative to the previous time window;

[0133] S804: By analyzing the call logs of the newly added application, determine the impact of the newly added application on the system link.

[0134] Specifically, we can identify the system links where the new application resides, and then analyze whether the traffic of these system links has changed relative to the previous time window, etc., in order to analyze the impact of the application on the specific system links.

[0135] Example 6

[0136] In this sixth embodiment, based on the discovery of system links, if it is determined that the traffic of a certain system link has changed, such as a significant increase or decrease in traffic, the time information corresponding to this change can also be determined, along with the activity information that caused the traffic change. For example, if a link's traffic increases significantly due to a limited-time promotion, it proves that the link is highly sensitive to the promotion. Furthermore, due to factors such as the store's actual operating conditions, the start time of such promotions may be limited. For instance, a store selling fresh produce needs to sell out its stock before closing time, so the promotion cannot start too late; conversely, starting too early might result in insignificant traffic changes due to insufficient foot traffic. The solution provided in this embodiment allows for monitoring of traffic changes in specific links and identifying the specific activity information and corresponding time information that caused the traffic change. This guides operators or store managers to launch specific activities at more appropriate times, thereby achieving better operational results.

[0137] Therefore, this application provides a method for disseminating activity information, see below. Figure 9 The method may specifically include:

[0138] S901: Collect call logs generated by multiple applications during the process of processing call requests;

[0139] S902: Analyze the call logs collected in multiple time windows to determine multiple different system link patterns;

[0140] S903: By comparing the calculation results in adjacent time windows, determine the system links where traffic changes and the corresponding time information, and determine the activity information that caused the traffic change;

[0141] S904: Provide the target client with the system link where the traffic changes, the corresponding time information, and the activity information, so that the target client can deliver the activity information at the specified time.

[0142] For the parts of Embodiments 2 to 6 that are not described in detail above, please refer to the description in Embodiment 1 above, which will not be repeated here.

[0143] Corresponding to Embodiment 1, this application also provides a link tracing device, see [link to embodiment 1]. Figure 10 The device may specifically include:

[0144] Log collection unit 1001 is used to collect call logs generated by multiple applications during the process of processing call requests;

[0145] The log analysis unit 1002 is used to analyze the call logs collected in multiple time windows to determine multiple different system link patterns.

[0146] The comparison unit 1003 is used to determine the information of the changed system links by comparing the analysis results in adjacent time windows.

[0147] The system link includes multiple nodes, each node corresponding to one application, and at least some nodes have upstream and downstream dependencies.

[0148] The multiple applications belong to the same business unit in the target business system. Different system links correspond to different application scenarios under the same business unit, and the nodes of different system links form a network structure.

[0149] The log analysis unit can be specifically used for:

[0150] The call logs collected from multiple time windows are aggregated and recursively processed to determine multiple different system link patterns.

[0151] In a specific implementation, the device may further include:

[0152] The system entry point determination unit is used to determine multiple system entry points based on the analysis results of the call logs.

[0153] The comparison unit is specifically used for:

[0154] Determine information about system link branches that have changed under the same system entry point.

[0155] Furthermore, the comparison unit can specifically be used for:

[0156] Group system link branches with the same system entry within the same time window, and determine the information of system link branches that have changed in the groups corresponding to the same system entry between adjacent time windows.

[0157] The information on the changed system link branches includes: information on system link branches that have been added, deleted, or whose percentage change is higher than a threshold relative to the previous time window.

[0158] Additionally, the device may also include:

[0159] The first information providing unit is used to provide the target client with the information of the determined system entry point.

[0160] The second information providing unit is used to provide the target client with information about the changed system links.

[0161] Additionally, the device may also include:

[0162] The sampling unit is used to sample the parameter information carried in the call request and the return value information of the application after processing the call request for the system link that has changed.

[0163] The parameter information providing unit is used to provide the parameter information and return value information corresponding to the system link when providing information about the changed system link.

[0164] The multiple applications mentioned above include multiple applications within the commodity object information service system.

[0165] Corresponding to Embodiment 2, this application also provides a link tracing device, see [link to embodiment 2]. Figure 11 The device may include:

[0166] Log generation unit 1101 is used to generate call logs during the process of processing call requests;

[0167] The log providing unit 1102 is used to provide the call logs to the link tracing system so that the link tracing system can analyze the call logs collected in multiple time windows, determine multiple different system link patterns, and determine the information of the changed system links by comparing the calculation results in adjacent time windows.

[0168] Corresponding to Embodiment 3, this application also provides a link optimization device, see [link to embodiment 3]. Figure 12 The device may include:

[0169] Log collection unit 1201 is used to collect call logs generated by multiple applications during the process of processing call requests;

[0170] The log analysis unit 1202 is used to analyze the call logs collected in multiple time windows to determine multiple different system link patterns;

[0171] The comparison unit 1203 is used to determine the information of the changed system links by comparing the calculation results in adjacent time windows;

[0172] The link optimization unit 1204 is used to optimize the changed system links.

[0173] Specifically, the link optimization unit can be used for:

[0174] For any new system links added relative to the previous time window, determine whether the server status of the application included in the new system link is running normally. If not, generate the corresponding prompt information and provide it to the corresponding application manager.

[0175] Alternatively, for system links that were deleted relative to the previous time window, determine whether the resources occupied by the deleted system links have been released. If not, release the corresponding resources.

[0176] Alternatively, for system links where traffic has increased relative to the previous time window, determine whether the server load capacity corresponding to each application on the system link is sufficient. If the load capacity is insufficient, increase the deployment of servers or virtual machines.

[0177] Corresponding to Embodiment 4, this application also provides a device for determining the system link configuration, see [link to embodiment]. Figure 13 The device may include:

[0178] Log collection unit 1301 is used to collect call logs generated by multiple applications during the process of processing call requests;

[0179] The log analysis unit 1302 is used to analyze the collected call logs to determine multiple different system link patterns.

[0180] Specifically, based on the analysis results of the call logs, multiple system entry points are determined. The log analysis unit is used to determine the information of the system link branches included under the same system entry point.

[0181] Corresponding to Embodiment 5, this application also provides a system link analysis device, see [link to embodiment 5]. Figure 14 The device may include:

[0182] Log collection unit 1401 is used to collect call logs generated by multiple applications during the process of processing call requests;

[0183] The log analysis unit 1402 is used to analyze the collected call logs to determine multiple different system link patterns;

[0184] The comparison unit 1403 is used to determine the application that has been added relative to the previous time window by comparing the call log information collected in multiple time windows.

[0185] The impact analysis unit 1404 is used to determine the impact of the newly added application on the system link by analyzing the call logs of the newly added application.

[0186] Corresponding to Embodiment Six, this application also provides an activity information delivery device, see [link to embodiment six]. Figure 15 The device may include:

[0187] Log collection unit 1501 is used to collect call logs generated by multiple applications during the process of processing call requests;

[0188] Log analysis unit 1502 is used to analyze call logs collected in multiple time windows to determine multiple different system link patterns;

[0189] The comparison unit 1503 is used to determine the system links whose traffic has changed and the corresponding time information by comparing the calculation results in adjacent time windows, and to determine the activity information that caused the traffic change.

[0190] The information providing unit 1504 is used to provide the system link where the traffic changes, the corresponding time information, and the activity information to the target client so that the target client can deliver the activity information at the time.

[0191] In addition, embodiments of this application also provide a computer system, including:

[0192] One or more processors; and

[0193] A memory associated with the one or more processors, the memory storing program instructions that, when read and executed by the one or more processors, perform the following operations:

[0194] Collect call logs generated by multiple applications during the process of processing call requests;

[0195] The call logs collected in multiple time windows were analyzed to determine several different system link patterns;

[0196] By comparing the analysis results in adjacent time windows, information about the changed system links is determined. Figure 16 The architecture of an electronic device is illustrated, which may include a processor 1610, a video display adapter 1611, a disk drive 1612, an input / output interface 1613, a network interface 1614, and a memory 1620. The processor 1610, video display adapter 1611, disk drive 1612, input / output interface 1613, network interface 1614, and memory 1620 can communicate with each other via a communication bus 1630.

[0197] The processor 1610 can be implemented using a general-purpose CPU (Central Processing Unit), microprocessor, application-specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to achieve the technical solution provided in this application.

[0198] The memory 1620 can be implemented in the form of ROM (Read Only Memory), RAM (Random Access Memory), static storage device, dynamic storage device, etc. The memory 1620 can store the operating system 1621 for controlling the operation of the electronic device 1600, and the basic input / output system (BIOS) for controlling the low-level operations of the electronic device 1600. Additionally, it can store a web browser 1623, a data storage management system 1624, and a link tracing system 1625, etc. The aforementioned link tracing system 1625 can be the application program that specifically implements the aforementioned steps in this embodiment. In summary, when implementing the technical solution provided in this application through software or firmware, the relevant program code is stored in the memory 1620 and executed by the processor 1610.

[0199] The input / output interface 1613 is used to connect input / output modules to realize information input and output. Input / output modules can be configured as components within the device (not shown in the figure) or externally connected to the device to provide corresponding functions. Input devices may include keyboards, mice, touchscreens, microphones, various sensors, etc., while output devices may include displays, speakers, vibrators, indicator lights, etc.

[0200] Network interface 1614 is used to connect a communication module (not shown in the figure) to enable communication between this device and other devices. The communication module can communicate via wired means (such as USB, Ethernet cable, etc.) or wireless means (such as mobile network, WIFI, Bluetooth, etc.).

[0201] Bus 1630 includes a pathway for transmitting information between various components of the device, such as processor 1610, video display adapter 1611, disk drive 1612, input / output interface 1613, network interface 1614, and memory 1620.

[0202] In addition, the electronic device 1600 can also obtain information on specific acquisition conditions from the virtual resource object acquisition condition information database 1641 for condition judgment, etc.

[0203] It should be noted that although the above-described device only shows the processor 1610, video display adapter 1611, disk drive 1612, input / output interface 1613, network interface 1614, memory 1620, bus 1630, etc., in specific implementations, the device may also include other components necessary for normal operation. Furthermore, those skilled in the art will understand that the above-described device may only include the components necessary for implementing the solution of this application, and does not necessarily include all the components shown in the figures.

[0204] As can be seen from the above description of the embodiments, those skilled in the art can clearly understand that this application can be implemented by means of software plus necessary general-purpose hardware platforms. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in various embodiments or some parts of the embodiments of this application.

[0205] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, for system or system embodiments, since they are basically similar to method embodiments, the description is relatively simple, and relevant parts can be referred to the descriptions in the method embodiments. The systems and system embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without creative effort.

[0206] The link tracing method, apparatus, and computer system provided in this application have been described in detail above. Specific examples have been used to illustrate the principles and implementation methods of this application. The descriptions of the embodiments above are only for the purpose of helping to understand the method and its core ideas. Furthermore, those skilled in the art will recognize that, based on the ideas of this application, there will be changes in the specific implementation methods and application scope. Therefore, the content of this specification should not be construed as a limitation of this application.

Claims

1. A link trace method characterized by, The application discloses a method for analyzing the change of different system links associated with a statistical service system, wherein the service system provides multiple functions, and each function is associated with multiple different system links. Collecting call logs generated by multiple applications during the process of processing call requests, wherein the multiple applications belong to at least one service system; Analyzing the call logs collected in multiple time windows respectively to determine the forms of multiple different system links associated with the at least one service system respectively; wherein the multiple different system links associated with the same service system are embodied as the call timing relationship between multiple applications in the service system obtained according to the call logs of the multiple applications in the service system; By comparing the analysis results in adjacent time windows, the information of the system link changed in the at least one service system is determined, so as to sort the service scene change of the service system according to the information of the system link changed, or to confirm the service system state dependent on the system link and to give a warning in the case of failure.

2. The method of claim 1, wherein The system link includes multiple nodes, and each node corresponds to an application, wherein there is an upstream and downstream dependency relationship between at least some nodes.

3. The method of claim 2, wherein The multiple applications belong to the same business unit in the target service system, different system links correspond to different application scenarios under the same business unit, and the nodes of different system links form a mesh structure.

4. The method of claim 1, wherein The analysis of the call logs collected in multiple time windows includes: Aggregating and recursively operating the call logs collected in multiple time windows to determine the forms of multiple different system links.

5. The method of claim 1, wherein, Further comprising: Determining multiple system entries according to the analysis results of the call logs; The determination of the information of the system link changed includes: Determining the information of the system link branch changed under the same system entry.

6. The method of claim 5, wherein The determination of the information of the system link branch changed under the same system entry includes: Grouping the system link branches with the same system entry in the same time window, and determining the information of the system link branch changed between adjacent time windows in the group corresponding to the same system entry.

7. The method of claim 6, wherein The information of the system link branch changed includes: the information of the system link branch newly added, deleted and / or with a change degree higher than a threshold in the previous time window.

8. The method of claim 5, wherein The information of the determined system entry is provided to a target client.

9. The method according to any one of claims 1 to 8, characterized in that, Further comprising: Providing the information of the system link changed to a target client.

10. The method of claim 9, wherein, Further comprising: For the system link changed, sampling the parameter information carried in the call request and the return value information after the application processes the call request; The method further comprises: In providing the information of the changed system link, the parameter information corresponding to the system link and the return value information are provided.

11. The method of any one of claims 1-8, wherein the plurality of applications comprises a plurality of applications in a commodity object information service system. The method for counting the change of different system links associated under a business system, the business system providing multiple functions, multiple different system links existing under each function, the method comprising:

12. A link-tracing method characterized by, In the process of multiple applications processing call requests, call logs are generated, the multiple applications belonging to at least one business system; The call logs are provided to a link tracking system, so that the link tracking system respectively analyzes the call logs collected in multiple time windows, determines the multiple different system link forms respectively associated under the at least one business system, and determines the information of the changed system link in the at least one business system by comparing the calculation results in adjacent time windows, so as to comb the business scenario change of the business system according to the information of the changed system link, or confirm the business system state dependent on the system link and give a warning in the case of failure; Wherein, the multiple different system links associated under the same business system are embodied as the call timing relationship between the multiple applications under the business system obtained according to the call logs of the multiple applications included in the business system. The method for counting the change of different system links associated under a business system, performing link optimization processing, the business system providing multiple functions, multiple different system links existing under each function, the method comprising:

13. A method of link optimization, the method comprising: Collecting call logs generated in the process of multiple applications processing call requests, the multiple applications belonging to at least one business system; Respectively analyzing the call logs collected in multiple time windows, determining the multiple different system link forms respectively associated under the at least one business system; wherein, the multiple different system links associated under the same business system are embodied as the call timing relationship between the multiple applications under the business system obtained according to the call logs of the multiple applications included in the business system; By comparing the calculation results in adjacent time windows, the information of the changed system link in the at least one business system is determined; Optimizing the changed system link.

14. The method of claim 13, wherein the optimizing the changed system link comprises: For the newly added system link relative to the last time window, determining whether the server state corresponding to the application included in the newly added system link is normally running, and if not, generating corresponding prompt information and providing it to the corresponding application management party.

15. The method of claim 13, wherein the optimizing the changed system link comprises: For the deleted system link relative to the last time window, determining whether the resources occupied by the deleted system link are released, and if not, releasing the corresponding resources. ​ ​ ​ 16. The method of claim 13, wherein the optimizing the changed system link comprises: for a system link with increased traffic relative to a previous time window, determining whether server load capacity of each application included in the system link is sufficient, and if not, increasing deployment of servers or virtual machines. A method for determining associated system links under a business system, the business system providing multiple functions, and under each function, multiple different system links, the method comprising:

17. A method for determining the configuration of a system link, characterized in that, collecting call logs generated by multiple applications in processing call requests, the multiple applications belonging to at least one business system; determining multiple different system link patterns respectively associated with the at least one business system by analyzing the collected call logs; wherein the multiple different system links associated with a same business system are embodied as a call timing relationship between multiple applications under the business system according to call logs of the multiple applications included in the business system. Further comprising:

18. The method of claim 17, wherein, determining multiple system entries according to the analysis result of the call logs; the determining multiple different system link patterns comprises: determining information of system link branches included under a same system entry. Further comprising:

19. A system link analysis method, characterized by, collecting call logs generated by multiple applications in processing call requests, the multiple applications belonging to at least one business system; determining multiple different system link patterns respectively associated with the at least one business system by analyzing the collected call logs; wherein the multiple different system links associated with a same business system are embodied as a call timing relationship between multiple applications under the business system according to call logs of the multiple applications included in the business system; determining an added application relative to a previous time window by comparing call log information collected in multiple time windows; determining an impact of the added application on system links by analyzing call logs of the added application. Further comprising:

20. An active information delivery method, characterized by, collecting call logs generated by multiple applications in processing call requests, the multiple applications belonging to at least one business system; respectively analyzing call logs collected in multiple time windows to determine multiple different system link patterns respectively associated with the at least one business system; wherein the multiple different system links associated with a same business system are embodied as a call timing relationship between multiple applications under the business system according to call logs of the multiple applications included in the business system; determining a system link with changed traffic and corresponding time information, and activity information causing the traffic change by comparing operation results in adjacent time windows; providing the system link with changed traffic, the corresponding time information, and the activity information to a target client, so as to perform delivery of the activity information at the time through the target client. An apparatus for counting changes of different system links associated with a business system, the business system providing multiple functions, and under each function, multiple different system links, the apparatus comprising:

21. A link-tracing apparatus characterized by comprising: ​ A log collection unit is configured to collect call logs generated by a plurality of applications in a process of processing a call request, the plurality of applications belonging to at least one business system; A log analysis unit is configured to analyze the call logs collected in a plurality of time windows respectively, and determine a plurality of different system link patterns respectively associated with the at least one business system; wherein the plurality of different system links associated with the same business system are embodied as a call timing relationship between a plurality of applications under the business system, which is obtained according to the call logs of the plurality of applications included in the business system. A comparison unit is configured to determine information of a system link changed in the at least one business system by comparing analysis results in adjacent time windows, so as to sort out a business scenario change of the business system according to the information of the system link changed, or confirm a business system state dependent on the system link and give a warning in a fault case.

22. A link-tracing apparatus characterized by comprising: The device for counting changes of different system links associated with a business system is configured to provide a plurality of functions, and a plurality of different system links exist under each function, and the device comprises: A log generation unit is configured to generate call logs in a process of processing a call request by a plurality of applications, the plurality of applications belonging to at least one business system; A log providing unit is configured to provide the call logs to a link tracking system, so that the link tracking system analyzes the call logs collected in a plurality of time windows respectively, and determines a plurality of different system link patterns respectively associated with the at least one business system, and determines information of a system link changed in the at least one business system by comparing operation results in adjacent time windows, so as to sort out a business scenario change of the business system according to the information of the system link changed, or confirm a business system state dependent on the system link and give a warning in a fault case; Wherein the plurality of different system links associated with the same business system are embodied as a call timing relationship between a plurality of applications under the business system, which is obtained according to the call logs of the plurality of applications included in the business system.

23. A link optimization apparatus, comprising: The device for counting changes of different system links associated with a business system is configured to provide a plurality of functions, and a plurality of different system links exist under each function, and the device comprises: A log collection unit is configured to collect call logs generated by a plurality of applications in a process of processing a call request, the plurality of applications belonging to at least one business system; A log analysis unit is configured to analyze the call logs collected in a plurality of time windows respectively, and determine a plurality of different system link patterns respectively associated with the at least one business system; wherein the plurality of different system links associated with the same business system are embodied as a call timing relationship between a plurality of applications under the business system, which is obtained according to the call logs of the plurality of applications included in the business system. A comparison unit is configured to determine information of a system link changed in the at least one business system by comparing operation results in adjacent time windows. A link optimization unit is configured to optimize the changed system link.

24. A system link profile determination apparatus, comprising: The device for determining the associated system link under a business system, the business system providing multiple functions, multiple different system links existing under each function, comprises: A log collection unit is configured to collect call logs generated by multiple applications in the process of processing call requests, the multiple applications belonging to at least one business system; A log analysis unit is configured to determine multiple different system link forms respectively associated under the at least one business system by analyzing the collected call logs; wherein the multiple different system links associated under the same business system are embodied as the call timing relationship between multiple applications under the business system according to the call logs of the multiple applications included in the business system.

25. A system link analysis apparatus, characterized by, Comprise: A log collection unit is configured to collect call logs generated by multiple applications in the process of processing call requests, the multiple applications belonging to at least one business system; A log analysis unit is configured to determine multiple different system link forms respectively associated under the at least one business system by analyzing the collected call logs; wherein the multiple different system links associated under the same business system are embodied as the call timing relationship between multiple applications under the business system according to the call logs of the multiple applications included in the business system; A comparison unit is configured to determine an application newly added relative to a previous time window by comparing the call log information collected in multiple time windows; An impact analysis unit is configured to determine the impact of the newly added application on the system link by analyzing the call logs of the newly added application.

26. An active information delivery device, comprising: Comprise: A log collection unit is configured to collect call logs generated by multiple applications in the process of processing call requests, the multiple applications belonging to at least one business system; A log analysis unit is configured to analyze the call logs collected in multiple time windows respectively, and determine multiple different system link forms respectively associated under the at least one business system; wherein the multiple different system links associated under the same business system are embodied as the call timing relationship between multiple applications under the business system according to the call logs of the multiple applications included in the business system; A comparison unit is configured to determine the system link with changed traffic and the corresponding time information by comparing the operation results in adjacent time windows, and determine the activity information causing the traffic change; An information providing unit is configured to provide the system link with changed traffic, the corresponding time information and the activity information to a target client, so as to perform the delivery of the activity information at the time through the target client.

27. A computer system, characterized in that The device for counting the change of different system links associated under a business system, the business system providing multiple functions, multiple different system links existing under each function, comprises: One or more processors; and A memory associated with the one or more processors, the memory being configured to store program instructions, the program instructions being configured to perform the following operations when read and executed by the one or more processors: Collect a plurality of application invocation logs generated in a process of processing an invocation request, the plurality of applications belonging to at least one business system; Respectively analyze the invocation logs collected in a plurality of time windows to determine a plurality of different system link forms respectively associated with the at least one business system; wherein the plurality of different system links associated with a same business system are embodied as invocation time sequence relationships between a plurality of applications under the business system obtained according to invocation logs of the plurality of applications included in the business system; By comparing analysis results in adjacent time windows, information of a system link that has changed in the at least one business system is determined, so as to sort out a business scenario change of the business system according to the information of the system link that has changed, or to confirm a business system state dependent on the system link and to give a warning in a fault condition.

Images