Order main link state monitoring method and device, computer equipment and storage medium

Abstract

The invention relates to an order main link state monitoring method and device, computer equipment and a storage medium. The method comprises the following steps: acquiring a monitoring instruction for each tenant on a Sass platform; obtaining a tenant identifier corresponding to each tenant according to the monitoring instruction; determining an operation city code corresponding to each tenant according to each tenant identifier, wherein the number of the operation city codes is at least one; generating script input parameters according to each tenant identifier and / or each operation city code; and executing a monitoring script according to the script input parameter to obtain a monitoring result, the monitoring script being used for monitoring the order main link of each tenant of the Sass platform. By adopting the method, the abnormity of the main link of the order can be identified in time.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a method, apparatus, computer equipment, and storage medium for monitoring the status of an order master link. Background Art

[0002] SaaS (Software as a Service) is a model for providing software services to different companies over the internet. This involves securing the main order flow for multiple customers and multiple cities. Each customer has a different order volume, so configuring monitoring for each customer is too costly. Monitoring only the overall order data for all customers can easily lead to problems being overwhelmed and overlooked.

[0003] Currently, automated inspections only use test tenants to perform regression monitoring of the online service capabilities of the main order link to ensure service link stability. However, each online customer's configuration varies. If a customer errs on the order process, causing anomalies in the main order process, these anomalies cannot be identified in a timely manner. Summary of the Invention

[0004] Based on this, it is necessary to provide an order main link status monitoring method, device, computer equipment and storage medium that can promptly identify order main link anomalies in order to address the above technical problems.

[0005] A method for monitoring the status of an order master link, the method comprising:

[0006] Get monitoring instructions for each tenant on the Sass platform;

[0007] Obtain the tenant ID corresponding to each tenant according to the monitoring instructions;

[0008] Determine the operating city code corresponding to each tenant based on each tenant ID, and the number of operating city codes must be at least one;

[0009] Generate script input parameters based on each tenant ID and / or each operating city code;

[0010] The monitoring script is executed according to the script input parameters to obtain the monitoring results. The monitoring script is used to monitor the main order links of each tenant of the Sass platform.

[0011] In one embodiment, obtaining monitoring instructions for each tenant on the Sass platform includes:

[0012] Get the current time;

[0013] If the current time reaches the preset monitoring time, a monitoring instruction is generated for each tenant on the Sass platform.

[0014] In one embodiment, script input parameters are generated based on each tenant identifier and / or each operating city code, including:

[0015] Get location parameters based on the operating city code, and get tenant interface parameters based on the tenant ID.

[0016] Obtain automated driver parameters based on each tenant ID and each operating city code;

[0017] Generate script input parameters based on location parameters, tenant interface parameters, and automated driver parameters.

[0018] In one embodiment, obtaining location parameters according to the codes of each operating city includes:

[0019] Obtain the starting and ending point coordinates from the location database based on the codes of each operating city;

[0020] According to the codes of each operating city, the longitude and latitude coordinates are obtained from the location database;

[0021] Parameterization is performed based on the coordinates of the starting point and end point and the longitude and latitude coordinates to obtain the position parameters.

[0022] In one embodiment, obtaining tenant interface parameters according to each tenant identifier includes:

[0023] Obtain the signature verification key for each tenant ID based on the tenant ID;

[0024] Get the channel value of each tenant ID according to each tenant ID;

[0025] Parameterize the verification key and channel value to obtain the tenant interface parameters.

[0026] In one embodiment, the method further includes:

[0027] Determine abnormal scenarios in the main order link based on monitoring results. The main order link includes user inquiry scenarios, order placement scenarios, order acceptance scenarios, order status flow scenarios, and payment scenarios.

[0028] Return the abnormal scenario to the device where the abnormal tenant is located on the Sass platform.

[0029] In one embodiment, the monitoring script is executed according to the script input parameters to obtain monitoring results, including:

[0030] The monitoring script is executed according to the script input parameters, and the monitoring script is used to judge various scenarios in the main link of the order;

[0031] If all scenarios are judged to be normal, the monitoring result of the order main link is determined to be a normal link;

[0032] When any scenario is determined to be abnormal, the monitoring result of the order main link is determined to be an abnormal link.

[0033] A device for monitoring the status of an order master link, comprising:

[0034] The first acquisition module is used to obtain monitoring instructions for each tenant on the Sass platform;

[0035] The second acquisition module is used to obtain the tenant identifier corresponding to each tenant according to the monitoring instruction;

[0036] A matching module, configured to determine the operating city code corresponding to each tenant according to each tenant identifier, where the number of operating city codes is at least one;

[0037] A generation module is used to generate script input parameters based on each tenant ID and / or each operating city code;

[0038] The execution module is used to execute the monitoring script according to the script input parameters to obtain the monitoring results. The monitoring script is used to monitor the main order links of each tenant of the Sass platform.

[0039] A computer device comprises a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, the following steps are implemented:

[0040] Get monitoring instructions for each tenant on the Sass platform;

[0041] Obtain the tenant ID corresponding to each tenant according to the monitoring instructions;

[0042] Determine the operating city code corresponding to each tenant based on each tenant ID, and the number of operating city codes must be at least one;

[0043] Generate script input parameters based on each tenant ID and / or each operating city code;

[0044] The monitoring script is executed according to the script input parameters to obtain the monitoring results. The monitoring script is used to monitor the main order links of each tenant of the Sass platform.

[0045] A computer-readable storage medium stores a computer program, which, when executed by a processor, implements the following steps:

[0046] Get monitoring instructions for each tenant on the Sass platform;

[0047] Obtain the tenant ID corresponding to each tenant according to the monitoring instructions;

[0048] Determine the operating city code corresponding to each tenant based on each tenant ID, and the number of operating city codes must be at least one;

[0049] Generate script input parameters based on each tenant ID and / or each operating city code;

[0050] The monitoring script is executed according to the script input parameters to obtain the monitoring results. The monitoring script is used to monitor the main order links of each tenant of the Sass platform.

[0051] The above-mentioned order main link status monitoring method, device, computer equipment and storage medium obtain monitoring instructions for each tenant on the Sass platform, obtain the tenant identification corresponding to each tenant according to the monitoring instructions, determine the operating city code corresponding to each tenant according to each tenant identification, and the number of operating city codes is at least one. Script input parameters are generated according to each tenant identification and / or each operating city code, and the monitoring script is executed according to the script input parameters to obtain monitoring results. The monitoring script is used to monitor the order main link of each tenant on the Sass platform.

[0052] Therefore, the tenant identifiers and operating city codes on the Sass platform can be used to generate script input parameters for different tenants and cities. The monitoring script can be executed according to the script input parameters, and regular inspections and monitoring of different tenants and cities can be carried out to ensure that the entire process of each scenario in the main order link runs efficiently and stably, and potential problems can be discovered and resolved in a timely manner, thereby ensuring business continuity. BRIEF DESCRIPTION OF THE DRAWINGS

[0053] Figure 1 This is an application environment diagram of a method for monitoring the status of an order master link in one embodiment;

[0054] Figure 2 1 is a flow chart of a method for monitoring the status of an order master link in one embodiment;

[0055] Figure 3 A structural block diagram of an order master link status monitoring device in one embodiment;

[0056] Figure 4 is a diagram of the internal structure of a computer device in one embodiment;

[0057] Figure 5 FIG. 1 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0058] In order to make the purpose, technical solutions and advantages of this application more clear, the following further describes this application in detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain this application and are not intended to limit this application.

[0059] The order master link status monitoring method provided in this application can be applied to Figure 1In the application environment shown, the first server 102 communicates with the second server 104 via a network. The first server 102 and the second server 104 can be implemented as independent servers or a server cluster consisting of multiple servers. The first server 102 can be the server where the Sass platform is located, and the second server 104 can be a server used for monitoring.

[0060] Specifically, the first server 102 obtains monitoring instructions for each tenant on the Sass platform and sends them to the second server 104. The second server 104 obtains the tenant identifier corresponding to each tenant according to the monitoring instruction, determines the operating city code corresponding to each tenant according to each tenant identifier, and the number of operating city codes is at least one. Script input parameters are generated according to each tenant identifier and / or each operating city code, and the monitoring script is executed according to the script input parameters to obtain the monitoring results. The monitoring script is used to monitor the main link of the order of each tenant on the Sass platform.

[0061] In one embodiment, Figure 2 As shown, a method for monitoring the status of an order master link is provided, which is applied to Figure 1 Taking the second server in the example as an example, the following steps are included:

[0062] Step 202: Obtain monitoring instructions for each tenant on the Sass platform.

[0063] Among them, Software as a Service (SaaS) enables users to use cloud-based applications through an Internet connection. SaaS provides complete software solutions that users can purchase from cloud service providers on a pay-as-you-go basis. Organizations rent applications, and their users can connect to the application through the Internet (usually using a web browser). All infrastructure, middleware, application software, and application data are located in the service provider's data center. The service provider is responsible for managing the hardware and software, and ensuring the availability and security of applications and data according to appropriate service agreements. SaaS allows organizations to quickly build and put applications into production with minimal upfront costs.

[0064] Among them, there is at least one tenant on the Sass platform. The tenant is a merchant who has signed an agreement with the Sass platform, and the monitoring instruction is an instruction to monitor the tenant on the Sass platform. It can be triggered to generate at a scheduled time or through related operations.

[0065] Step 204: Obtain tenant identifiers corresponding to each tenant according to the monitoring instruction.

[0066] The tenant ID uniquely identifies a tenant. Different tenants may have different IDs, and the tenant ID can be used to identify the corresponding tenant. A tenant ID is a unique identifier used to distinguish different tenants in a cloud platform or SaaS (Software as a Service) environment. In a multi-tenant architecture, each tenant has its own unique ID, enabling the system to manage and isolate the resources and usage of different tenants.

[0067] Step 206: Determine the operating city code corresponding to each tenant according to each tenant identifier, and the number of operating city codes is at least one.

[0068] The Operational City Code, a standardized geographic identifier used to identify operational cities, uniquely identifies and locates cities worldwide. The Operational City Code is a crucial component of modern urban management and informatization. It provides a unique digital identifier for cities and is widely used in various fields, including logistics, tourism, and public services.

[0069] Specifically, after obtaining each tenant ID, the city in which each tenant operates is searched using the tenant ID to obtain the corresponding operating city code. The number of operating cities can be at least one, and the number of operating city codes can also be at least one, because each tenant can operate in multiple operating cities.

[0070] Step 208: Generate script input parameters according to each tenant identifier and / or each operating city code.

[0071] Script input parameters are parameters passed to the script when it's written. These parameters provide additional information or instructions during script execution, allowing the script to perform different operations based on different inputs. The specific implementation of script input parameters varies across programming languages. Therefore, the script input parameters here are the parameters that need to be passed to the monitoring script.

[0072] Specifically, after obtaining each tenant ID and operating city code, tenant-specific parameters are retrieved using each tenant ID, city-specific parameters are retrieved using each operating city code, and automated driver parameters are retrieved using each tenant ID and city code. The automated driver parameters are parameters related to the automated driver and are used to simulate the online ride-hailing driver for that tenant in that operating city. Finally, the tenant-specific parameters, city-specific parameters, and automated driver parameters are assembled to obtain the script input parameters.

[0073] Step 210: Execute the monitoring script according to the script input parameters to obtain the monitoring results. The monitoring script is used to monitor the main order link of each tenant of the Sass platform.

[0074] The monitoring script is an automated tool used to regularly check various metrics of the main order link for each tenant on the Sass platform. The main order link includes scenarios such as inquiry, order placement, order acceptance, order status flow, and payment. The monitoring script monitors each scenario of the main order link and generates monitoring results for the main order link. The main order link refers to the entire process from user order placement to order completion, including order generation, processing, payment, delivery, and receipt confirmation. This process involves interaction and collaboration between multiple systems to ensure the smooth completion of orders.

[0075] Therefore, the monitoring script can be used to monitor the main order links of each tenant on the Sass platform, which can ensure the smooth completion of each tenant's orders, and can also promptly discover abnormal order scenarios of each tenant, identify the causes and respond in a timely manner.

[0076] In the above-mentioned order main link status monitoring method, a monitoring instruction for each tenant on the Sass platform is obtained, and the tenant identifier corresponding to each tenant is obtained according to the monitoring instruction. The operating city code corresponding to each tenant is determined according to each tenant identifier, and the number of operating city codes is at least one. Script input parameters are generated according to each tenant identifier and / or each operating city code, and the monitoring script is executed according to the script input parameters to obtain the monitoring results. The monitoring script is used to monitor the order main link of each tenant on the Sass platform.

[0077] Therefore, the tenant identifiers and operating city codes on the Sass platform can be used to generate script input parameters for different tenants and cities. The monitoring script can be executed according to the script input parameters, and regular inspections and monitoring of different tenants and cities can be carried out to ensure that the entire process of each scenario in the main order link runs efficiently and stably, and potential problems can be discovered and resolved in a timely manner, thereby ensuring business continuity.

[0078] In one embodiment, obtaining monitoring instructions for each tenant on the Sass platform includes: obtaining the current time, and if the current time reaches a preset monitoring time, generating monitoring instructions for each tenant on the Sass platform.

[0079] Among them, the Sass platform concentrates multiple joint channels, that is, the Sass platform includes multiple tenants, and can monitor the main order links of each tenant of the Sass platform, and promptly discover abnormalities in the main order links, mainly triggering monitoring through monitoring instructions.

[0080] Specifically, the monitoring instructions for each tenant on the Sass platform can be triggered by timed polling, wherein the timed polling can be understood as a timed event. By setting the timed monitoring time, when the timed time is reached, the monitoring instructions for each tenant on the Sass platform are automatically triggered. Specifically, it can be to obtain the current time, where the current time is the current time on the server, which can be understood as the server time, and at the same time obtain the preset monitoring time, and determine whether the current time reaches the preset monitoring time. If it reaches it, it automatically triggers the generation of monitoring instructions for each tenant on the Sass platform. The preset monitoring time can be determined according to actual business needs, actual product needs or actual application scenarios. On the contrary, if the current time is not the preset monitoring time, wait until the preset monitoring time is reached, and automatically trigger the generation of monitoring instructions.

[0081] In one embodiment, script input parameters are generated according to each tenant identifier and / or each operating city code, including: obtaining location parameters according to each operating city code, obtaining tenant interface parameters according to each tenant identifier, obtaining automated driver parameters according to each tenant identifier and each operating city code, and generating script input parameters according to the location parameters, tenant interface parameters and automated driver parameters.

[0082] Among them, the script input parameters are generated according to each tenant identifier and / or each operating city code. Specifically, the tenant-related parameters are obtained through each tenant identifier, and the tenant-related parameters are determined as tenant interface parameters. In fact, the tenant-related parameters are parameterized to obtain tenant interface parameters. At the same time, the parameters related to the operating city location are obtained through each operating city code, and parameterized to obtain location parameters. The location parameters are parameters related to the location, and the location is within the operating city range.

[0083] Furthermore, you can obtain automated driver parameters using each tenant ID and operating city code. The automated driver here can be understood as a simulated driver, used to simulate driving within the city area where the tenant ID and operating city code match. Finally, the obtained location parameters, tenant interface parameters, and automated driver parameters are assembled to obtain the script input parameters.

[0084] In one embodiment, location parameters are obtained according to the codes of each operating city, including: obtaining the starting and ending point coordinates from the location database according to the codes of each operating city, obtaining the longitude and latitude coordinates from the location database according to the codes of each operating city, and performing parameterization processing based on the starting and ending point coordinates and the longitude and latitude coordinates to obtain location parameters.

[0085] Location parameters are location-related parameters that can be obtained through the operating city codes, including the starting and ending coordinates, as well as the longitude and latitude coordinates. The starting and ending coordinates describe the starting and ending locations of the online ride-hailing vehicle, while the longitude and latitude coordinates are specific locations. Both the starting and ending coordinates and the longitude and latitude coordinates are within the city range corresponding to the operating city code. The location database is a collection of specific location information, including the longitude and latitude coordinates corresponding to each location.

[0086] Furthermore, after obtaining the start and end coordinates and the longitude and latitude coordinates, the start and end coordinates and the longitude and latitude coordinates are parameterized to obtain position parameters. The so-called parameterization refers to converting the start and end coordinates and the longitude and latitude coordinates into parameters. By modifying these parameters, the behavior and output of subsequent monitoring scripts can be controlled, which can improve flexibility and efficiency and facilitate reuse and data analysis.

[0087] In one embodiment, tenant interface parameters are obtained according to each tenant identifier, including: obtaining a signature verification key of each tenant identifier according to each tenant identifier, obtaining a channel channel value of each tenant identifier according to each tenant identifier, and performing parameterization processing according to the signature verification key and the channel channel value to obtain tenant interface parameters.

[0088] Tenant interface parameters are tenant-specific parameters that can be obtained by parameterizing the data obtained using each tenant's ID. Specifically, the signature verification key for each tenant ID can be obtained based on the tenant ID. The so-called signature verification key refers to the public key used to verify digital signatures. During the digital signature verification process, the signature verification key corresponds to the private key used in the signing process. Specifically, the public key is used to encrypt data, while the private key is used to generate the digital signature. Conversely, the public key is used to verify the signature; that is, the signature verification process uses the public key to verify the authenticity of the digital signature. The signature verification key here is the public key used by each tenant to verify the authenticity of the tenant's digital signature.

[0089] You can also retrieve the channel value for each tenant ID based on the tenant ID. In Go, a channel is a mechanism for communication and synchronization between goroutines. A channel can be thought of as a conduit through which data can be sent or received, solving synchronization and data sharing issues between goroutines. The primary function of a channel is to ensure concurrency safety by sharing memory through communication, rather than sharing memory for communication.

[0090] Finally, after obtaining the signature verification key and channel value, they are parameterized to obtain tenant interface parameters. Parameterization converts the signature verification key and channel value into parameters. Modifying these parameters controls the behavior and output of subsequent monitoring scripts, improving flexibility and efficiency and facilitating reuse and data analysis.

[0091] In one embodiment, the above method also includes: determining abnormal scenarios in the order main link based on the monitoring results, the order main link includes the user inquiry scenario, order placement scenario, order acceptance scenario, order status flow scenario and payment scenario, and returning the abnormal scenario to the device where the abnormal tenant is located on the Sass platform.

[0092] The main order chain encompasses multiple scenarios, including inquiry, order placement, order acceptance, order status flow, and payment. Monitoring scripts monitor each of these scenarios to generate monitoring results. The main order chain encompasses the entire process from user order placement to order fulfillment, encompassing order generation, processing, payment, delivery, and receipt confirmation. This process involves interaction and collaboration between multiple systems to ensure smooth order completion.

[0093] Among them, the inquiry scenario is the stage where online car-hailing users ask about prices, the ordering scenario is the stage where online car-hailing users rent cars or place orders, the order-receiving scenario is the stage where online car-hailing drivers receive orders from online car-hailing users, the order status flow scenario is the stage where online car-hailing orders go through the order status from order placement to completion, and the payment scenario is the stage where online car-hailing users complete payment.

[0094] Specifically, after obtaining the monitoring results, the abnormal scenarios in the main link of the order are determined based on the monitoring results, and returned to the device where the abnormal tenant is located through the Sass platform. In this way, the abnormal scenarios can be understood in a timely manner, the causes can be identified, and responses can be taken.

[0095] In one embodiment, a monitoring script is executed according to the script input parameters to obtain a monitoring result, including: executing the monitoring script according to the script input parameters, judging each scenario of the order main link through the monitoring script, when each scenario is judged to be normal, the monitoring result of the order main link is determined to be a normal link, and when any scenario is judged to be abnormal, the monitoring result of the order main link is determined to be an abnormal link.

[0096] Among them, the monitoring script is executed according to the script input parameters, and the monitoring result can be specifically that the monitoring script is executed according to the script input parameters, and the monitoring script monitors and judges each scenario of the order main link to determine whether there is any abnormality in each scenario. If there is no abnormality in each scenario, it means that there is no abnormality in the order main link corresponding to the operating city code under the tenant identifier, and it is a normal order link. Each environment is operating normally without any problems.

[0097] On the contrary, when the monitoring script determines that an abnormality occurs in any scenario, it means that an abnormality occurs in the main order link corresponding to the operating city code under the tenant ID. The monitoring result of the main order link can be determined as an abnormal order link, and returned to the Sass platform. The abnormal tenant is informed through the Sass platform, so that the abnormality can be discovered and responded to in a timely manner, the cause can be investigated, the abnormality can be resolved, and the smooth completion of the online car-hailing order can be ensured.

[0098] It should be understood that, although the various steps in the above flow chart are shown in sequence as indicated by the arrows, these steps are not necessarily performed in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order restriction on the execution of these steps, and these steps can be performed in other orders. Moreover, at least a portion of the steps in the above flow chart may include multiple sub-steps or multiple stages, and these sub-steps or stages are not necessarily performed at the same time, but can be performed at different times, and the execution order of these sub-steps or stages is not necessarily to be performed in sequence, but can be performed in turn or alternately with other steps or at least a portion of the sub-steps or stages of other steps.

[0099] In one embodiment, Figure 3 As shown, an order master link status monitoring device 300 is provided, comprising: a first acquisition module 302, a second acquisition module 304, a matching module 306, a generation module 308 and an execution module 310, wherein:

[0100] The first acquisition module 302 is used to obtain monitoring instructions for each tenant on the Sass platform.

[0101] The second acquisition module 304 is configured to acquire a tenant identifier corresponding to each tenant according to the monitoring instruction.

[0102] The matching module 306 is configured to determine the operating city code corresponding to each tenant according to each tenant identifier, where the number of the operating city code is at least one.

[0103] The generation module 308 is used to generate script input parameters according to each tenant identifier and / or each operating city code.

[0104] The execution module 310 is used to execute the monitoring script according to the script input parameters to obtain the monitoring results. The monitoring script is used to monitor the main order link of each tenant of the Sass platform.

[0105] In one embodiment, the first acquisition module 302 acquires the current time, and generates a monitoring instruction for each tenant on the Sass platform if the current time reaches a preset monitoring time.

[0106] In one embodiment, the generation module 308 obtains location parameters based on the operating city codes, obtains tenant interface parameters based on the tenant identifiers, obtains automated driver parameters based on the tenant identifiers and the operating city codes, and generates script input parameters based on the location parameters, tenant interface parameters, and automated driver parameters.

[0107] In one embodiment, the generation module 308 obtains the starting and ending point coordinates from the location database according to the codes of each operating city, obtains the longitude and latitude coordinates from the location database according to the codes of each operating city, and performs parameterization processing based on the starting and ending point coordinates and the longitude and latitude coordinates to obtain location parameters.

[0108] In one embodiment, the generation module 308 obtains the signature verification key of each tenant identifier according to each tenant identifier, obtains the channel channel value of each tenant identifier according to each tenant identifier, performs parameterization processing according to the signature verification key and the channel channel value, and obtains the tenant interface parameters.

[0109] In one embodiment, the generation module 308 determines the abnormal scenario in the order main link based on the monitoring results. The order main link includes the user inquiry scenario, order placement scenario, order acceptance scenario, order status flow scenario and payment scenario, and returns the abnormal scenario to the device where the abnormal tenant is located on the Sass platform.

[0110] In one embodiment, the execution module 310 executes the monitoring script according to the script input parameters, and judges each scenario of the order main link through the monitoring script. When each scenario is judged to be normal, the monitoring result of the order main link is determined to be a normal link. When any scenario is judged to be abnormal, the monitoring result of the order main link is determined to be an abnormal link.

[0111] The specific definition of the order master link status monitoring device can be found in the definition of the order master link status monitoring method described above and will not be repeated here. Each module in the above-mentioned order master link status monitoring device can be implemented in whole or in part through software, hardware, or a combination thereof. Each of the above-mentioned modules can be embedded in or independent of a processor in a computer device in hardware form, or can be stored in a memory in a computer device in software form, so that the processor can call and execute the corresponding operations of each of the above modules.

[0112] In one embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as follows: Figure 4 As shown. The computer device includes a processor, memory, network interface, and database connected via a system bus. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operation of the operating system and computer program in the non-volatile storage medium. The database of the computer device is used to store monitoring results. The network interface of the computer device is used to communicate with an external terminal via a network connection. When the computer program is executed by the processor, it implements a method for monitoring the status of an order master link.

[0113] In one embodiment, a computer device is provided. The computer device may be a terminal, and its internal structure diagram may be as follows: Figure 5 As shown. The computer device includes a processor, memory, network interface, display screen and input device connected via a system bus. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and computer program in the non-volatile storage medium. The network interface of the computer device is used to communicate with an external terminal via a network connection. When the computer program is executed by the processor, a method for monitoring the status of an order master link is implemented. The display screen of the computer device can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer device can be a touch layer covering the display screen, or a button, trackball or touchpad provided on the computer device housing, or an external keyboard, touchpad or mouse.

[0114] Those skilled in the art will understand that Figure 4 or Figure 5 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than shown in the figure, or combine certain components, or have a different component arrangement.

[0115] In one embodiment, a computer device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, the following steps are implemented: obtaining monitoring instructions for each tenant on a Sass platform, obtaining a tenant identifier corresponding to each tenant according to the monitoring instructions, determining an operating city code corresponding to each tenant according to each tenant identifier, wherein the number of operating city codes is at least one, generating script input parameters according to each tenant identifier and / or each operating city code, executing a monitoring script according to the script input parameters, and obtaining monitoring results. The monitoring script is used to monitor the main order link of each tenant on the Sass platform.

[0116] In one embodiment, when the processor executes the computer program, it further implements the following steps: obtaining the current time, and if the current time reaches the preset monitoring time, generating a monitoring instruction for each tenant on the Sass platform.

[0117] In one embodiment, when the processor executes the computer program, it also implements the following steps: obtaining location parameters based on each operating city code, obtaining tenant interface parameters based on each tenant identifier, obtaining automated driver parameters based on each tenant identifier and each operating city code, and generating script input parameters based on the location parameters, tenant interface parameters, and automated driver parameters.

[0118] In one embodiment, when the processor executes the computer program, it also implements the following steps: obtaining the starting and ending point coordinates from the location database according to the codes of each operating city, obtaining the longitude and latitude coordinates from the location database according to the codes of each operating city, and performing parameterization processing based on the starting and ending point coordinates and the longitude and latitude coordinates to obtain location parameters.

[0119] In one embodiment, when the processor executes the computer program, it also implements the following steps: obtaining the signature verification key of each tenant identification according to each tenant identification, obtaining the channel channel value of each tenant identification according to each tenant identification, and performing parameterization processing based on the signature verification key and the channel channel value to obtain tenant interface parameters.

[0120] In one embodiment, when the processor executes the computer program, it also implements the following steps: determining abnormal scenarios in the order main link based on the monitoring results, the order main link includes the user inquiry scenario, order placement scenario, order acceptance scenario, order status flow scenario and payment scenario, and returning the abnormal scenario to the device where the abnormal tenant is located on the Sass platform.

[0121] In one embodiment, when the processor executes the computer program, it also implements the following steps: executing the monitoring script according to the script input parameters, judging each scenario of the order main link through the monitoring script, when each scenario is judged to be normal, the monitoring result of the order main link is determined to be a normal link; when any scenario is judged to be abnormal, the monitoring result of the order main link is determined to be an abnormal link.

[0122] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the following steps are implemented: obtaining monitoring instructions for each tenant on the Sass platform, obtaining a tenant identifier corresponding to each tenant according to the monitoring instructions, determining an operating city code corresponding to each tenant according to each tenant identifier, the number of operating city codes being at least one, generating script input parameters according to each tenant identifier and / or each operating city code, executing a monitoring script according to the script input parameters, and obtaining a monitoring result. The monitoring script is used to monitor the main order link of each tenant on the Sass platform.

[0123] In one embodiment, when the computer program is executed by the processor, the following steps are further implemented: obtaining the current time, and if the current time reaches the preset monitoring time, generating a monitoring instruction for each tenant on the Sass platform.

[0124] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: obtaining location parameters based on each operating city code, obtaining tenant interface parameters based on each tenant identifier, obtaining automated driver parameters based on each tenant identifier and each operating city code, and generating script input parameters based on the location parameters, tenant interface parameters and automated driver parameters.

[0125] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: obtaining the starting and ending point coordinates from the location database according to the codes of each operating city, obtaining the longitude and latitude coordinates from the location database according to the codes of each operating city, and performing parameterization processing based on the starting and ending point coordinates and the longitude and latitude coordinates to obtain location parameters.

[0126] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: obtaining the signature verification key of each tenant identification according to each tenant identification, obtaining the channel channel value of each tenant identification according to each tenant identification, and performing parameterization processing based on the signature verification key and the channel channel value to obtain tenant interface parameters.

[0127] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: determining abnormal scenarios in the order main link based on the monitoring results, the order main link includes the user inquiry scenario, order placement scenario, order acceptance scenario, order status flow scenario and payment scenario, and returning the abnormal scenario to the device where the abnormal tenant is located on the Sass platform.

[0128] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: executing the monitoring script according to the script input parameters, judging each scenario of the order main link through the monitoring script, when each scenario is judged to be normal, the monitoring result of the order main link is determined to be a normal link, and when any scenario is judged to be abnormal, the monitoring result of the order main link is determined to be an abnormal link.

[0129] Those skilled in the art will appreciate that all or part of the processes in the above-mentioned embodiment methods can be implemented by instructing the relevant hardware through a computer program. The computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM) or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. As an illustration and not limitation, RAM is available in many forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchl ink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).

[0130] The technical features of the above embodiments can be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0131] The above-described embodiments merely represent several implementation methods of the present application. While the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the present invention. It should be noted that a person skilled in the art could make various modifications and improvements without departing from the spirit of the present application, all of which fall within the scope of protection of the present application. Therefore, the scope of protection of the present patent application shall be determined by the appended claims.

Claims

1. A method for monitoring the status of an order master link, the method comprising: Get monitoring instructions for each tenant on the Sass platform; Obtaining tenant identifiers corresponding to the tenants according to the monitoring instructions; Determining, according to each tenant identifier, an operating city code corresponding to each tenant, where the number of the operating city code is at least one; Generate script input parameters according to each tenant identifier and / or each operating city code; The monitoring script is executed according to the script input parameters to obtain the monitoring results. The monitoring script is used to monitor the main link of the order of each tenant of the Sass platform.

2. The method according to claim 1, characterized in that The acquisition of monitoring instructions for each tenant on the Sass platform includes: Get the current time; If the current time reaches the preset monitoring time, a monitoring instruction is generated for each tenant on the Sass platform.

3. The method according to claim 1, characterized in that The script input parameters generated according to each tenant identifier and / or each operating city code include: Acquire location parameters according to the operating city codes, and acquire tenant interface parameters according to the tenant identifiers; Obtaining automated driver parameters according to each of the tenant identifiers and each of the operating city codes; The script input parameter is generated according to the location parameter, the tenant interface parameter, and the automation driver parameter.

4. The method according to claim 3, characterized in that The obtaining of location parameters according to the operating city codes includes: Obtaining the starting and ending point coordinates from the location database according to the codes of the respective operating cities; longitude and latitude coordinates from the location database according to the codes of the respective operating cities; Parameterization is performed based on the start and end point coordinates and the longitude and latitude coordinates to obtain the position parameters.

5. The method according to claim 3, characterized in that The acquiring of tenant interface parameters according to each tenant identifier includes: Obtaining a signature verification key for each tenant identifier according to each tenant identifier; Obtaining a channel value for each tenant identifier according to each tenant identifier; Parameterization is performed according to the signature verification key and the channel value to obtain the tenant interface parameters.

6. The method according to claim 3, characterized in that The method further comprises: Determine abnormal scenarios in the order main link based on the monitoring results, where the order main link includes user inquiry scenarios, order placement scenarios, order acceptance scenarios, order status flow scenarios, and payment scenarios; The abnormal scenario is returned to the device where the abnormal tenant is located on the Sass platform.

7. The method according to claim 1, characterized in that The step of executing the monitoring script according to the script input parameters to obtain the monitoring results includes: Executing the monitoring script according to the script input parameters, and judging each scenario of the order main link through the monitoring script; When all the scenarios are determined to be normal, the monitoring result of the order main link is determined to be a normal link; When any of the scenarios is determined to be abnormal, the monitoring result of the order main link is determined to be an abnormal link.

8. An order master link status monitoring device, characterized in that: The device comprises: The first acquisition module is used to obtain monitoring instructions for each tenant on the Sass platform; A second acquisition module is used to obtain the tenant identifier corresponding to each tenant according to the monitoring instruction; a matching module, configured to determine, based on each tenant identifier, an operating city code corresponding to each tenant, where the number of the operating city code is at least one; A generation module, configured to generate script input parameters according to each tenant identifier and / or each operating city code; An execution module is used to execute a monitoring script according to the script input parameters to obtain a monitoring result. The monitoring script is used to monitor the main order link of each tenant of the Sass platform.

9. A computer 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 computer program, the steps of the method according to any one of claims 1 to 7 are implemented.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 7 are implemented.

Images