Operation and maintenance method and device of query system, computer readable storage medium and processor

Abstract

The invention discloses an operation and maintenance method and device of a query system, a computer readable storage medium and a processor. The method comprises the steps that a query request of a query object is received, and the query request at least comprises target identification information; based on target identification information in the query request, target full-link log information matched with the target identification information is retrieved from a retrieval server; based on the target full-link log information, determining a service scene targeted by the query task; detecting a query message corresponding to the query task based on the execution standard information in the service scene to obtain a first detection result, and detecting the target full-link log information based on the execution standard information to obtain a second detection result; and adjusting the query message based on the first detection result, and adjusting the service execution process based on the second detection result. The technical problem that the operation and maintenance difficulty of a query system for data interaction based on the extensible markup language is large is solved.

Description

Technical Field

[0001] The present invention relates to the field of system operation and maintenance technology, and in particular to an operation and maintenance method, device, computer-readable storage medium and processor of a query system. Background Art

[0002] Currently, as a universal data exchange format, Extensible Markup Language (XML) is widely used in various business systems due to its good structural characteristics, cross-platform compatibility and easy parsing.

[0003] However, since the data structure and rules of the XML format are relatively complex, reading and understanding XML files requires certain professional knowledge and experience. When the system uses XML as the data exchange format, it will bring difficulties to the operation and maintenance of the system, and special training is required for technical operation and maintenance objects. There are technical problems that make the operation and maintenance of XML systems more difficult.

[0004] With respect to the above-mentioned technical problem that the operation and maintenance of the query system based on the extensible markup language (XML) for data interaction is difficult, no effective solution has been proposed yet. Summary of the invention

[0005] The embodiments of the present invention provide a query system operation and maintenance method, device, computer-readable storage medium and processor to at least solve the technical problem that the operation and maintenance of a query system for data interaction based on extensible markup language is difficult.

[0006] According to one aspect of an embodiment of the present invention, a method for operating and maintaining a query system is provided. The method may include: receiving a query request of a query object, wherein the query request includes at least target identification information, and the query request is used to query the abnormal situation existing in the query task identified by the target identification information during the processing of the query system; based on the target identification information in the query request, retrieving the target full-link log information matching the target identification information from the retrieval server, wherein the retrieval server stores multiple log information carrying identification information; based on the target full-link log information, determining the business scenario targeted by the query task; based on the execution standard information under the business scenario, detecting the query message corresponding to the query task to obtain a first detection result, and based on the execution standard information, detecting the target full-link log information to obtain a second detection result, wherein the query message is in an extensible markup language format, the first detection result is used to at least indicate the format error information and parameter abnormality information existing in the query message, and the second detection result is used to at least indicate the abnormal information existing in the business execution process represented by the target full-link log information; adjusting the query message based on the first detection result, and adjusting the business execution process based on the second detection result.

[0007] Optionally, based on the target identification information in the query request, target full-link log information matching the target identification information is retrieved from the retrieval server, including: retrieving identification information consistent with the target identification information from the retrieval server; sorting and integrating the log information carrying the identification information in the retrieval server according to the timestamp of the identification information to obtain the target full-link log information.

[0008] Optionally, based on the target full-link log information, determining the business scenario targeted by the query task includes: extracting business keywords from the target full-link log information; and determining the business scenario targeted by the query task based on the business keywords.

[0009] Optionally, based on the execution standard information in the business scenario, the query message corresponding to the query task is detected to obtain a first detection result, including: based on the execution standard information in the business scenario, the extensible markup language format corresponding to the query message and the business parameters included in the query message are detected to obtain a first detection result.

[0010] Optionally, based on the executed standard information, the target full-link log information is detected to obtain a second detection result, including: based on the execution standard information in the business scenario, the business execution process represented by the target full-link log information is detected to obtain a second detection result.

[0011] Optionally, the operation and maintenance method of the query system also includes: obtaining log information at key positions in the query system, wherein the key positions include at least the task processing start position, the task processing end position and the switch configuration; adding identification information to the log information; and storing the log information with the added identification information in the retrieval server.

[0012] Optionally, storing the log information with added identification information in the retrieval server includes: cleaning the log information with added identification information to obtain cleaned log information; and storing the cleaned log information in the retrieval server according to a specified format of the retrieval server.

[0013] According to another aspect of an embodiment of the present invention, an operation and maintenance device of a query system is also provided. The device may include: a receiving unit, configured to receive a query request of a query object, wherein the query request includes at least target identification information, and the query request is used to query the abnormal situation existing in the query task identified by the target identification information during the processing of the query system; a retrieval unit, configured to retrieve the target full-link log information matching the target identification information from the retrieval server based on the target identification information in the query request, wherein the retrieval server stores a plurality of log information carrying identification information; a determination unit, configured to determine the business scenario targeted by the query task based on the target full-link log information; a detection unit, configured to detect the query message corresponding to the query task based on the execution standard information under the business scenario to obtain a first detection result, and to detect the target full-link log information based on the execution standard information to obtain a second detection result, wherein the query message is in an extensible markup language format, the first detection result is used to at least indicate the format error information and parameter abnormality information existing in the query message, and the second detection result is used to at least indicate the abnormal information existing in the business execution process represented by the target full-link log information; an adjustment unit, configured to adjust the query message based on the first detection result, and adjust the business execution process based on the second detection result.

[0014] According to another aspect of an embodiment of the present invention, a computer-readable storage medium is also provided, the computer-readable storage medium including a stored program, wherein when the program is executed by a processor, the device where the storage medium is located is controlled to execute the operation and maintenance method of the query system in the embodiment of the present invention.

[0015] According to another aspect of an embodiment of the present invention, a processor is further provided, wherein the processor is used to run a program, wherein when the program is run, the operation and maintenance method of the query system in the embodiment of the present invention is executed.

[0016] According to another aspect of the embodiment of the present invention, a computer program product is provided, which includes computer instructions, and when the computer instructions are executed by a processor, the operation and maintenance method of the query system in the embodiment of the present invention is implemented.

[0017] In an embodiment of the present invention, a plurality of log information carrying identification information is stored in the retrieval server. Based on this, after receiving the query request, the target full-link log information matching the target identification information can be directly retrieved in the retrieval server according to the target identification information included in the query request. After retrieving the target full-link log information, the business scenario for the query task queried by the query request can be further determined according to the target full-link log information, and the query message corresponding to the query task and the target full-link log information are detected according to the business scenario, and the first detection result and the second detection result are obtained respectively. By analyzing the first detection result and the second detection result, the query message and the business execution process can be adjusted in a targeted manner to ensure the smooth execution of the business process. That is, in the entire interactive process, the log data related to the query task can be retrieved only through the target identification information in the query request, and then automatic analysis and detection are performed, which greatly reduces the professional requirements for the operation and maintenance object, so that the operation and maintenance object can quickly realize problem location and troubleshooting, thereby solving the technical problem of the difficulty of operation and maintenance of the query system for data interaction based on extensible markup language in the prior art. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] The drawings described herein are used to provide a further understanding of the present invention and constitute a part of this application. The exemplary embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute an improper limitation of the present invention. In the drawings:

[0019] Figure 1 is a flow chart of an operation and maintenance method of a query system according to an embodiment of the present invention;

[0020] Figure 2 is a schematic diagram of a component module based on an NDC toolbox according to an embodiment of the present invention;

[0021] Figure 3 is a flow chart of an operation and maintenance method of a query system based on XML format according to an embodiment of the present invention;

[0022] Figure 4 is a flow chart of an entry and exit recording method of a query system based on XML format according to an embodiment of the present invention;

[0023] Figure 5 is a schematic diagram of a log storage principle according to an embodiment of the present invention;

[0024] Figure 6 is a schematic diagram of an application location of an NDC toolbox in a system architecture based on XML format according to an embodiment of the present invention;

[0025] Figure 7is a schematic diagram of an operation and maintenance device of a query system according to an embodiment of the present invention. DETAILED DESCRIPTION

[0026] In order to enable those skilled in the art to better understand the scheme of the present invention, the technical scheme in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present invention.

[0027] It should be noted that the terms "first", "second", etc. in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, functional component or device that includes a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, functional components or devices.

[0028] First, some nouns or terms that appear in the description of the embodiments of the present application are subject to the following explanations:

[0029] XML message, XML message is a message encoded in XML, usually used to transmit data in the network. XML message defines the format and structure of messages encoded in XML;

[0030] Retrieval server (Elastic Search, referred to as ES), used for storage and retrieval of log data.

[0031] It should be noted that the collected information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data for display, data for analysis, etc.) involved in this application are information and data authorized by the user or fully authorized by all parties, and the collection, storage, use, processing, transmission, provision, disclosure and application of relevant data are in compliance with relevant laws, regulations and standards, necessary confidentiality measures are taken, and public order and good customs are not violated, and corresponding operation entrances are provided for users to choose to authorize or refuse. For example, an interface is set up between this system and relevant users or institutions to provide users with corresponding operation entrances for users to choose to agree or refuse the results of automated decision-making; if the user chooses to refuse, the expert decision-making process will be entered.

[0032] According to an embodiment of the present invention, an embodiment of an operation and maintenance method of a query system is provided, wherein the query system may be a system for interacting based on data messages in XML format. It should be noted that the steps shown in the flowchart of the accompanying drawings may be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in an order different from that here.

[0033] Figure 1 is a flow chart of an operation and maintenance method of a query system according to an embodiment of the present invention. Figure 1 As shown, the method may include the following steps:

[0034] Step S101: receiving a query request for a query object.

[0035] In the technical solution provided in the above step S101 of the present invention, the query request may be a request triggered by a query object, the query object may be a user, and the query request at least includes target identification information, wherein the target identification information is global transaction identification information (Transaction ID, referred to as TID for short), which may be used to track and identify specific transactions or operations in the query system, wherein the query system may be a system that interacts using data messages in XML format, and the language format of the query request is XML format.

[0036] In this embodiment, after the user submits a query task identified by the target identification information to the query system, the query system will execute the query task and return the query result. If the user has questions about the query result, a query request can be initiated to the query system, wherein the query request includes the target identification information corresponding to the query task, and the target identification information is used to mark the log information associated with the query task in the query system. Based on this, the query system can receive the query request triggered by the query object, and then retrieve the target full-link log information matching the target identification information from the retrieval server through the following step S102.

[0037] Step S102: based on the target identification information in the query request, retrieve the target full-link log information matching the target identification information from the retrieval server.

[0038] In the technical solution provided in the above step S102 of the present invention, a plurality of log information carrying identification information (e.g., TID) is stored in the retrieval server. The retrieval server (ES) is a high-performance distributed search and analysis engine, a platform for log storage and retrieval, and is used to receive log information from various parts of the query system, including XML messages and business execution logs related to TID. These log information are indexed and stored in the retrieval server for fast retrieval and analysis.

[0039] Optionally, in a query system that interacts with XML-formatted data messages, in order to track and associate the full-link log information of each query request and its response, the query system generates a unique TID when processing each transaction and embeds it into the log record. This TID, as the identifier of the transaction, runs through the entire request processing process, including but not limited to data encryption and decryption, cache refresh, token generation, business logic processing and other key links, ensuring the integrity and traceability of the log information. That is, the log information related to a transaction corresponds to a TID, and this log information can be stored in the retrieval server.

[0040] In this embodiment, after receiving the query request in step S101 and extracting the target identification information (TID) in the query request, a search can be performed in the search server (ES) according to the target TID to find the log information associated with the target TID. The search server (ES) can quickly find the log information carrying the target TID according to the TID, such as the request message, the response message, each step information in the business processing flow, and even the error information and abnormal conditions.

[0041] Optionally, after retrieving the log information associated with the target TID from the retrieval server according to the target TID, the retrieved log information can be sorted and integrated in chronological order to obtain the target full-link log information, wherein the target full-link log information contains the complete process of the query task from initiation to final response, which is crucial for analyzing and locating problems.

[0042] For example, if a user encounters a problem when using an XML-based interactive query system, he can send a query request containing a target TID to the operation and maintenance object of the query system. After receiving the query request, the operation and maintenance object can extract the target TID in the query request, and then use the target TID to retrieve the relevant full-link log information from the retrieval server (ES), which provides the necessary information basis for subsequent scene identification, problem location and resolution.

[0043] Step S103: Determine the business scenario targeted by the query task based on the target full-link log information.

[0044] In the technical solution provided in step S103 of the present invention, the business scenario refers to the specific business environment and purpose of the user's operation through the query system. For example, in the toolbox (NDC) under the customer data platform (CDP) product, the business scenario may include flight query, order processing, payment service, ticket refund process, etc.

[0045] In this embodiment, after obtaining the target full-link log information, the specific business scenario targeted by the user's query task can be identified and determined by parsing the business keywords, service call sequence and other information contained in the log information.

[0046] Optionally, after determining the business scenario, the characteristics of the business scenario and the execution standard information can be combined to more effectively detect and locate the problem. For example, check whether there are problems such as parameter filling errors and improper format in the query message corresponding to the query task, where the query message is a message in XML data format; or analyze whether there are abnormal conditions in the execution process of the query task based on log information.

[0047] In this step, by locating the specific business scenario targeted by the query task through the target full-link log information, the background and intention of the user's query request can be determined more accurately, so that the problem can be analyzed and located in a targeted manner, the system's operation and maintenance efficiency can be improved, and the time required for problem location can be reduced.

[0048] Step S104: Based on the execution standard information in the business scenario, the query request is detected to obtain a first detection result, and based on the execution standard information, the target full-link log information is detected to obtain a second detection result.

[0049] In the technical solution provided in the above step S104 of the present invention, the execution standard information refers to the system's specifications and expected standards for XML message formats, parameter requirements, and business process execution in a specific business scenario. These standard information are usually contained in the interface document, which defines the structure of the XML message, the required parameters, the type and range of the parameters, and the normal behavior mode and expected output results of the query system when processing the business scenario. The first detection result can be used to at least indicate the format error information and parameter abnormality information that exist in the query message corresponding to the query task, and the second detection result can be used to at least indicate the abnormal information that exists in the business execution process represented by the target full-link log information.

[0050] In this embodiment, after determining the business scenario targeted by the query request through the above step S103, the query message corresponding to the query task can be detected according to the execution standard information under the business scenario. For example, an automated tool is used to check whether the query message in XML format complies with the execution standard information under a specific business scenario, wherein the first detection result may include any format error information and parameter abnormality information in the query message.

[0051] Optionally, as can be seen from the foregoing introduction, the target full-link log information refers to the log records from the time the user initiates the query task to the time the system returns the response result when the user uses the query system. These log records contain the status information, execution time, execution results, etc. of each service node that processes the query task. Among them, when testing the target full-link log information, you can also use automated detection tools to verify whether the target full-link log information meets the execution standard information under the business scenario. Among them, the second detection result focuses on the abnormal information existing in the business execution process, such as abnormal execution process, abnormal state of the system, or abnormal output results, which are not specifically limited here.

[0052] Optionally, through the first test result and the second test result, the operation and maintenance object can quickly understand whether the format and parameters of the query request meet the system requirements, and whether the query system is executed according to the expected business scenario and process during the request processing. These test results not only help to quickly locate the problem, but also guide the operation and maintenance object to make necessary query request adjustments and business process optimization, thereby improving the efficiency of problem solving and the stability of the system.

[0053] Step S105: adjusting the query message based on the first detection result, and adjusting the service execution process based on the second detection result.

[0054] In the technical solution provided by the above step S105 of the present invention, since the first detection result will identify any format error information and parameter abnormality information in the query message corresponding to the query task, the second detection result may include abnormal situations that may exist in the business process. Based on this, after obtaining the first detection result and the second detection result through the above step S104, the query message corresponding to the query task can be adjusted according to the first detection result to ensure that the query message can be correctly parsed and processed by the query system to avoid subsequent processing failures or abnormalities of the query task due to format or parameter problems. And the business execution process is adjusted and optimized accordingly according to the second detection result to reduce the occurrence of abnormal situations and improve the overall performance and reliability of the system.

[0055] In the above steps S101 to S105, a plurality of log information carrying identification information is stored in the retrieval server. Based on this, after receiving the query request, the target identification information included in the query request can be directly used to retrieve the target full-link log information matching the target identification information in the retrieval server. After retrieving the target full-link log information, the business scenario for the query task queried by the query request can be further determined according to the target full-link log information, and the query message corresponding to the query task and the target full-link log information are detected according to the business scenario, and the first detection result and the second detection result are obtained respectively. By analyzing the first detection result and the second detection result, the query message and the business execution process can be adjusted in a targeted manner to ensure the smooth execution of the business process. That is, in the entire interactive process, the log data related to the query task can be retrieved only through the target identification information in the query request, and then automatic analysis and detection are performed, which greatly reduces the professional requirements for the operation and maintenance object, so that the operation and maintenance object can quickly realize problem location and troubleshooting, thereby solving the technical problem of the difficulty of operation and maintenance of the query system for data interaction based on extensible markup language in the prior art.

[0056] The above method of this embodiment is further introduced below.

[0057] As an optional implementation method, step S102, based on the target identification information in the query request, retrieves the target full-link log information that matches the target identification information from the retrieval server, including: based on the target identification information, retrieving the identification information consistent with the target identification information from the retrieval server; sorting and integrating the log information carrying the identification information in the retrieval server according to timestamps to obtain the target full-link log information.

[0058] In this embodiment, as can be seen from the above introduction, the query request includes target identification information (target TID), which is a globally unique identifier that runs through the entire transaction processing process. In addition, the retrieval server stores the full log data of the query system, which includes detailed log records of each key node in the transaction processing process. These log records all contain TID. Based on this, after receiving the query request, the full-link log information matching the target TID can be retrieved from the retrieval server according to the target TID included in the query request, and the retrieved full-link log information is used as the target full-link log information.

[0059] For example, the target TID is input into the link query module of the NDC toolbox, and the link query module can search for a TID matching the target TID from the search server, and then find the log information associated with the user's query request from the search server.

[0060] Optionally, the retrieved log information contains multiple links in the transaction processing process, and the log records of each link have their own timestamp. In order to clearly display the complete process of transaction processing, the data integration module of the NDC toolbox can sort these log information according to the timestamp, and then integrate the retrieved log information into a coherent full-link log information sequence in chronological order to obtain the target full-link log information. Among them, the target full-link log information not only includes the starting point of the user request, but also includes the call information, response information, and possible exceptions or error information of each service node in the query system processing process, until the end point of the transaction processing. Through this sorting and integration, the operation and maintenance object can easily track the overall picture of the transaction processing, so as to quickly locate the problem. For example, it can be found out which service link has timed out, or which step's XML message format exception caused the processing failure.

[0061] In this step, the log information associated with the query request is retrieved from the retrieval server through the TID, which greatly improves the retrieval efficiency and accuracy of the log information.

[0062] As an optional implementation method, step S103, based on the target full-link log information, determines the business scenario targeted by the query task, including: extracting business keywords from the target full-link log information; based on the business keywords, determines the business scenario targeted by the query task.

[0063] In this embodiment, the target full-link log information is parsed to extract business keywords related to the business, wherein the business keywords can reflect the business scenario targeted by the query task.

[0064] For example, the scene recognition module in the NDC toolbox is used to process the target full-link log information and identify business keywords from it. Business keywords can be specific XML tag names, attribute values, business operation names, service call identifiers, etc., which are not specifically limited here.

[0065] Optionally, after determining the business keywords, the business scenario targeted by the query task can be determined based on the business keywords. For example, the scenario recognition module compares the business keywords with a predefined business scenario mapping table to identify the best matching business scenario, wherein the mapping table includes a keyword list under different business scenarios, wherein the keyword list can be set based on historical query records.

[0066] For example, if "flight query" or flight-related city names frequently appear in the target full-link log information, it can be determined that the problem encountered by the user is in the business process of flight query.

[0067] Optionally, after determining the business scenario, you can further perform more detailed detection on the query message corresponding to the query task based on the execution standard information of the scenario, check whether the XML format of the query message corresponding to the query task meets the format and parameter requirements defined by the scenario, and analyze the target full-link log information to identify whether there are anomalies in the processing flow, such as service call timeout, data processing error, resource competition problem, etc. These detection results based on business scenarios will help the operation and maintenance objects quickly locate the problem so that timely measures can be taken to correct or optimize it, thereby improving the stability of the entire system and user experience.

[0068] As an optional implementation, step S104, based on the execution standard information in the business scenario, detects the query message corresponding to the query task to obtain a first detection result, including: based on the execution standard information in the business scenario, detects the extensible markup language format corresponding to the query message and the query parameters included in the query message to obtain the first detection result.

[0069] In this embodiment, the execution standard information in the business scenario refers to the specifications and expected behaviors that the query system should follow when processing a specific type of request. For example, in the flight query scenario, the query system may need to follow the following rules: the query request in XML message format must contain specific fields and attributes, such as departure, destination, date, etc.; parameter values ​​must be within a reasonable range, for example, the date format should be "YYYY-MM-DD", and the flight number must comply with specific encoding rules; the system's expected process when processing flight query requests, such as first verifying the user's identity, then querying flight information based on the request parameters, and finally returning the query results.

[0070] For example, after determining the business scenario targeted by the query task, the format and parameter information of the query message in XML format can be detected according to the execution standard information of the business scenario to determine whether the query message complies with the predefined format requirements under the business scenario, and whether the parameters in the query message meet the expectations under the business scenario, thereby obtaining a first detection result, wherein the first detection result includes all abnormal or non-standard information obtained after a comprehensive detection of the XML format and business parameters of the query message.

[0071] In this step, the XML format of the query message corresponding to the query task and the business parameters included in the query message are detected through the execution standard information of the business scenario targeted by the query task. This can quickly identify problems in the query message, facilitate the adoption of appropriate measures to adjust the query message or provide feedback to the user, thereby improving the accuracy and efficiency of the operation and maintenance of the query system based on the XML format, reducing the time for troubleshooting problems caused by incorrect message format or non-compliant parameters, and also helping to improve system stability and user experience.

[0072] As an optional implementation method, step S104, based on the executed standard information, detects the target full-link log information to obtain a second detection result, including: based on the execution standard information in the business scenario, detects the business execution process represented by the target full-link log information to obtain a second detection result.

[0073] In this embodiment, by querying the execution standard information in the business scenario targeted by the task and detecting the target full-link log information, it can be determined whether there is any abnormality in the execution process of the query system when processing the business in the business scenario.

[0074] For example, check whether the order of service calls in the system when executing business is consistent with the process defined in the execution standard information. For example, a normal flight query process may involve calling the flight information query service first, then calling the price query service, and finally calling the seat availability check service. If the log information shows that the order is incorrect, this may indicate that there is a defect in the service call logic. This is just an illustrative example.

[0075] Optionally, the business execution process represented by the target full-link log information is detected through the execution standard information in the business scenario to obtain a second detection result, which can help the operation and maintenance object to quickly focus on the problem and take corresponding measures to repair it, thereby improving the operation and maintenance efficiency of the query system, ensuring the stable operation of the query system and optimizing the user experience.

[0076] As an optional implementation, the operation and maintenance method of the query system also includes: obtaining log information at key positions in the query system, wherein the key positions include at least the task processing start position, the task processing end position, and the switch configuration; adding identification information to the log information; and storing the log information with the added identification information in the retrieval server.

[0077] In this embodiment, in the XML-based query system, in order to fully understand and track the entire business processing flow, the query system needs to record detailed log information at certain key locations, which include at least: the task processing start location, the task processing end location, and the switch configuration. Among them, the task processing start location is used to indicate the first node where the query task enters the query system, for example, when the user sends a flight query task in XML format, the query system receives the query task and starts processing. The task processing end location is used to indicate the last node where the user's query task is completely processed by the system and returns a response, for example, after the flight query task is processed, the query system generates an XML response message and sends it to the user. The switch configuration is used to indicate some control logic or configuration information that may exist in the query system, which has an important impact on the execution of the business process. For example, a business switch is set to the closed state, resulting in specific business logic not being executed.

[0078] Optionally, obtaining log information at key locations of the query system means that the query system will record relevant information in detail when a business process starts, ends, and when important configurations change.

[0079] Optionally, in order to be able to associate all relevant log information in a business process, the query system will add a TID to the generated log information. TID is a unique identifier generated by the query system for each transaction process, which is generated from the beginning of the query task submission and runs through the entire business process until the processing is completed. Adding TID to the log information ensures that the log of each processing step is bound to the TID of the transaction, which facilitates the subsequent retrieval and integration of logs based on TID.

[0080] Optionally, the log information with the TID added is stored in the retrieval server, where the retrieval server (ES) is a high-performance distributed search and analysis engine that can store massive amounts of log information and provide efficient full-text search and data analysis capabilities. Storing the log information in the retrieval server (ES) can not only ensure the persistence and security of the log data, but also enable the operation and maintenance object to quickly retrieve all log information related to a specific transaction process through the TID when needed.

[0081] Optionally, when the log information with the TID added is stored in the search server, the log data will be cleaned and formatted to ensure the consistency and readability of the data, and finally the processed log will be stored in the search server (ES).

[0082] In this step, by capturing logs at key locations in the query system, adding TIDs to the log information, and then storing the log information with TIDs added to the retrieval server (ES), a complete log information collection and storage system is established, providing a solid foundation for subsequent rapid operation and maintenance. The operation and maintenance object can use this system to quickly retrieve detailed logs of the entire business processing flow from the retrieval server (ES) based on the target TID in the query request provided by the user, quickly identify the problem, and take appropriate measures to solve the problem, thereby improving the system's operation and maintenance system.

[0083] As an optional implementation, storing the log information with added identification information in the retrieval server includes: cleaning the log information with added identification information to obtain cleaned log information; and storing the cleaned log information in the retrieval server according to the specified format of the retrieval server.

[0084] In this embodiment, since the log information usually contains some redundant information or unstructured data, these data may cause unnecessary burden during storage and retrieval, and reduce the response speed and efficiency of the query system. Based on this, when storing the log information in the retrieval server, the log information can be cleaned first to remove irrelevant or redundant data, and the remaining useful information can be structured to meet the storage standards of the retrieval server.

[0085] Optionally, the data cleaning process of the log information may include: removing irrelevant information, format standardization, etc. Removing irrelevant information is used to indicate filtering out information in the log that is irrelevant to the current business scenario. Format standardization is used to indicate converting the log information into a format that can be efficiently indexed and retrieved by the retrieval server, so as to facilitate the retrieval server to perform fast search and data extraction.

[0086] Optionally, after data cleaning and format standardization of the log information, it can be stored in a retrieval server to provide a data basis for subsequent TID-based rapid retrieval and problem location.

[0087] The technical solution of the embodiment of the present invention is illustrated below in conjunction with preferred implementation modes.

[0088] At present, XML messages are widely used in the development and interaction of backend systems due to their flexible data presentation, excellent portability, scalability, and cross-platform data sharing. At the same time, there are also problems of complexity and readability in systems that use XML as interactive messages. For example, the data structure and rules of the XML format are relatively complex, and reading and understanding XML files requires certain professional knowledge and experience. This will bring difficulties to the operation and maintenance of the system, requiring special training for technical operation and maintenance objects, resulting in technical problems that make the operation and maintenance of systems that use XML as interactive messages more difficult.

[0089] However, an embodiment of the present invention provides an operation and maintenance method for a query system based on the XML format, which records standardized log data at various key locations of the query system, such as business entrances and exits, configuration switches, etc., to ensure that the log contains sufficient information for subsequent analysis and tracking. A TID is added to the log record to uniquely identify each system operation or transaction, so that operations between different components can be tracked and associated in a distributed environment. The log information generated by XML interactions is automatically collected and processed, and the log information is uniformly cleaned up and finally stored in a retrieval server to achieve efficient data retrieval and analysis. When the operation and maintenance object receives a query request from a user, the link query module of the NDC toolbox can be used to input the TID provided by the user to quickly retrieve the full-link log information related to it in the retrieval server. Based on the extracted full-link log information, the scenario recognition module of the NDC toolbox can automatically identify the specific business scenarios requested by users, and then identify the query requests and abnormal information in the retrieved full-link log information according to the business scenarios, helping the operation and maintenance objects to quickly locate the problem and make adjustments, thereby improving the operation and maintenance efficiency of the system and reducing the operation and maintenance objects' dependence on XML expertise, thereby solving the technical problems of the difficulty of system operation and maintenance using XML as interactive messages, and providing strong support for the stable operation and efficient maintenance of the system.

[0090] Optionally, the operation and maintenance method of the system based on the XML format in the embodiment of the present invention needs to be implemented with the help of the NDC toolbox. The main component modules of the NDC toolbox are further introduced below.

[0091] Figure 2 is a schematic diagram of a component module based on an NDC toolbox according to an embodiment of the present invention, such as Figure 2 As shown, the NDC toolbox includes: common tool module, scene recognition module, monitoring alarm module, link query module and data integration module.

[0092] Optionally, the common tool module is used to provide a series of basic service functions for operation and maintenance work, including data encryption and decryption, cache refresh, token generation, XML message definition query, etc. These tools are designed to simplify the process of data processing and security verification to ensure the normal operation of the system and the security of data.

[0093] Optionally, the scenario recognition module is used to quickly convert XML request messages (XML Request, referred to as XMLRQ) into actual business scenarios. By parsing the specific fields and structures of the XML message, the business type requested by the user (such as flight query, payment confirmation, etc.) is identified, laying the foundation for subsequent link tracking and problem location.

[0094] Optionally, the monitoring alarm module is used to read the system log data received in the retrieval server (ES) and analyze and compare the error logs therein. Once an error log that may affect the stable operation of the system is detected, the alarm information will be immediately pushed to the operation and maintenance object to ensure that the problem can be responded to and handled in a timely manner.

[0095] Optionally, the link query module can quickly retrieve the full link log information from ES based on the TID (global transaction ID) provided by the user.

[0096] Optionally, the data integration module is used to comprehensively analyze the information collected by each module in the NDC toolbox, including the results of scene recognition, monitoring alarm information, and detailed logs of link queries. Through data integration, the NDC toolbox can generate a problem location report and provide a one-click problem location and processing solution for the operation and maintenance object.

[0097] Optionally, each module in the NDC toolbox has its own specific functions and tasks, together forming a complete automated tool that can help operation and maintenance objects quickly and accurately locate and handle system problems based on XML format. Through the collaborative work of these modules, the NDC toolbox can significantly improve operation and maintenance efficiency, reduce manual intervention, and improve system stability and security.

[0098] Next, the operation and maintenance method of the query system based on XML format in the embodiment of the present invention is further introduced.

[0099] Figure 3 is a flow chart of an operation and maintenance method of a query system based on XML format according to an embodiment of the present invention, such as Figure 3 As shown, the method comprises the following steps:

[0100] Step S301, record key logs in the query system.

[0101] In this embodiment, detailed log data is recorded at key locations of the query system, such as entry and exit points of business processing, switch configuration, etc.

[0102] Step S302: Generate a TID and add it to the log.

[0103] In this embodiment, a globally unique transaction ID (TID) is generated for each system operation or transaction, and the TID is added to the log output format. The addition of the TID enables the operation and maintenance object to track all logs related to a specific user request, and to associate the processing records of different components even in a distributed environment.

[0104] Step S303: Push the log to ES.

[0105] In this embodiment, the logs generated by the system are pushed to ES for persistent storage. ES provides efficient log retrieval and analysis capabilities and is a key data source for subsequent rapid operation and maintenance.

[0106] Step S304: receiving a TID query request provided by a user.

[0107] In this embodiment, when a user encounters a problem, the user can provide the TID contained in the XML response message to the operation and maintenance object, which uses the TID as a query entry to start the problem location process.

[0108] Step S305: Obtain full logs from ES through the link query module.

[0109] In this embodiment, the operation and maintenance object uses the link query module in the NDC toolbox. After the TID is input, the module retrieves all log information related to the TID from the ES.

[0110] Step S306: Determine the user's question through the scene recognition module.

[0111] In this embodiment, through the scenario recognition module, the NDC toolbox can analyze the extracted full-link log information, identify the business scenario requested by the user, and then determine whether the user has problems such as parameter filling errors based on the business scenario.

[0112] Step S307, collating and analyzing the user access graph.

[0113] In this embodiment, based on time sorting and business processes, the NDC toolbox organizes the complete link log of the user's TID request into a user access diagram with a clear timeline. This diagram shows the processing flow of the user request and the error points at each stage, which facilitates the operation and maintenance object to quickly identify and handle problems.

[0114] In the above steps S301 to S307, the NDC toolbox can significantly improve the operation and maintenance efficiency of the XML format-based system, reduce the dependence of the operation and maintenance objects on XML expertise, and can quickly locate problems and take timely measures to resolve anomalies, thereby ensuring the stable operation of the system.

[0115] Next, the entry and exit log recording method of the query system based on XML format is further introduced.

[0116] Figure 4 is a flow chart of an entry and exit log recording method of a query system based on XML format according to an embodiment of the present invention, such as Figure 4 As shown, the method comprises the following steps:

[0117] Step S401, processing request sensitive data.

[0118] In this embodiment, after the query system receives the query request sent by the user in XML format, it can process the sensitive information in the query request, for example, encrypt, desensitize, etc. the sensitive information in the query request to protect the user's privacy and data security.

[0119] Step S402, determining whether the interface exists.

[0120] In this embodiment, the system checks whether the received query request corresponds to a known interface or service. If the requested interface exists, the system will continue to execute step S403; if not, the process will end directly.

[0121] Step S403, obtaining entry configuration.

[0122] In this embodiment, when it is determined that the request interface exists, the switch state of the interface is further determined, and if the switch of the interface is in the on state, step S404 is executed. If the switch of the interface is in the off state, step S404 is executed.

[0123] Step S404: print the entry request log.

[0124] In this embodiment, before processing a request, the system records an entry log, which generally includes detailed information of the request, such as the XML content of the request, timestamp, client information, etc., as well as the generated TID.

[0125] Step S405: Distribute request processing business logic.

[0126] In this real time, the processing business logic in the query request is assigned to the business module corresponding to the interface, so that the business module corresponding to the interface executes the corresponding business according to the business logic.

[0127] Step S406, obtaining an interface response.

[0128] In this embodiment, after the business logic processing is completed, the system generates a response message in XML format.

[0129] Step S407, obtaining export configuration.

[0130] In this embodiment, the outlet configuration information is obtained, and when the switch of the outlet is in an open state, step S408 is executed; when the switch state of the outlet is in a closed state, step S409 is executed.

[0131] Step S408, print the export log.

[0132] In this embodiment, before returning a response, the system will record an egress log, which usually includes detailed information of the response, such as the XML content of the response, the processing result, a timestamp, etc., and the TID associated with the request.

[0133] Step S409, respond to the user.

[0134] In this embodiment, the system sends the generated XML response message to the user, completing a request-response interaction.

[0135] In the above steps S401 to S409, the steps of how the system records the entry and exit logs in the whole process from receiving the user request to returning the response are described, in which the addition of TID as a key tracking identifier ensures that the full link information of each request can be fully recorded and tracked. This provides the necessary foundation for subsequent problem location, operation and maintenance monitoring and data analysis, and is an important part of achieving stable system operation and efficient operation and maintenance.

[0136] Next, we will further introduce the process of storing logs in ES.

[0137] Figure 5 is a schematic diagram of a log storage principle according to an embodiment of the present invention, such as Figure 5 As shown in the figure, it shows how to use the ELK stack (Elasticsearch, Logstash, Kibana) to collect, process and store system logs. Figure 5 As shown in the figure, the Application Programming Interface Log File (Api Log File) is used to collect logs; the distributed publish-subscribe messaging system (Kafka) is used to receive log data from different sources; the data ingestion component (Logstash) is used to read the log data in Kafka, clean, format, parse and enhance it, and ensure that the log data is recorded and stored in a unified format and structure.

[0138] Optionally, the log data processed by Logstash is written to ES, which is a distributed search and data analysis engine that can store massive amounts of log data and provide fast search and analysis capabilities. In ES, log data is indexed and stored for subsequent retrieval and analysis.

[0139] Next, the application position of the NDC toolbox in the system architecture based on XML format interaction is further introduced.

[0140] Figure 6is a schematic diagram of an application location of an NDC toolbox in a system architecture based on XML format interaction according to an embodiment of the present invention, such as Figure 6 As shown, the user entrance is the front end of the system receiving user requests, which can be a web page (Web) or an application (Application, referred to as APP). Users initiate XML-based business requests through these portals; the tool usage management layer includes the NDC toolbox, which is used to provide functions such as data encryption and decryption, cache refresh, token generation, XML message definition query, as well as key scene recognition, monitoring alarm, link query and data integration capabilities; the business conversion management layer is responsible for converting user requests from XML format to an internally processable format, and converting the results after processing the business logic back to XML format for response; the core business management layer includes specific business modules of the system, such as flight booking (Airshtopping), order processing (Order), payment (Payment), return processing (Return), product management (Product), etc. These modules are responsible for executing business logic based on XML requests; the data storage layer includes MySQL database and Oracle database, which are responsible for storing data in the business process, such as user information, order details, product catalog, etc., and are the data basis for business processing; the operating environment is the system operating hardware and software environment, including the Product Data Platform (PDP for short), independent servers and third-party virtual hosts. This environment provides the resources and external service support required for system operation.

[0141] According to an embodiment of the present invention, there is also provided an operation and maintenance device for a query system. It should be noted that the operation and maintenance device for the query system can be used to execute the operation and maintenance method for the query system in the embodiment.

[0142] Figure 7 Schematic diagram of an operation and maintenance device of a query system according to an embodiment of the present invention. Figure 7 As shown, the operation and maintenance device 700 of the query system may include: a receiving unit 701, a retrieval unit 702, a determination unit 703, a detection unit 704 and an adjustment unit 705.

[0143] The receiving unit 701 is used to receive a query request for a query object, wherein the query request includes at least target identification information, and the query request is used to query an abnormality existing in a query task identified by the target identification information during processing by the query system.

[0144] The retrieval unit 702 is used to retrieve target full-link log information matching the target identification information from a retrieval server based on the target identification information in the query request, wherein the retrieval server stores a plurality of log information carrying identification information.

[0145] The determination unit 703 is used to determine the business scenario targeted by the query task based on the target full-link log information.

[0146] The detection unit 704 is used to detect the query message corresponding to the query task based on the execution standard information in the business scenario to obtain a first detection result, and to detect the target full-link log information based on the execution standard information to obtain a second detection result, wherein the query message is in the extensible markup language format, and the first detection result is used to at least indicate the format error information and parameter abnormality information existing in the query message, and the second detection result is used to at least indicate the abnormal information existing in the business execution process represented by the target full-link log information.

[0147] The adjusting unit 705 adjusts the query message based on the first detection result, and adjusts the service execution process based on the second detection result.

[0148] Optionally, the retrieval unit 702 is also used to: retrieve identification information consistent with the target identification information from the retrieval server; sort and integrate the log information carrying the identification information in the retrieval server according to the timestamp of the identification information to obtain the target full-link log information.

[0149] Optionally, the determination unit 703 is further configured to: extract business keywords from the target full-link log information; and determine the business scenario targeted by the query task based on the business keywords.

[0150] Optionally, the detection unit 704 is further configured to: detect an extensible markup language format corresponding to the query message and a query parameter included in the query message based on execution standard information in a business scenario to obtain a first detection result.

[0151] Optionally, the detection unit 704 is further used to: detect the business execution process represented by the target full-link log information based on the execution standard information in the business scenario, and obtain a second detection result.

[0152] Optionally, the operation and maintenance device 700 of the query system is also used to: obtain log information at key positions in the query system, wherein the key positions include at least the task processing start position, the task processing end position and the switch configuration; add identification information to the log information; and store the log information with the added identification information in the retrieval server.

[0153] Optionally, the operation and maintenance device 700 of the query system is further used to: clean the log information with added identification information to obtain cleaned log information; and store the cleaned log information in the retrieval server according to a specified format of the retrieval server.

[0154] In the operation and maintenance device of the query system, a plurality of log information carrying identification information is stored in the retrieval server. Based on this, after receiving the query request, the target full-link log information matching the target identification information can be directly retrieved in the retrieval server according to the target identification information included in the query request. After retrieving the target full-link log information, the business scenario for the query task queried by the query request can be further determined according to the target full-link log information, and the query message corresponding to the query task and the target full-link log information are detected according to the business scenario, and the first detection result and the second detection result are obtained respectively. By analyzing the first detection result and the second detection result, the query message and the business execution process can be adjusted in a targeted manner to ensure the smooth execution of the business process. That is, in the entire interactive process, the log data related to the query task can be retrieved only through the target identification information in the query request, and then automatic analysis and detection are performed, which greatly reduces the professional requirements for the operation and maintenance object, so that the operation and maintenance object can quickly realize problem location and troubleshooting, thereby solving the technical problem of the difficulty of operation and maintenance of the query system for data interaction based on extensible markup language in the prior art.

[0155] According to an embodiment of the present invention, a computer-readable storage medium is further provided, the storage medium comprising a stored program, wherein the program executes the operation and maintenance method of the query system in the embodiment.

[0156] According to an embodiment of the present invention, a processor is further provided, and the processor is used to run a program, wherein the operation and maintenance method of the query system in the embodiment is executed when the program is run.

[0157] According to another aspect of the embodiments of the present invention, a computer program product is provided, which includes computer instructions, and when the computer instructions are executed by a processor, the operation and maintenance method of the query system in the embodiments is implemented.

[0158] The serial numbers of the above embodiments of the present invention are only for description and do not represent the advantages or disadvantages of the embodiments.

[0159] In the above embodiments of the present invention, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0160] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only schematic. For example, the division of units can be a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.

[0161] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed over multiple units. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0162] In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0163] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent functional component, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software functional component, which is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, a server or a network device, etc.) to perform all or part of the steps of the methods of each embodiment of the present invention. The aforementioned storage medium includes: U disk, Read-Only Memory (ROM), Random Access Memory (RAM), mobile hard disk, magnetic disk or optical disk, etc., various media that can store program codes.

[0164] The above are only preferred embodiments of the present invention. It should be pointed out that, for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present invention. These improvements and modifications should also be regarded as the scope of protection of the present invention.

Claims

1. A query system operation and maintenance method, characterized in that: include: Receiving a query request of a query object, wherein the query request includes at least target identification information, and the query request is used to query an abnormality existing in a query task identified by the target identification information during processing by the query system; Based on the target identification information in the query request, retrieving target full-link log information matching the target identification information from a search server, wherein the search server stores a plurality of log information carrying identification information; Based on the target full-link log information, determine the business scenario targeted by the query task; Based on the execution standard information in the business scenario, the query message corresponding to the query task is detected to obtain a first detection result, and based on the execution standard information, the target full-link log information is detected to obtain a second detection result, wherein the query message is in an extensible markup language format, the first detection result is used to at least indicate the format error information and parameter abnormality information existing in the query message, and the second detection result is used to at least indicate the abnormal information existing in the business execution process represented by the target full-link log information; The query message is adjusted based on the first detection result, and the service execution process is adjusted based on the second detection result.

2. The method according to claim 1, characterized in that: Based on the target identification information in the query request, retrieving target full-link log information matching the target identification information from a retrieval server includes: Retrieving identification information consistent with the target identification information from the search server; The log information carrying the identification information in the retrieval server is sorted and integrated according to the timestamp of the identification information to obtain the target full-link log information.

3. The method according to claim 1, characterized in that Based on the target full-link log information, determining the business scenario targeted by the query task includes: Extracting business keywords from the target full-link log information; Based on the business keywords, the business scenario targeted by the query task is determined.

4. The method according to claim 1, characterized in that Based on the execution standard information in the business scenario, Detecting the query message corresponding to the query task to obtain a first detection result includes: Based on the execution standard information in the business scenario, the extensible markup language format corresponding to the query message and the query parameters included in the query message are detected to obtain the first detection result.

5. The method according to claim 1, characterized in that Based on the executed standard information, the target full-link log information is detected to obtain a second detection result, including: Based on the execution standard information in the business scenario, the business execution process represented by the target full-link log information is detected to obtain the second detection result.

6. The method according to claim 1, characterized in that The method further comprises: At a key position in the query system, the log information is obtained, wherein the key position at least includes a task processing start position, a task processing end position, and a switch configuration; Adding the identification information to the log information; The log information with the added identification information is stored in the search server.

7. The method according to claim 6, characterized in that Storing the log information with the identification information added thereto in the search server includes: Cleaning the log information added with the identification information to obtain the cleaned log information; The cleaned log information is stored in the retrieval server according to a specified format of the retrieval server.

8. An operation and maintenance device for a query system, characterized in that: include: A receiving unit, configured to receive a query request for a query object, wherein the query request includes at least target identification information, and the query request is used to query an abnormality existing in a query task identified by the target identification information during processing by the query system; A retrieval unit, configured to retrieve target full-link log information matching the target identification information from a retrieval server based on the target identification information in the query request, wherein the retrieval server stores a plurality of log information carrying identification information; A determination unit, configured to determine the business scenario targeted by the query task based on the target full-link log information; A detection unit, configured to detect the query message corresponding to the query task based on the execution standard information in the business scenario to obtain a first detection result, and to detect the target full-link log information based on the execution standard information to obtain a second detection result, wherein the query message is in an extensible markup language format, the first detection result is used to at least indicate format error information and parameter abnormality information existing in the query message, and the second detection result is used to at least indicate abnormal information existing in the business execution process represented by the target full-link log information; An adjustment unit is used to adjust the query message based on the first detection result, and adjust the service execution process based on the second detection result.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium includes a stored program, wherein when the program is executed by a processor, the device where the storage medium is located is controlled to execute the method according to any one of claims 1 to 7.

10. A processor, characterized in that: The processor is used to run a program, wherein the program executes the method according to any one of claims 1 to 7 when running.

Images