Recommendation platform business inspection system and method and related equipment
By designing a business inspection system, using multiple offline inspection links to sort out the complex links of the recommendation platform and clarifying the inspection process, it solves the problem of difficulty in maintaining the status of the recommendation platform, and achieves stable guarantees of the business links and improves overall efficiency.
Patent Information
- Application Number
- CN202510252039.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-03-04
- Publication Date
- 2025-06-06
AI Technical Summary
The status maintenance of the recommended platform is difficult. Passively discovering problems with existing alarms and oncall processes is easy to cause missed problems and difficult to gain global status recognition of the system. Especially the offline core link is complex, and it is difficult to locate and repair faults, which affects user experience and recommendation effects.
Design a business inspection system, by designing multiple offline inspection links on the system, sorting out the complex upstream and downstream coupling links of the recommended platform's offline links, and clarifying the standard process for investigation, so as to help maintenance personnel to troubleshoot problems in multiple environments at a low cost.
It has achieved stable guarantees for the business links of the recommendation platform, improved overall efficiency, reduced maintenance costs, quickly positioned problems on complex links, and improved user experience and recommendation results.
Smart Images

Figure CN120104427A_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to the field of computer technology, and in particular to a recommendation platform service inspection system, a recommendation platform service inspection method and related equipment. Background Art
[0002] At present, the recommendation platform covers many front-end and back-end services and big data tasks, and its status maintenance is quite difficult. Moreover, with the increase in environment deployment and customer access, the difficulty of status maintenance will increase linearly. Relying solely on the existing alarm and on-call processes, passively discovering problems poses great challenges to personnel in different roles, easily leads to omissions of problems, and it is difficult to obtain the global status of the system. In addition, the core links on the offline side of the recommendation platform, such as the forward candidate reverse ranking module, have high consistency requirements, complex logic, and lengthy links. They are prone to problems and have serious impacts, which directly impact the user experience and recommendation effect. At the same time, because the business links of these offline core links are long, fault location and repair are difficult, and full-link elimination is required, which consumes a lot of manpower and time to check many nodes, hindering the stable operation and optimization process of the recommendation platform, resulting in poor experience on both the user side and the R&D side. Summary of the invention
[0003] In view of this, the embodiments of the present disclosure combine the business logic and current situation of the recommendation platform to build a business inspection system that meets the requirements of scalability, ease of use, stability, and timeliness. By designing multiple offline inspection links on the constructed business inspection system, sorting out the complex upstream and downstream coupling links of the offline links of the recommendation platform, and clarifying the standard process of troubleshooting, it helps maintenance personnel to troubleshoot problems in multiple environments at a low cost, thereby ensuring the stability of the business link and improving the overall efficiency of the recommendation platform.
[0004] The recommendation platform service inspection system described in the embodiment of the present disclosure includes:
[0005] An inspection plan generation module is used to generate an inspection plan based on the project information of the service to be inspected and the configuration information of at least one pre-configured inspection link; wherein the inspection plan includes at least one inspection task; each inspection task corresponds to a service link to be inspected; the service link to be inspected includes at least one service node to be inspected; each service node corresponds to at least one service indicator to be inspected; and each service indicator to be inspected corresponds to at least one data source;
[0006] The data tracking module is used to track the data sources associated with each inspection task to obtain data from the data sources;
[0007] At least one inspection execution module, used to execute the inspection plan based on the data embedding points, and obtain the inspection results of each inspection task respectively;
[0008] An inspection result summary module, used to summarize the inspection results of each inspection task to obtain the inspection results of the inspection plan; and
[0009] The display module is used to display the inspection results of the inspection plan.
[0010] In an embodiment of the present disclosure, the above-mentioned recommendation platform service inspection system may further include: an inspection link configuration module, which is used to pre-configure at least one inspection link; wherein the inspection link configuration module includes:
[0011] A link configuration unit, used to set inspection link information and set at least one service node for the inspection link; wherein the inspection link information includes: an identifier of the inspection link;
[0012] A node configuration unit, used to set service node information and set at least one service indicator related to the service node; wherein the service node information includes: an identifier of the service node;
[0013] An indicator configuration unit is used to set a group of data sources associated with the business indicator and determine a specific method of the business indicator based on the set data sources; wherein,
[0014] The inspection link configuration information includes: an identifier of the inspection link, an identifier of the service node included in the inspection link, at least one service indicator related to the service node included in the inspection link, a group of data sources associated with the service indicator, and a specific method for determining the service indicator based on the set data source.
[0015] In an embodiment of the present disclosure, the inspection plan generation module may include:
[0016] An inspection link matching unit, configured to determine at least one target inspection link associated with the service to be inspected based on the project information of the service to be inspected; and
[0017] The inspection task determination unit is used to generate at least one service link to be inspected based on the project information and the configuration information of the at least one target inspection link, and use each of the service links to be inspected as an inspection task of the inspection plan.
[0018] In an embodiment of the present disclosure, the recommendation platform service inspection system may further include: a periodic scheduling module, which is used to set a period for service inspection for the service to be inspected.
[0019] In an embodiment of the present disclosure, the above-mentioned recommendation platform service inspection system may further include: a manual scheduling module, which is used to set the inspection tasks that need to be performed on the service inspection; wherein the manual scheduling module includes:
[0020] An identification query unit, used to provide an identification query interface for users to query the inspection entity identification; wherein the inspection entity identification includes: the identification of the service link to be inspected or the identification of the service node to be inspected;
[0021] An inspection target entity receiving unit, used to receive an inspection target entity identifier fed back by a user; and
[0022] The inspection triggering unit is used to trigger the inspection execution module to perform service inspection on the target entity corresponding to the inspection target entity identifier.
[0023] In an embodiment of the present disclosure, the data tracking module includes:
[0024] A data reporting setting unit, used to configure the service to be inspected to actively report the inspection data, and cache the inspection data actively reported by the service to be inspected; or,
[0025] A data interface setting unit is used to configure the service to be inspected to provide a data interface for reading the inspection data.
[0026] In an embodiment of the present disclosure, the above-mentioned inspection execution module includes: at least one executor unit, which is used to execute an inspection task in the inspection plan based on the data embedding point.
[0027] In an embodiment of the present disclosure, the above-mentioned recommendation platform business inspection system may further include: a task issuing module;
[0028] The inspection plan generation module publishes at least one inspection task included in the inspection plan to the task publishing module;
[0029] The task publishing module maintains an inspection task queue for caching inspection tasks that have been published but not yet executed;
[0030] The at least one inspection execution module includes respective executor units that respectively monitor the inspection task queue of the task issuing module; and when the executor units can be used to execute inspection tasks, they receive inspection tasks from the head of the inspection task queue and execute the received inspection tasks.
[0031] In an embodiment of the present disclosure, the above-mentioned executor unit executes the inspection task received including:
[0032] Add all service nodes with zero in-degree in the directed acyclic graph corresponding to the inspection task to a stack;
[0033] Determine whether there is a service node at the top of the stack, if there is a service node at the top of the stack, pop the service node at the top of the stack as the target service node; if there is no service node at the top of the stack, end;
[0034] Based on the data embedding point, obtain the inspection data of all data sources corresponding to all business indicators corresponding to the target business node;
[0035] Determine inspection values of all service indicators corresponding to the target service nodes based on the inspection data;
[0036] Determine whether there is an abnormal business indicator based on the inspection value, if there is an abnormal business indicator, record the inspection value of the abnormal business indicator, mark the business indicator as an abnormal business indicator, and mark the target business node as an abnormal business node; if there is no abnormal business indicator, record the inspection value of the normal business indicator;
[0037] Deleting the in-degree of all downstream service nodes in the directed acyclic graph; and
[0038] De-duplicate the service nodes with zero in-degree among all downstream service nodes in the directed acyclic graph, add them to the stack, and then return to the step of determining whether there is a service node at the top of the stack.
[0039] In an embodiment of the present disclosure, the above-mentioned recommendation platform business inspection system may further include: a backend module;
[0040] After executing the received inspection tasks, each executor unit included in the at least one inspection execution module writes the inspection results corresponding to the executed inspection tasks into the back-end module;
[0041] The backend module caches the inspection results corresponding to each inspection task; and
[0042] The inspection result summary module reads the cached inspection results corresponding to each inspection task from the back-end module, and summarizes the inspection results corresponding to each inspection task to obtain the inspection results corresponding to the inspection plan.
[0043] In an embodiment of the present disclosure, the display module includes:
[0044] An inspection result display unit, used to display the inspection results of each inspection task included in the inspection plan in order of business inspection time; and / or,
[0045] The event reporting unit is used to report abnormal service links, abnormal service nodes and abnormal service indicators in the inspection results to the abnormal event center, and the abnormal event center performs abnormal result alarm processing.
[0046] Corresponding to the above-mentioned recommendation platform business inspection system, an embodiment of the present disclosure also discloses a recommendation platform business inspection method, including: generating an inspection plan based on the project information of the business to be inspected and the configuration information of at least one pre-configured inspection link; wherein the inspection plan includes at least one inspection task; each inspection task corresponds to a business link to be inspected; the business link to be inspected includes at least one business node to be inspected; each business node corresponds to at least one business indicator to be inspected; and each business indicator to be inspected corresponds to at least one data source; data embedding is performed on the data sources associated with each inspection task to obtain the data of the data source; the inspection plan is executed based on the data embedding to obtain the inspection results of each inspection task; the inspection results of each inspection task are summarized to obtain the inspection results of the inspection plan; and the inspection results of the inspection plan are displayed.
[0047] In addition, an embodiment of the present disclosure further provides an electronic device, including: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the above-mentioned recommendation platform service inspection method when executing the program.
[0048] An embodiment of the present disclosure further provides a non-transitory computer-readable storage medium, wherein the non-transitory computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a computer to execute the above-mentioned recommendation platform service inspection method.
[0049] An embodiment of the present disclosure further provides a computer program product, including computer program instructions, which, when executed on a computer, enable the computer to execute the above-mentioned recommendation platform service inspection method.
[0050] It can be seen that under the design framework of the above-mentioned recommendation platform business inspection system and recommendation platform business inspection method, the complex data link characteristics of the recommendation platform can be fully considered, and several types of inspection links can be carefully extracted. Among them, each type of inspection link corresponds precisely to a business link in each type of business of the recommendation platform. These inspection links or business links are composed of multiple business nodes, and each business node covers a large number of business indicator elements. Whenever the inspection process is started, the business inspection will be performed one by one from the first business node to the last business node in the order of the inspection link. After all business nodes are executed, the inspection results will be integrated and aggregated with the business node as the basic unit to obtain the overall inspection results for the business to be inspected. In addition, the overall inspection results can be used by relying on the message push mechanism and / or intuitive page presentation form, which can assist the operation and maintenance personnel to gain insight into the operation status and situation of the entire business link very clearly and accurately.
[0051] The above-mentioned recommendation platform business inspection system can actively monitor each business link of the recommendation platform system, discover problems in advance, make up for the shortcomings of alarms and oncalls, and effectively ensure the stability of the recommendation platform. In addition, the above-mentioned recommendation platform business inspection system can integrate multiple forms such as alarms and page presentations. Operation and maintenance personnel can timely perceive the status of each business of the recommendation platform and the status of business nodes on each business chain through a visual interface, so as to quickly locate problems on complex links, lock the scope of problems at a lower cost, and reduce the maintenance cost of the recommendation platform. BRIEF DESCRIPTION OF THE DRAWINGS
[0052] In order to more clearly illustrate the technical solutions in the present disclosure or related technologies, the drawings required for use in the embodiments or related technical descriptions are briefly introduced below. Obviously, the drawings described below are only embodiments of the present disclosure. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.
[0053] Figure 1 A structural diagram of a recommendation platform service inspection system according to an embodiment of the present disclosure is shown.
[0054] Figure 2 A schematic diagram of the process of completing inspection task allocation and inspection result aggregation among the inspection plan generation module, the inspection execution module and the inspection result aggregation module described in an embodiment of the present disclosure is shown.
[0055] Figure 3 The specific process of the executor unit performing the inspection task described in the embodiment of the present disclosure is shown.
[0056] Figure 4 The implementation process of the recommendation platform service inspection method described in the embodiment of the present disclosure is shown.
[0057] Figure 5 A more specific schematic diagram of the hardware structure of an electronic device described in some embodiments of the present disclosure is shown. DETAILED DESCRIPTION
[0058] In order to make the objectives, technical solutions and advantages of the present disclosure more clearly understood, the present disclosure is further described in detail below in combination with specific embodiments and with reference to the accompanying drawings.
[0059] It should be noted that, unless otherwise defined, the technical terms or scientific terms used in the embodiments of the present disclosure should be understood by people with ordinary skills in the field to which the present disclosure belongs. The "first", "second" and similar words used in the embodiments of the present disclosure do not indicate any order, quantity or importance, but are only used to distinguish different components. "Including" or "comprising" and similar words mean that the elements or objects appearing before the word cover the elements or objects listed after the word and their equivalents, without excluding other elements or objects. "Connect" or "connected" and similar words are not limited to physical or mechanical connections, but can include electrical connections, whether direct or indirect. "Up", "down", "left", "right" and the like are only used to indicate relative positional relationships. When the absolute position of the described object changes, the relative positional relationship may also change accordingly.
[0060] It is understandable that before using the technical solutions of each embodiment of the present disclosure, the type, scope of use, usage scenarios, etc. of the personal information involved will be informed to the user in an appropriate manner, and the user's authorization will be obtained.
[0061] For example, in response to receiving an active request from a user, a prompt message is sent to the user to clearly remind the user that the operation requested to be performed will require obtaining and using the user's personal information. Thus, the user can independently choose whether to provide personal information to software or hardware such as an electronic device, application, server, or storage medium that performs the operation of the technical solution of the present disclosure according to the prompt message.
[0062] As an optional but non-limiting implementation, in response to receiving an active request from the user, the prompt information may be sent to the user in the form of a pop-up window, in which the prompt information may be presented in text form. In addition, the pop-up window may also carry a selection control for the user to choose "agree" or "disagree" to provide personal information to the electronic device.
[0063] It is understandable that the above notification and the process of obtaining user authorization are merely illustrative and do not constitute a limitation on the implementation of the present disclosure. Other methods that meet relevant laws and regulations may also be applied to the implementation of the present disclosure.
[0064] As mentioned above, it is difficult to maintain the status of the recommendation platform. Moreover, there is no ready-made inspection solution for the recommendation platform in the industry, and it is difficult to find information about end-to-end troubleshooting tools, which makes it difficult to meet the troubleshooting needs of the recommendation platform, resulting in a poor experience on both the user side and the R&D side.
[0065] In view of this, some embodiments of the present disclosure provide a recommendation platform business inspection system, which can build a business inspection system that meets the requirements of scalability, ease of use, stability, and timeliness, and design multiple offline side inspection links on the constructed business inspection system, sort out the complex upstream and downstream coupling links of the recommendation platform offline links, and clarify the standard troubleshooting process, so as to help maintenance personnel troubleshoot problems in multiple environments at low cost, ensure the stability of business links, and thus improve the overall efficiency of the recommendation platform.
[0066] Figure 1 The internal structure of the recommendation platform service inspection system described in some embodiments of the present disclosure is shown. Figure 1 As shown, in some embodiments of the present disclosure, the above-mentioned recommendation platform business inspection system may include: an inspection plan generation module 110, a data tracking module 120, at least one inspection execution module 130, an inspection result summary module 140 and a display module 150.
[0067] In an embodiment of the present disclosure, the inspection plan generating module 110 is used to generate an inspection plan based on the project information of the service to be inspected and the configuration information of at least one pre-configured inspection link.
[0068] In some embodiments of the present disclosure, the service to be inspected may be a specific service, a specific task, or a specific configuration on the recommendation platform, or any combination thereof. The project information of the service to be inspected may include various configuration information of the service to be inspected.
[0069] In some embodiments of the present disclosure, the inspection plan may include at least one inspection task. Each inspection task may correspond to a service link to be inspected. Specifically, the service link to be inspected may include at least one service node to be inspected; each service node corresponds to at least one service indicator to be inspected; and each service indicator to be inspected corresponds to at least one data source.
[0070] In an embodiment of the present disclosure, the data tracking module 120 is used to respectively track data sources associated with each inspection task.
[0071] As mentioned above, in an embodiment of the present disclosure, the above inspection task corresponds to a service link to be inspected. The above service link to be inspected may include at least one service node to be inspected; each service node may correspond to at least one service indicator to be inspected; and each service indicator may correspond to at least one data source. Thus, in an embodiment of the present disclosure, the above data source associated with an inspection task may include: a data source corresponding to each service indicator corresponding to each service node to be inspected on the service link to be inspected corresponding to the above inspection task.
[0072] It can be understood that after the data tracking module 120 performs data tracking on the data sources associated with each inspection task respectively, when performing business inspection, the at least one inspection execution module 130 can respectively obtain the inspection data of the data sources associated with each inspection task, so as to respectively determine the status of each business indicator corresponding to each business node included in each business link to be inspected, and then respectively determine the status of each business node included in each business link to be inspected and the status of each business link to be inspected, thereby completing the inspection of the business to be inspected.
[0073] In an embodiment of the present disclosure, the at least one inspection execution module 130 is used to execute the inspection plan based on the data points to obtain the inspection results of each inspection task.
[0074] Generally speaking, in the embodiments of the present disclosure, the at least one inspection execution module 130 can respectively obtain the inspection data of the data source related to each inspection task, and determine the inspection value of the business indicator corresponding to each business node to be inspected based on the obtained inspection data, and determine the status of each business indicator based on the determined inspection value, and then determine the status of each business node to be inspected and the status of each business link to be inspected.
[0075] In an embodiment of the present disclosure, the inspection result of each inspection task mentioned above may include: the inspection value of the business indicator corresponding to each business node to be inspected included in the corresponding business link to be inspected, the marked abnormal business nodes and the marked abnormal business indicators.
[0076] In the embodiment of the present disclosure, the inspection result summary module 140 is used to summarize the inspection results of each inspection task to obtain the inspection results of the inspection plan.
[0077] In the embodiment of the present disclosure, the display module 150 is used to display the inspection results of the inspection plan.
[0078] It can be seen from this that the recommendation platform service inspection system provided by the embodiment of the present disclosure can generate an inspection plan based on the project information of the service to be inspected and the configuration information of at least one pre-configured inspection link, and complete the inspection of the service to be inspected based on the generated inspection plan.
[0079] The above-mentioned recommendation platform business inspection system can pre-sort out the complex upstream and downstream coupling links of the recommendation platform offline links by pre-designing multiple offline inspection links, and clarify the standard troubleshooting process, so as to help maintenance personnel troubleshoot problems in multiple environments at low cost, thereby ensuring the stability of the business links and improving the overall efficiency of the recommendation platform.
[0080] The structure and function of each module in the recommendation platform service inspection system will be described in detail below with reference to specific examples.
[0081] In the embodiments of the present disclosure, each of the above-mentioned pre-configured inspection links is respectively used to describe a group of business nodes with dependencies. The above-mentioned inspection links are mainly used to characterize the business logic of the core links on the offline side of the recommendation platform, sort out the complex upstream and downstream coupling relationships of the offline links of the recommendation platform, and clarify the standard procedures for troubleshooting. In other words, the relationship between the business nodes of the above-mentioned inspection links usually also corresponds to an actual business link. It can be seen that through the above-mentioned pre-set inspection links, the inspection of the business links can be completed, thereby helping maintenance personnel to troubleshoot problems in multiple environments at low cost, thereby ensuring the stability of the business links and improving the overall efficiency of the recommendation platform.
[0082] Generally, all nodes on a patrol link may form a directed acyclic graph (DAG). Therefore, in some embodiments of the present disclosure, the patrol link may be represented by a DAG, where the nodes on the DAG represent the service nodes on the patrol link, and the edges between the nodes on the DAG represent the dependencies between the service nodes on the patrol link.
[0083] In the recommendation platform application scenario, based on various core business links of the recommendation platform, the above-mentioned pre-set inspection links may include: forward link, candidate link, reverse link, streaming task link and batch task link, etc.
[0084] In addition, in an embodiment of the present disclosure, the above-mentioned inspection link includes at least one service node. Each service node may correspond to at least one service indicator; and each service indicator corresponds to at least one data source. Specifically, in an embodiment of the present disclosure, the service nodes included in the above-mentioned inspection link are used to describe some relatively important nodes on the inspection link. Generally, the above-mentioned service node may be a type of task, a type of component, a type of data, or any combination of the above three in terms of service. One or more service indicators corresponding to each of the above-mentioned service nodes are used to describe the state of the above-mentioned service node. And as mentioned above, each of the above-mentioned service indicators corresponds to at least one data source. Among them, the above-mentioned data source is used to describe the buried point data, for example, the above-mentioned data source may be one of metrics, logs, events, application programming interfaces (APIs), etc. or any combination thereof. In addition, the above-mentioned data source may also be other data of at least one customized type. It can be understood that for a certain service node, the inspection value of each service indicator corresponding to the above-mentioned service node can be determined based on the inspection data obtained from the data source associated with each service indicator corresponding to the above-mentioned service node, thereby determining the state of each service indicator respectively, such as whether it is a normal service indicator or an abnormal service indicator. Moreover, after determining the status of all the business indicators corresponding to the above-mentioned business nodes, the status of the above-mentioned business nodes can be determined, such as whether it is a normal business node or an abnormal business node. Further, after determining the status of each business node on a business link to be inspected, the status of the above-mentioned business link to be inspected can be determined, such as whether it is a normal business link or an abnormal business link. Then, the status of the business corresponding to it can be determined, that is, the business inspection is completed. It can be understood that under normal circumstances, when configuring the inspection link, the normal range of each business indicator on each business node will be configured at the same time. If the inspection value is within the configured normal range, the business indicator is a normal business indicator; otherwise, it is an abnormal business indicator. In addition, for the status of the business node, it can be generally considered that the business node with abnormal business indicators is an abnormal business node; and when all the corresponding business indicators are all normal, the business node is a normal business node. It is similar for the business link to be inspected. It can be generally considered that the business link with abnormal business nodes is an abnormal business link; and when all the business nodes it includes are all normal, the business link is a normal business link.
[0085] Based on the above content, in an embodiment of the present disclosure, the configuration information of the above inspection link may include: an identifier of the inspection link, an identifier of at least one service node included in the inspection link, information of at least one service indicator corresponding to each service node, information of at least one data source corresponding to each service indicator, and a determination method of each service indicator, etc. In an embodiment of the present disclosure, the identifier of the inspection link may be used to uniquely identify the pre-built inspection link. In addition, the identifier of the service node may also be used to uniquely identify each service node on the inspection link.
[0086] In order to implement the pre-configuration of the inspection link, in the embodiment of the present disclosure, the recommendation platform service inspection system may further include: an inspection link configuration module. In practical applications, the inspection link configuration module may specifically include: a link configuration unit, a node configuration unit and an indicator configuration unit.
[0087] Among them, the link configuration unit is mainly used to set the inspection link information and set at least one business node for the inspection link. Among them, the inspection link information may include information such as the identification of the inspection link. The node configuration unit is mainly used to set the business node information and set at least one business indicator related to the business node. Among them, the business node information may include information such as the identification of the business node. The indicator configuration unit is mainly used to set a group of data sources associated with the business indicators and a specific method for determining the above-mentioned business indicators based on the set data sources. In this way, after completing the configuration of the business indicators, in the subsequent business inspection process, data points can be first buried through the set data sources to obtain inspection data related to each business indicator, and then the inspection value of the business indicator can be determined based on the specific method for determining the business indicator set in the above configuration information and the obtained inspection data, and then the status of the business indicator, the status of the business node and the status of the business link to be inspected can be determined in turn.
[0088] It can be seen from this that through the above-mentioned inspection link configuration module, multiple offline inspection links can be designed on the constructed inspection system, so as to sort out the complex upstream and downstream coupling links of the offline links of the recommendation platform, clarify the standard process of troubleshooting, ensure effective inspection of business links, and help maintenance personnel troubleshoot problems in multiple environments, thereby improving the overall efficiency of the recommendation platform.
[0089] In addition, the project information of the service to be inspected is the relevant information set for the service to be inspected from the user side, such as the name of the project and the service logic and other related information. Generally, from the perspective of service logic, the service to be inspected may be associated with multiple inspection links at the same time. Therefore, the project information of the service to be inspected may include the corresponding information of at least one inspection link associated with the service to be inspected.
[0090] Thus, in the embodiment of the present disclosure, the inspection plan generation module 110 may include:
[0091] An inspection link matching unit, configured to determine at least one target inspection link associated with the service to be inspected based on the project information of the service to be inspected; and
[0092] The inspection task determination unit is used to generate at least one service link to be inspected based on the project information and the configuration information of at least one target inspection link, and each of the service links to be inspected is used as an inspection task.
[0093] That is to say, in an embodiment of the present disclosure, the above-mentioned inspection plan may include at least one inspection task. Among them, each inspection task corresponds to a business link to be inspected. Among them, each business link to be inspected corresponds to a patrol link. Moreover, each business link to be inspected may also include at least one business node to be inspected; each business node corresponds to at least one business indicator; and each business indicator corresponds to at least one data source. It can be understood that the above-mentioned business link to be inspected is generated based on a pre-set patrol link. Among them, the business nodes to be inspected contained in the business link to be inspected correspond to the business nodes configured on the patrol link, and the business indicators corresponding to each business node to be inspected and the data source corresponding to each business indicator also correspond to the business indicators and data sources corresponding to the business nodes on each patrol link.
[0094] In other words, each pre-generated inspection link corresponds to an actual business link, which defines the key business nodes that need to be inspected when inspecting the business link, the business indicators that need to be checked when inspecting each business node, the data source for calculating these business indicators, and the calculation method. The inspection link is similar to a "template" that specifies how to inspect a business link. For example, the inspection link defines which key business nodes need to be inspected for a business link, which business indicators need to be inspected for a business node that needs to be inspected, the specific standards for evaluating whether these business indicators are abnormal, and which data needs to be paid attention to for each business indicator, how to determine these business indicators based on these data, etc. For each specific business to be inspected, before conducting the business inspection, the above-mentioned inspection plan generation module 110 needs to "instantiate" the above-mentioned multiple "templates" based on the project information of the business to be inspected, that is, define the business nodes, business indicators and data sources of this business based on the "template", determine the business links that actually need to be inspected, and the business nodes that need to be paid attention to when conducting business inspections on these business links, the business indicators that need to be determined on each node when conducting inspections, and the data sources required to determine the business indicators, etc. As mentioned above, each inspection link can be represented as a DAG. Similarly, each business link to be inspected can also be represented as a DAG, or correspond to a DAG. The nodes on the DAG represent the business nodes to be inspected on the business link to be inspected, and the edges between the nodes on the DAG represent the dependencies between the business nodes to be inspected on the business link to be inspected.
[0095] In addition, in order to identify the generated service link to be inspected, in the embodiment of the present disclosure, a service link identifier may be assigned to the determined service link to be inspected and a service node identifier may be assigned to the service node on it. In the embodiment of the present disclosure, the service link to be inspected and the service node to be inspected may be used as an entity for service inspection separately.
[0096] In addition, it can be understood that business inspections usually need to be performed repeatedly or periodically, that is, most business inspections are periodically triggered business inspections. Therefore, for periodically triggered business inspections, the project information of the above-mentioned business to be inspected can also include the inspection cycle set for the business to be inspected from the user side. In some embodiments of the present disclosure, the user can directly configure the inspection cycle in the project information when configuring the business. In this case, the above-mentioned recommendation platform business inspection system can further include: a periodic scheduling module, which is used to set the period for business inspections for the inspection business based on the above-mentioned project information. In some other embodiments of the present disclosure, the user can set the period for business inspections for the inspection business separately. In this case, the above-mentioned periodic scheduling module can be used to set the period for business inspections for the inspection business based on the user's settings. In this way, in general, the above-mentioned periodic scheduling module is mainly used to set the period for business inspections for the inspection business.
[0097] In the case of the above-mentioned periodically triggered service inspection, after generating the inspection plan corresponding to the service to be inspected, the above-mentioned inspection plan generation module 110 will also read the inspection cycle set for the service to be inspected, so as to determine the planned trigger time of each inspection task in the above-mentioned inspection plan, and trigger the above-mentioned inspection execution module 130 to execute the corresponding inspection task at the planned trigger time of each inspection task. Specifically, when triggering the above-mentioned inspection execution module 130 to execute the inspection task, the service link identifier or service node identifier related to the inspection task can be used to inform the inspection execution module 130 of the object of the service inspection.
[0098] It can be seen that in the above embodiment, the above inspection plan generation module 110 can serve as a manager (Manager) of business inspection, and can generate an inspection plan containing one or more inspection tasks according to the actual business needs of the user and the configuration information of the pre-configured inspection link, and complete periodic business inspection triggering based on the set inspection cycle.
[0099] It is understandable that the inspection plan generation module 110 can generate multiple inspection plans for different services to be inspected. Among them, for inspection plans with the same scheduling period, the inspection plan generation module 110 can also integrate the inspection plans with the same scheduling period and schedule them together, that is, trigger the inspection plans in a unified manner.
[0100] In addition, as a supplementary solution to the above solution, in addition to periodically triggered service inspections, the embodiments of the present disclosure may also support manually triggered service inspections. Specifically, for manually triggered service inspections, the above recommendation platform service inspection system may further include: a manual scheduling module for setting inspection tasks that require service inspections. Specifically, the above manual scheduling module may specifically include:
[0101] The identification query unit is used to provide an identification query interface for users to query the inspection entity identification.
[0102] In an embodiment of the present disclosure, the above-mentioned inspectable entity identifier may be the identifier of at least one generated service link to be inspected and the identifier of each service node on the at least one service link to be inspected. In some embodiments of the present disclosure, the above-mentioned identifier query interface may provide a graphical user interface (GUI) for the user, for example, displaying an inspectable service link to the user in the form of a DAG, and supporting the user's selection operation on the DAG and the selection operation on each service node on the DAG.
[0103] The inspection target entity receiving unit is used to receive the inspection target entity identifier fed back by the user.
[0104] In an embodiment of the present disclosure, the inspection target entity identifier may be the identifier of any service link, or the identifier of any service node on any service link. That is, a user may manually trigger a service inspection of any service link, or manually trigger a service inspection of any service node on any service link. In some embodiments of the present disclosure, a user may feedback the inspection target entity identifier through a GUI. For example, a user may feedback the inspection target entity identifier by selecting a DAG displayed on the GUI or selecting a service node on a DAG.
[0105] The inspection triggering unit is used to trigger the inspection execution module 130 to perform a service inspection on the entity corresponding to the inspection target entity identifier.
[0106] It can be seen from this that through the above manual scheduling module, the user can trigger the inspection of any service link to be inspected or any service node thereon at any time.
[0107] In an embodiment of the present disclosure, the above-mentioned data tracking module 120 is used to perform data tracking on the data sources associated with each business link to be inspected, so as to obtain data of the data sources related to each business link to be inspected during business inspection, also known as inspection data.
[0108] The tracking module 120 mainly provides the data (for example, including metrics, APIs, logs or events, etc.) required to determine each business indicator of the business node through various methods based on the inspection requirements of the business to be inspected.
[0109] In some embodiments of the present disclosure, the data tracking module 120 may include: a data reporting setting unit, which is used to configure the service to be inspected (such as the service, task or configuration to be inspected) to actively report the inspection data, and cache the inspection data actively reported by the service to be inspected. In this way, when performing service inspections, each inspection execution module 130 can directly read the data source required to determine each service indicator of the service node from the cached inspection data.
[0110] In other embodiments of the present disclosure, the data tracking module 120 may include: a data interface setting unit, which is used to configure the service to be inspected (e.g., the service, task or configuration to be inspected) to provide a data interface for reading the inspection data. In this way, when performing a service inspection, the inspection execution module 130 can read the data source required to determine each service indicator of the service node from the service to be inspected through the data interface.
[0111] In an embodiment of the present disclosure, the at least one inspection execution module 130 is used to execute the inspection plan based on data points. In general, the at least one inspection execution module 130 can be used to respectively obtain the inspection data of the data source related to each inspection task, determine the inspection value of the business indicator corresponding to each business node to be inspected based on the obtained inspection data, and determine the inspection result of each inspection task based on the inspection value.
[0112] In an embodiment of the present disclosure, the at least one inspection execution module 130 is a worker for business inspection. In order to realize distributed business inspection, in an embodiment of the present disclosure, the recommendation platform business inspection system may include multiple inspection execution modules 130. In practical applications, after the inspection plan generation module 110 generates the inspection plan, it can assign the inspection tasks contained in the inspection plan to one or more inspection execution modules 130 for completion. Furthermore, the inspection execution module 130 may also include one or more executor units. Executor is the smallest unit of resource scheduling in Worker, and each Executor executes one inspection task respectively. Usually, the number of Executors in Worker indicates the number of threads that can be used to execute inspection tasks.
[0113] In the embodiment of the present disclosure, the inspection result summary module 140 can serve as another manager of the service inspection, and is used to summarize the inspection results for each inspection task obtained from each inspection execution module 130 to obtain the inspection results for the inspection plan.
[0114] Figure 2 A schematic diagram of the process of allocating inspection tasks and summarizing inspection results among the inspection plan generating module 110, the inspection executing module 130 and the inspection result summarizing module 140 according to an embodiment of the present disclosure is shown.
[0115] like Figure 2 As shown, the recommendation platform business inspection system may include multiple inspection execution modules 130 (two are shown in the figure). Each inspection execution module 130 may also include multiple Executors 210 (three are shown in the figure). Each Executor is used to execute an inspection task, that is, corresponding to a DAG.
[0116] In order to distribute inspection tasks, a task publishing module (Broker) 220 may also be included between the inspection plan generation module 110 and the inspection execution module 130. After generating the inspection plan, the inspection plan generation module 110 will publish at least one inspection task included in the inspection plan to the task publishing module 220. The task publishing module 220 will maintain an inspection task queue for caching inspection tasks that have been published but not yet executed. Each Executor in the multiple inspection execution modules 130 will respectively monitor the inspection task queue in the task publishing module, and when it can be used to execute the inspection task, it will receive an inspection task from the head of the inspection task queue, and then execute the received inspection task.
[0117] Furthermore, in order to complete the collection of inspection results, a backend module (Backend) 230 can also be included between the inspection result summary module 140 and the inspection execution module 130. After executing the received inspection task, each Executor in the above-mentioned multiple inspection execution modules 130 will write the inspection result corresponding to the executed inspection task into the above-mentioned backend module 230. The above-mentioned backend module 230 will cache the inspection results corresponding to each inspection task. Afterwards, the inspection result summary module 140 will read the inspection results corresponding to each inspection task cached in the above-mentioned backend module, and summarize the inspection results corresponding to the inspection plan, and finally submit them to the display module 150 for display of the inspection results.
[0118] Furthermore, in an embodiment of the present disclosure, each Executor may also include multiple checkers, wherein each Checker corresponds to a business indicator, and its main task is to extract the inspection data of the data source through the data embedding point required for calculating a certain business indicator, and calculate the business indicator based on the extracted inspection data, thereby obtaining the inspection value of the business indicator. The above-mentioned Checker will further verify the inspection value of each business indicator based on the pre-set verification rules to determine the status of the business indicator. For example, the normal inspection value range of each business indicator is determined in advance, so that it can be determined whether the business indicator is an abnormal business indicator or a normal business indicator based on the determined inspection value of the business indicator.
[0119] Considering that there is a front-and-back relationship between some service nodes on each service link to be inspected that cannot be decoupled, the inspection of these service nodes needs to be performed serially according to the front-and-back relationship of the service link. In this case, in some embodiments of the present disclosure, the inspection execution module 130 can perform service inspection according to the following logic. Specifically, the specific process of each Executor on the inspection execution module 130 performing the inspection task can be as follows: Figure 3 As shown, it includes the following steps:
[0120] In step 310, all service nodes with zero in-degree in the directed acyclic graph corresponding to the inspection task are added to a stack.
[0121] In step 320 , it is determined whether there is a service node at the top of the stack. If there is a service node at the top of the stack, step 330 is executed; if there is no service node at the top of the stack, step 325 is executed.
[0122] Before executing the following step 330, it is also possible to further check whether the service inspection has timed out. If the inspection has timed out, the inspection timeout processing is performed, and then the process jumps to step 325 to recall the inspection result and then ends. If the inspection has not timed out, the following step 330 can be continued.
[0123] In step 330, the top service node of the stack is popped out of the stack as the target service node.
[0124] In step 340, based on the data tracking point, the inspection data of all data sources corresponding to all business indicators corresponding to the target business node are obtained.
[0125] In step 350, inspection values of all service indicators corresponding to the target service node are determined based on the inspection data.
[0126] In the above steps, the inspection value of each business indicator may be calculated based on a pre-configured specific method for calculating the business indicator.
[0127] As mentioned above, the operations of obtaining inspection data and calculating inspection values for each business indicator corresponding to the target business node can be respectively executed in parallel by multiple Checkers.
[0128] In step 360 , it is determined whether there are abnormal business indicators based on the above inspection values. If there are abnormal business indicators, step 370 is executed; if there are no abnormal business indicators, step 380 is executed.
[0129] In the above steps, the calculated inspection value can be determined to be normal according to the preset service indicator inspection rule, thereby determining whether the service indicator is normal or abnormal. Specifically, the preset service indicator inspection rule can also be configured during the configuration process of the inspection link.
[0130] In step 370 , the inspection value of the abnormal service indicator is recorded, and the service indicator is marked as an abnormal service indicator, and the target service node is marked as an abnormal service node, and then step 390 is executed.
[0131] In the embodiments of the present disclosure, it is also possible to further pre-set business indicator exception handling rules based on the experience accumulated from handling abnormal business indicators, that is, the handling solutions for business indicators under various abnormal conditions. Specifically, the above-mentioned pre-set business indicator exception handling rules can also be configured during the configuration process of the inspection link. In this case, after the business indicator abnormality is captured, the corresponding handling solution can be obtained according to the pre-set business indicator exception handling rules, and the handling solution can be summarized in the inspection results and provided to the user together.
[0132] In step 380 , the inspection value of the normal business indicator is recorded, and then step 390 is executed.
[0133] In step 390, the in-degrees of all downstream service nodes in the directed acyclic graph corresponding to the inspection task are deleted.
[0134] In step 395 , the service nodes with zero in-degree in all downstream service nodes in the directed acyclic graph corresponding to the inspection task are deduplicated, added to the stack, and then the process returns to step 320 .
[0135] In step 325, the inspection results are recalled and the process ends.
[0136] From the above process, it can be seen that when each Executor performs the inspection task, it will fully consider the inseparable front-end and back-end relationships between the business nodes on each business link to be inspected, and perform serial inspections on these business nodes, so that the inspection results are accurate and effective.
[0137] As mentioned above, after completing the inspection of each service link respectively, that is, after completing the inspection of each inspection task, an inspection result related to the inspection plan will be summarized, which is also a collection of inspection results. In the embodiment of the present disclosure, the above-mentioned inspection results may include: the inspection value of the business indicator corresponding to each service node to be inspected on each service link to be inspected. In the case of abnormal business indicators, the above-mentioned inspection results may also include: the identification of the abnormal business link, the identification of the abnormal business node and the identification of the abnormal business indicator. The above-mentioned inspection results may also include: the processing plan corresponding to the abnormal business indicator. After obtaining the above-mentioned inspection results, the recommendation platform business inspection system can send the inspection results to different targets according to the pre-set inspection processing interface, so that the inspection results for different business links can be subsequently manually processed by pre-set personnel.
[0138] Specifically, the recommendation platform service inspection system can display the inspection results corresponding to the above inspection plan through the display module 150.
[0139] In some embodiments of the present disclosure, the above-mentioned display module 150 may include: an inspection result display unit, which is used to display the inspection results of each inspection task included in the inspection plan in the order of the time of the business inspection. Specifically, the above-mentioned inspection result display unit can display the inspection results in dimensions according to the timeline of the inspection dashboard built by the low-code front-end framework (amis), so as to intuitively display the status information and fluctuation changes of each dimension of each business. In an embodiment of the present disclosure, the above-mentioned multiple dimensions may refer to the inspection results of each inspection task, each business node to be inspected, or each business indicator to be inspected, etc., waiting for the inspection business in multiple dimensions.
[0140] Alternatively, as an alternative or supplementary solution to the above solution, the above display module 150 may also include: an event reporting unit, which is used to report abnormal business links, abnormal business nodes, and abnormal business indicators in the inspection results to the abnormal event center of the business system, and the abnormal event center performs abnormal result alarm processing. Specifically, the above event reporting unit can connect the inspection abnormality information to the event center, and publish the inspection abnormality information according to the alarm rules configured by the event center, and then the relevant personnel will manually process it.
[0141] It can be seen that under the design framework of the above-mentioned recommendation platform business inspection system, the complex data link characteristics of the recommendation platform can be fully considered, and several types of inspection links have been carefully refined. Among them, each inspection link corresponds precisely to a business link in each type of business of the recommendation platform. These links are composed of multiple business nodes, and each business node covers a large number of business indicator elements. Whenever the inspection process is started, the business inspection will be performed one by one from the first business node to the last business node in the order of the inspection link. After all business nodes are executed, the inspection results will be integrated and aggregated with the business node as the basic unit. With the message push mechanism and intuitive page presentation, the operation status and situation of the entire business link can be very clearly and accurately understood.
[0142] The above-mentioned recommendation platform business inspection system can actively monitor each business link of the recommendation platform system, discover problems in advance, make up for the shortcomings of alarms and oncalls, and effectively ensure the stability of the recommendation platform. In addition, the above-mentioned recommendation platform business inspection system can integrate multiple forms such as alarms and page presentations. Operation and maintenance personnel can timely perceive the status of each business of the recommendation platform and the status of business nodes on each business chain through a visual interface, so as to quickly locate problems on complex links, lock the scope of problems at a lower cost, and reduce the maintenance cost of the recommendation platform.
[0143] Corresponding to the above-mentioned recommendation platform service inspection system, the embodiment of the present disclosure also discloses a recommendation platform service inspection method. Figure 4 The implementation process of the recommendation platform service inspection method described in the embodiment of the present disclosure is shown. Figure 4 As shown, the above recommendation platform service inspection method may include:
[0144] In step 410, an inspection plan is generated based on the project information of the service to be inspected and the configuration information of at least one pre-configured inspection link.
[0145] In an embodiment of the present disclosure, the inspection plan may include at least one inspection task. Each inspection task may correspond to a service link to be inspected. Specifically, the service link to be inspected may include at least one service node to be inspected; each service node corresponds to at least one service indicator to be inspected; and each service indicator to be inspected corresponds to at least one data source.
[0146] Specifically, in an embodiment of the present disclosure, the business nodes included in the above-mentioned inspection link can be a type of task, a type of component, a type of data, or any combination of the above three in terms of business. Further, in an embodiment of the present disclosure, each of the above-mentioned business nodes corresponds to one or more business indicators to describe the status of the above-mentioned business nodes. And as mentioned above, each of the above-mentioned business indicators corresponds to at least one data source. Among them, the above-mentioned data source is used to describe the buried data. For example, the above-mentioned data source can be one of metrics, log, event, API, etc. or any combination thereof. Alternatively, the above-mentioned data source can also be customized at least one type of other data.
[0147] In step 420, data points are respectively buried for the data sources associated with each inspection task to obtain data from the above data sources.
[0148] In step 430, the inspection plan is executed based on the data points to obtain inspection results for each inspection task.
[0149] In step 440, the inspection results of each inspection task are summarized to obtain the inspection results of the inspection plan.
[0150] In an embodiment of the present disclosure, the inspection results may include: inspection values of service indicators corresponding to each service node to be inspected included in each service link to be inspected, identification of abnormal service links, identification of abnormal service nodes and abnormal service indicators.
[0151] In step 450, the inspection results of the inspection plan are displayed.
[0152] As mentioned above, in some embodiments of the present disclosure, the above-mentioned business to be inspected may specifically be one of a specific service, a specific task, and a group of specific configurations on the recommendation platform, or any combination thereof.
[0153] In addition, in an embodiment of the present disclosure, the data source associated with each inspection task may specifically include: a data source corresponding to each service indicator corresponding to each service node to be inspected on the service link to be inspected corresponding to the inspection service.
[0154] It can be seen from this that the recommendation platform service inspection method provided by the embodiment of the present disclosure can generate an inspection plan based on the project information of the service to be inspected and the configuration information of at least one pre-configured inspection link, and complete the service inspection based on the generated inspection plan. The above-mentioned recommendation platform service inspection method can pre-sort out the complex upstream and downstream coupling links of the recommendation platform offline link by pre-designing multiple offline side inspection links, clarify the standard process of troubleshooting, thereby ensuring the stability of the link, helping maintenance personnel to troubleshoot problems in multiple environments at a low cost, thereby improving the overall efficiency of the recommendation platform.
[0155] The specific implementation method of each step in the above recommendation platform service inspection method will be described in detail below with reference to specific examples.
[0156] In an embodiment of the present disclosure, before executing the above step 410, the above recommendation platform service inspection method may further include: pre-configuring at least one inspection link.
[0157] In an embodiment of the present disclosure, the configuration information of the inspection link may include: an identifier of the inspection link, an identifier of at least one service node included in the inspection link, information of at least one service indicator corresponding to each service node, information of at least one data source corresponding to each service indicator, and a determination method for each service indicator. In an embodiment of the present disclosure, the identifier of the inspection link is used to uniquely identify the pre-built inspection link, and in addition, the identifier of the service node is used to uniquely identify each service node on the inspection link.
[0158] In order to realize the pre-configuration of the above-mentioned inspection link, in an embodiment of the present disclosure, the step of pre-configuring at least one inspection link may include: first, setting the inspection link information and setting at least one service node for the inspection link. Among them, the above-mentioned inspection link information may include information such as the identification of the inspection link. Then, setting the service node information and setting at least one service indicator related to the service node. Among them, the above-mentioned service node information may include information such as the identification of the service node. Finally, setting a group of data sources associated with the service indicators and a specific method for determining the above-mentioned service indicators based on the set data sources. In this way, after completing the configuration of the above-mentioned inspection link, in the subsequent service inspection process, data points may be first buried through the set data sources to obtain data related to the service indicators, and then the inspection value of the service indicator may be determined based on the set specific method for determining the service indicators and the acquired data, so as to determine the status of the service node and the status of the service link to be inspected.
[0159] It can be seen from this that through the pre-configuration of at least one inspection link mentioned above, multiple offline inspection links can be designed on the constructed inspection system, so as to sort out the complex upstream and downstream coupling links of the offline links of the recommendation platform, clarify the standard process of troubleshooting, ensure effective inspection of business links, and help maintenance personnel troubleshoot problems in multiple environments, thereby improving the overall efficiency of the recommendation platform.
[0160] In addition, the project information of the service to be inspected is the relevant information set for the service to be inspected from the user side, such as the name of the project and the service logic and other related information. Usually, the service to be inspected may involve multiple inspection links at the same time, so the project information of the service to be inspected may include the corresponding information of at least one inspection link associated with the service to be inspected.
[0161] Thus, in the embodiment of the present disclosure, the above step 410 may specifically include: first, determining at least one target inspection link associated with the business to be inspected based on the project information of the business to be inspected; then, generating at least one business link to be inspected based on the project information and the configuration information of at least one target inspection link, and treating each of the business links to be inspected as a respective inspection task.
[0162] That is to say, the above inspection plan may include at least one inspection task. Each inspection task corresponds to a business link to be inspected. Corresponding to the inspection link, each business link to be inspected may also include at least one business node to be inspected; each business node corresponds to at least one business indicator; and each business indicator corresponds to at least one data source. It can be understood that the above business link to be inspected is generated based on the pre-set inspection link. The business nodes to be inspected included in the business link to be inspected correspond to the business nodes configured on the inspection link, and the business indicators corresponding to each business node to be inspected and the data source corresponding to each business indicator also correspond to the business indicators and data sources corresponding to the business nodes on each inspection link.
[0163] In addition, for periodically triggered service inspections, the project information of the service to be inspected may also include the inspection cycle set for the service to be inspected from the user side. In some embodiments of the present disclosure, the user may directly configure the inspection cycle in the project information when configuring the service. In this case, the project information of the service to be inspected may directly include the inspection cycle. In other embodiments of the present disclosure, the recommendation platform service inspection method may further include: setting an inspection cycle for the service to be inspected.
[0164] In the above-mentioned periodically triggered business inspection scenario, after the inspection plan corresponding to the business to be inspected is generated, the inspection cycle set for the business to be inspected will also be read to determine the planned trigger time of each inspection task in the above-mentioned inspection plan, and trigger the execution of the corresponding inspection task at the planned trigger time of each inspection task.
[0165] In addition, as a supplementary scheme to the above scheme, in addition to periodically triggered business inspections, the embodiments of the present disclosure can also support manually triggered business inspections. Specifically, for manually triggered business inspections, the above recommendation platform business inspection method can further include: receiving inspection tasks set by users that need to be inspected. Specifically, the above steps of receiving inspection tasks set by users that need to be inspected can specifically include: first, providing an identification query interface to the user for the user to query the inspectionable entity identification; second, receiving the inspection target entity identification fed back by the user; and finally, performing a business inspection on the entity corresponding to the above inspection target entity identification. It can be seen from this that through the above manual scheduling module, the user can trigger the inspection of any business link to be inspected or any business node thereon at any time.
[0166] In an embodiment of the present disclosure, through the above step 420, the data required to determine each business indicator of the business node (for example, including metrics, APIs, logs or events, etc.) can be provided in various ways based on the inspection requirements of the business to be inspected.
[0167] In some embodiments of the present disclosure, the data tracking may specifically include: configuring the service to be inspected (e.g., the service, task, or configuration to be inspected) to actively report the inspection data, and caching the inspection data actively reported by the service to be inspected. In this way, when performing service inspections, data of the data source required to determine each service indicator of the service node can be directly read from the cached inspection data.
[0168] In some other embodiments of the present disclosure, the data tracking may specifically include: configuring the service to be inspected (e.g., the service, task, or configuration to be inspected) to provide a data interface for reading the inspection data. In this way, when performing service inspection, the data interface may be used to read the data source required for determining each service indicator of the service node from the service to be inspected.
[0169] In the embodiment of the present disclosure, the subject for executing the inspection plan may be multiple inspection execution modules, and each inspection execution module may also include multiple executor units. Each executor unit is used to execute an inspection task in the above inspection plan. In other words, the multiple inspection tasks included in the inspection plan can be executed in parallel by multiple executor units. The inspection execution module can be based on Figure 2The process shown in FIG. 1 receives the inspection task to be executed by itself and submits the inspection result. In addition, for each inspection task, the executor unit can use the aforementioned Figure 3 The method shown completes the business inspection of an inspection task. The specific process will not be repeated.
[0170] Specifically, in the embodiments of the present disclosure, the executor unit can obtain the inspection data of the data source associated with a service node in two ways. The first way is to obtain the inspection data reported by the service to be inspected from the cached inspection data; the second way is to obtain the inspection data of the data source associated with the service node through the data interface for reading the inspection data provided by the service to be inspected.
[0171] After completing the service inspection of each inspection task, the inspection results of each inspection task can be obtained, including: the inspection value of the service indicator associated with each inspection task, abnormal service link, abnormal service node and abnormal service indicator information. For abnormal service indicators, the inspection results can also include the processing plan for the abnormal service indicators.
[0172] Thus, in the subsequent step 440, the inspection results of the above-mentioned inspection tasks may be summarized to obtain the inspection results of the above-mentioned inspection plan.
[0173] Finally, in the above-mentioned step 450, the step of displaying the inspection results of the inspection plan may include: displaying the inspection results of each inspection task included in the inspection plan in chronological order of business inspection; and / or reporting abnormal business links, abnormal business nodes and abnormal business indicators in the inspection results to the abnormal event center, and the abnormal event center will perform abnormal result alarm processing.
[0174] It can be seen that under the design framework of the above-mentioned recommendation platform business inspection method, the complex data link characteristics of the recommendation platform are fully considered, and several types of inspection links are carefully extracted. Among them, each inspection link corresponds precisely to a business link in various businesses of the recommendation platform. These links are composed of multiple business nodes, and each business node covers a large number of business indicator elements. Whenever the inspection process is started, the business inspection will be performed one by one from the first business node to the last business node in the order of the inspection link. After all business nodes are executed, the inspection results will be integrated and aggregated with the business node as the basic unit. With the message push mechanism and intuitive page presentation, the operation status and situation of the entire business link can be very clearly and accurately understood.
[0175] The above recommendation platform business inspection method can actively monitor each business link of the recommendation platform system, discover problems in advance, make up for the shortcomings of alarms and oncalls, and effectively ensure the stability of the recommendation platform. In addition, the above recommendation platform business inspection system can integrate multiple forms such as alarms and page presentations. Operation and maintenance personnel can timely perceive the status of each business of the recommendation platform and the status of business nodes on each business chain through a visual interface, so as to quickly locate problems on complex links, lock the scope of problems at a lower cost, and reduce the maintenance cost of the recommendation platform.
[0176] Based on the same inventive concept, corresponding to any of the above-mentioned embodiments and methods, the present disclosure also provides an electronic device, including: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, the recommendation platform service inspection method described in any of the above embodiments is implemented.
[0177] Figure 5 A more specific hardware structure diagram of an electronic device provided in this embodiment is shown, and the device may include: a processor 2010, a memory 2020, an input / output interface 2030, a communication interface 2040, and a bus 2050. The processor 2010, the memory 2020, the input / output interface 2030, and the communication interface 2040 are connected to each other in communication within the device through the bus 2050.
[0178] The processor 2010 can be implemented by a general-purpose CPU (Central Processing Unit), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of this specification.
[0179] The memory 2020 can be implemented in the form of ROM (Read Only Memory), RAM (Random Access Memory), static storage device, dynamic storage device, etc. The memory 2020 can store an operating system and other application programs. When the technical solutions provided in the embodiments of this specification are implemented by software or firmware, the relevant program codes are stored in the memory 2020 and are called and executed by the processor 2010.
[0180] The input / output interface 2030 is used to connect input / output devices to realize information input and output. The input / output devices can be configured in the device as components, or can be externally connected to the device to provide corresponding functions. The input devices can include microphones, various sensors, etc., and the output devices can include displays, speakers, vibrators, indicator lights, etc.
[0181] The communication interface 2040 is used to connect a communication module (not shown) to realize communication interaction between the device and other devices. The communication module can realize communication through a wired mode (such as USB, network cable, etc.) or a wireless mode (such as mobile network, WIFI, Bluetooth, etc.).
[0182] The bus 2050 includes a path that transmits information between the various components of the device (eg, the processor 2010, the memory 2020, the input / output interface 2030, and the communication interface 2040).
[0183] It should be noted that, although the above device only shows the processor 2010, the memory 2020, the input / output interface 2030, the communication interface 2040, and the bus 2050, in the specific implementation process, the device may also include other components necessary for normal operation. In addition, it can be understood by those skilled in the art that the above device may also only include the components necessary for implementing the embodiments of the present specification, and does not necessarily include all the components shown in the figure.
[0184] The electronic device of the above embodiment is used to implement the corresponding recommendation platform service inspection method in any of the above embodiments, and has the beneficial effects of the corresponding method embodiment, which will not be repeated here.
[0185] Based on the same inventive concept, corresponding to any of the above-mentioned embodiment methods, the present disclosure also provides a non-transitory computer-readable storage medium, wherein the non-transitory computer-readable storage medium stores computer instructions, and the computer instructions are used to enable the computer to execute the recommendation platform business inspection method described in any of the above embodiments.
[0186] The computer-readable medium of this embodiment includes permanent and non-permanent, removable and non-removable media, and information storage can be implemented by any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, read-only compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device.
[0187] The computer instructions stored in the storage medium of the above embodiments are used to enable the computer to execute the task processing method described in any of the above embodiments, and have the beneficial effects of the corresponding method embodiments, which will not be repeated here.
[0188] Those skilled in the art should understand that the discussion of any of the above embodiments is merely illustrative and is not intended to imply that the scope of the present disclosure (including the claims) is limited to these examples. Based on the concept of the present disclosure, the technical features in the above embodiments or different embodiments may be combined, the steps may be implemented in any order, and there are many other variations of the different aspects of the embodiments of the present disclosure as described above, which are not provided in detail for the sake of simplicity.
[0189] In addition, to simplify the description and discussion, and in order not to make the embodiments of the present disclosure difficult to understand, the known power / ground connections to the integrated circuit (IC) chips and other components may or may not be shown in the provided figures. In addition, the device can be shown in the form of a block diagram to avoid making the embodiments of the present disclosure difficult to understand, and this also takes into account the fact that the details of the implementation of these block diagram devices are highly dependent on the platform on which the embodiments of the present disclosure will be implemented (that is, these details should be fully within the scope of understanding of those skilled in the art). Where specific details (e.g., circuits) are set forth to describe exemplary embodiments of the present disclosure, it is apparent to those skilled in the art that the embodiments of the present disclosure can be implemented without these specific details or with changes in these specific details. Therefore, these descriptions should be considered illustrative rather than restrictive.
[0190] Although the present disclosure has been described in conjunction with specific embodiments of the present disclosure, many replacements, modifications and variations of these embodiments will be apparent to those skilled in the art from the foregoing description. For example, other memory architectures (e.g., dynamic RAM (DRAM)) may use the embodiments discussed.
[0191] The embodiments of the present disclosure are intended to cover all such substitutions, modifications and variations that fall within the broad scope of the appended claims. Therefore, any omissions, modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the embodiments of the present disclosure should be included in the scope of protection of the present disclosure.
Claims
1. A recommendation platform business inspection system, comprising: An inspection plan generation module is used to generate an inspection plan based on the project information of the service to be inspected and the configuration information of at least one pre-configured inspection link; wherein the inspection plan includes at least one inspection task; each inspection task corresponds to a service link to be inspected; the service link to be inspected includes at least one service node to be inspected; each service node corresponds to at least one service indicator to be inspected; and each service indicator to be inspected corresponds to at least one data source for determining the service indicator; The data tracking module is used to track the data sources associated with each inspection task to obtain data from the data sources; At least one inspection execution module, used to execute the inspection plan based on the data embedding points, and obtain the inspection results of each inspection task respectively; An inspection result summary module, used to summarize the inspection results of each inspection task to obtain the inspection results of the inspection plan; and The display module is used to display the inspection results of the inspection plan.
2. The system according to claim 1, further comprising: A patrol link configuration module, used to pre-configure at least one patrol link; wherein the patrol link configuration module includes: A link configuration unit, used to set inspection link information and set at least one service node for the inspection link; wherein the inspection link information includes: an identifier of the inspection link; A node configuration unit, used to set service node information and set at least one service indicator related to the service node; wherein the service node information includes: an identifier of the service node; An indicator configuration unit is used to set a group of data sources associated with the business indicator and determine a specific method of the business indicator based on the set data sources; wherein, The inspection link configuration information includes: an identifier of the inspection link, an identifier of the service node included in the inspection link, at least one service indicator related to the service node included in the inspection link, a group of data sources associated with the service indicator, and a specific method for determining the service indicator based on the set data source.
3. The system according to claim 1, wherein: The inspection plan generation module includes: An inspection link matching unit, configured to determine at least one target inspection link associated with the service to be inspected based on the project information of the service to be inspected; and The inspection task determination unit is used to generate at least one service link to be inspected based on the project information and the configuration information of the at least one target inspection link, and use each of the service links to be inspected as an inspection task of the inspection plan.
4. The system according to claim 1, further comprising: The periodic scheduling module is used to set a period for service inspection for the service to be inspected.
5. The system according to claim 1, further comprising: A manual scheduling module is used to set inspection tasks that require business inspections; wherein the manual scheduling module includes: An identification query unit, used to provide an identification query interface for a user to query the inspection entity identification; wherein the inspection entity identification includes: the identification of the service link to be inspected or the identification of the service node to be inspected; An inspection target entity receiving unit, used to receive an inspection target entity identifier fed back by a user; and The inspection triggering unit is used to trigger the inspection execution module to perform service inspection on the target entity corresponding to the inspection target entity identifier.
6. The system according to claim 1, wherein: The data embedding module includes: A data reporting setting unit, used to configure the service to be inspected to actively report the inspection data, and cache the inspection data actively reported by the service to be inspected; or, A data interface setting unit is used to configure the service to be inspected to provide a data interface for reading the inspection data.
7. The system according to claim 1, wherein: The inspection execution module includes: at least one executor unit, each used to execute an inspection task in the inspection plan based on the data embedding point.
8. The system according to claim 7, further comprising: Task release module; The inspection plan generating module publishes at least one inspection task included in the inspection plan to the task publishing module; The task publishing module maintains an inspection task queue for caching inspection tasks that have been published but not yet executed; as well as Each executor unit included in the at least one inspection execution module respectively monitors the inspection task queue of the task issuing module; And when it can be used to execute the inspection task, it receives the inspection task from the head of the inspection task queue and executes the received inspection task.
9. The system according to claim 8, wherein: The inspection tasks performed by the executor unit include: Add all service nodes with zero in-degree in the directed acyclic graph corresponding to the inspection task to a stack; Determine whether there is a service node at the top of the stack, if there is a service node at the top of the stack, pop the service node at the top of the stack as the target service node; if there is no service node at the top of the stack, end; Based on the data embedding point, obtain the inspection data of all data sources corresponding to all business indicators corresponding to the target business node; Determine inspection values of all service indicators corresponding to the target service node based on the inspection data; Determine whether there is an abnormal business indicator based on the inspection value, if there is an abnormal business indicator, record the inspection value of the abnormal business indicator, mark the business indicator as an abnormal business indicator, and mark the target business node as an abnormal business node; if there is no abnormal business indicator, record the inspection value of the normal business indicator; Deleting the in-degree of all downstream service nodes in the directed acyclic graph; and De-duplicate the service nodes with zero in-degree among all downstream service nodes in the directed acyclic graph, add them to the stack, and then return to the step of determining whether there is a service node at the top of the stack.
10. The system according to claim 7, further comprising: Backend module; After executing the received inspection tasks, each executor unit included in the at least one inspection execution module writes the inspection results corresponding to the executed inspection tasks into the back-end module; The backend module caches the inspection results corresponding to each inspection task; as well as The inspection result summary module reads the cached inspection results corresponding to each inspection task from the back-end module, and summarizes the inspection results corresponding to each inspection task to obtain the inspection results corresponding to the inspection plan.
11. The system according to claim 1, wherein: The display module comprises: An inspection result display unit, used to display the inspection results of each inspection task included in the inspection plan in order of business inspection time; and / or, The event reporting unit is used to report abnormal service links, abnormal service nodes and abnormal service indicators in the inspection results to the abnormal event center, and the abnormal event center performs abnormal result alarm processing.
12. A recommendation platform service inspection method, comprising: An inspection plan is generated based on the project information of the service to be inspected and the configuration information of at least one pre-configured inspection link; wherein the inspection plan includes at least one inspection task; each inspection task corresponds to a service link to be inspected; the service link to be inspected includes at least one service node to be inspected; each service node corresponds to at least one service indicator to be inspected; and each service indicator to be inspected corresponds to at least one data source; Data points are respectively buried for the data sources associated with each inspection task to obtain data from the data sources; Execute the inspection plan based on the data points, and obtain the inspection results of each inspection task respectively; Summarizing the inspection results of each inspection task to obtain the inspection results of the inspection plan; and The inspection results of the inspection plan are displayed.
13. An electronic device, comprising: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, the recommendation platform service inspection method as claimed in claim 12 is implemented.
14. A non-transitory computer-readable storage medium storing computer instructions, wherein the computer instructions are used to enable a computer to execute the recommendation platform service inspection method according to claim 12.
15. A computer program product, comprising computer program instructions, which, when executed on a computer, enable the computer to execute the recommendation platform service inspection method according to claim 12.