RPA, AI and LLM-based server product operation and maintenance method, device and equipment for realizing Agent, and storage medium

Abstract

The invention provides an RPA, AI and LLM-based operation and maintenance method, device and equipment of a server product for realizing Agent and a storage medium, the operation and maintenance method is applied to an operation and maintenance tool platform, the operation and maintenance tool platform is configured with an operation and maintenance tool library, the operation and maintenance tool library comprises a plurality of operation and maintenance tools, each operation and maintenance tool is used for executing different operation and maintenance operations, and the operation and maintenance tools are used for executing different operation and maintenance operations. The method comprises the steps that configuration information of a target operation and maintenance object in a current operation environment is obtained, the target operation and maintenance object and a current operation and maintenance tool platform are deployed on the same server, and the configuration information comprises host configuration information, middleware configuration information and service configuration information; and calling a target operation and maintenance tool based on the configuration information and the operation and maintenance demand, so as to execute an operation and maintenance operation corresponding to the operation and maintenance demand through the target operation and maintenance tool. By adopting the technical scheme, the operation and maintenance efficiency of the server product is effectively improved.

Description

Technical Field

[0001] This application relates to the field of operation and maintenance technology, and in particular to an operation and maintenance method, apparatus, equipment and storage medium for server-side products that implement agents based on RPA, AI and LLM. Background Technology

[0002] Robotic Process Automation (RPA) uses specific "robot software" to simulate human operations on a computer and automatically execute process tasks according to rules.

[0003] Artificial intelligence (AI) is a technical science that studies and develops theories, methods, technologies, and application systems for simulating, extending, and expanding human intelligence.

[0004] Large Language Models (LLMs) are models trained on massive amounts of text that can recognize human language, perform language-related tasks, and have a large number of parameters.

[0005] Artificial Intelligence Agents (AI Agents) are capable of perceiving their environment, making decisions, and executing actions. Unlike traditional artificial intelligence, they possess the ability to think and act independently, and can utilize tools to achieve given goals. AI Agents are based on Large Language Models (LLMs) as their core computing engine, enabling them to engage in dialogue, perform tasks, reason, and exhibit a degree of autonomy. They possess the ability to autonomously understand, perceive, plan, remember, and use tools, and can automate complex tasks. Specifically, LLM-driven AI Agents, composed of various AI capabilities, can interact with employees using natural language, understand employee instructions and needs, and provide feedback and responses; they can acquire domain-specific knowledge relevant to the business to complete complex professional tasks; they can break down complex tasks into several executable tasks and use data and tools to complete them; they can also collaborate with employees, and AI Agents can collaborate with each other to complete complex tasks, enabling digital employees to leap from automation to intelligence, helping employees complete their work more efficiently, and fully realizing human-machine collaboration.

[0006] In related business operations, maintenance (O&M) work is typically performed manually by O&M personnel. When O&M personnel discover problems in product operation, they need to troubleshoot the issues one by one and determine solutions. For problems with different modules of the product, multiple O&M personnel often need to work together to determine solutions. This O&M approach consumes a lot of time and energy, resulting in extremely low O&M efficiency. Summary of the Invention

[0007] This application provides an operation and maintenance method, apparatus, device, and storage medium for server-side products that implement agents based on RPA, AI, and LLM, to solve the problems existing in related technologies. The technical solution is as follows: Firstly, embodiments of this application provide an operation and maintenance method for a server-side product implementing an agent based on RPA, AI, and LLM. This operation and maintenance method is applied to an operation and maintenance tool platform, which is configured with an operation and maintenance tool library containing multiple operation and maintenance tools. Each operation and maintenance tool is used to perform different operation and maintenance operations. The operation and maintenance method includes: Obtain the configuration information of the target operation and maintenance object in the current operating environment. The target operation and maintenance object and the current operation and maintenance tool platform are deployed on the same server. The configuration information includes host configuration information, middleware configuration information and service configuration information. The target operation and maintenance object includes the RPA server platform, intelligent document processing platform, intelligent agent document processing platform and intelligent agent process automation platform. Based on configuration information and operational requirements, the target operational tool is invoked to perform operational operations corresponding to the operational requirements.

[0008] In one implementation, invoking the target operation and maintenance tool based on configuration information and operation and maintenance requirements includes: In response to the request to add an operation and maintenance tool, the parameter configuration interface of the operation and maintenance tool is displayed. After the configuration of the target operation and maintenance tool is completed, if a run request for the target operation and maintenance tool is received, the corresponding target operation and maintenance tool is called based on the configuration information and the configured operation and maintenance tool parameter information. The operation and maintenance tool parameters include the tool name, tool type, execution action and execution parameters. or, The system detects the running status of the target operation and maintenance object based on the configuration information, determines the corresponding target operation and maintenance tool based on the abnormal detection items in the detection results, and calls the target operation and maintenance tool.

[0009] In one implementation, detecting the running status of the target maintenance object based on configuration information includes: Obtain the monitoring platform's detection report on the target operation and maintenance object, and determine the operating status of the target operation and maintenance object based on the detection results in the inspection report. The detection results include abnormal prompt information and corresponding handling methods. The handling methods corresponding to the abnormal prompt information are obtained by the monitoring platform through calling the Natural Language Processing (NLP) service to analyze the actual operating indicators of each item to be detected. or, The running status of each item to be detected is obtained based on the configuration information, and the running status is detected based on the created inspection task. Each item to be detected includes the system layer basic environment, the application services of the target maintenance object, and the middleware status.

[0010] In one implementation, the operational status is detected based on a created inspection task, including: In response to the request to create an inspection task, the inspection task's detection parameter configuration interface is displayed. The detection parameter configuration interface is used to configure the detection parameters of the inspection task, including the detection start time, detection end time, and detection frequency. After the inspection task is configured, the operating status of each inspection item is compared with the corresponding standard operating indicators, and abnormal inspection items that do not meet the corresponding standard operating indicators are marked.

[0011] In one implementation, the corresponding target operation and maintenance tool is determined based on the abnormal detection items in the detection results, including: When a request to view the inspection report of any inspection task is received, the inspection report of the inspection task is displayed on the current interface. The inspection report records the actual operating indicators of each inspection item. When a request to view the runtime log of an anomaly detection item is received, the runtime log of the anomaly detection item is displayed. Determine the target operation and maintenance tool corresponding to the anomaly detection item based on the operation log.

[0012] In one implementation, after invoking the target operation and maintenance tool, the method provided in this application further includes: Generate operation and maintenance tasks corresponding to the target operation and maintenance tool.

[0013] In one embodiment, the method provided in this application further includes: When a viewing request for any type of operation and maintenance task is received, the task details corresponding to the viewing request are displayed. The types of operation and maintenance tasks include: operation and maintenance tasks in progress, completed historical operation and maintenance tasks, inspection tasks, and task plans.

[0014] In one implementation, after adding the maintenance tools, the method provided in this application further includes: In response to the task plan creation request, the task plan execution strategy setting interface is displayed. The execution strategy setting interface is used to configure the target operation and maintenance tools and task triggering rules corresponding to the task plan. The task triggering rules include task start time, task end time, task running frequency and task repeated execution time. After configuring the execution strategy, the corresponding tasks are executed according to the execution parameters of the target operation and maintenance tool and the configured task triggering rules.

[0015] In one implementation, the functional models corresponding to each operation and maintenance tool are built using the following method: Create the data layer Action entity for the operation and maintenance tool, which serves as the carrier of the operation and maintenance tool; Configure the type field of the Action entity to establish an association between the type field and the class name of the execution action of the operation and maintenance tool, so as to bind the execution action type corresponding to the operation and maintenance tool; The metadata interface for deploying and executing actions is enabled to query the type field corresponding to the Action entity. The metadata interface is used to provide the front-end application layer with services for obtaining, enumerating, and configuring tool types.

[0016] In one implementation, the operation and maintenance tools include: disk cleanup tools, product configuration modification tools, product service recovery tools, environment anomaly recovery tools, and data recovery and backup tools, wherein the operation and maintenance tools are generated through an Agent.

[0017] Secondly, embodiments of this application provide an operation and maintenance device for server-side products implementing agents based on RPA, AI, and LLM. This device includes: The configuration information acquisition module is used to acquire the configuration information of the target operation and maintenance object in the current operating environment. The target operation and maintenance object and the current operation and maintenance tool platform are deployed on the same server. The configuration information includes host configuration information, middleware configuration information and service configuration information. The target operation and maintenance object includes the RPA server platform, intelligent document processing platform, intelligent agent document processing platform and intelligent agent process automation platform. The target operation and maintenance tool invocation module is used to invoke the target operation and maintenance tool based on configuration information and operation and maintenance requirements, so as to execute the operation and maintenance operations corresponding to the operation and maintenance requirements through the target operation and maintenance tool.

[0018] In one implementation, the target operation and maintenance tool calls the module, including: The first invocation unit is used to respond to the request to add an operation and maintenance tool, display the parameter configuration interface of the operation and maintenance tool, and after completing the configuration of the target operation and maintenance tool, if a run request for the target operation and maintenance tool is received, invoking the corresponding target operation and maintenance tool based on the configuration information and the configured operation and maintenance tool parameter information. The operation and maintenance tool parameters include the tool name, tool type, execution action, and execution parameters; or, The second invocation unit is used to detect the running status of the target operation and maintenance object based on the configuration information, determine the corresponding target operation and maintenance tool according to the abnormal detection items in the detection results, and invoke the target operation and maintenance tool.

[0019] In one implementation, the second calling unit includes: An external detection report identification and acquisition subunit is used to acquire the detection report of the target maintenance object from the monitoring platform, and determine the operating status of the target maintenance object based on the detection results in the inspection report. The detection results include abnormal prompts and corresponding handling methods. The handling methods are obtained by the monitoring platform through natural language processing (NLP) services analyzing the actual operating indicators of each item to be detected; or... The inspection task execution subunit is used to obtain the running status of each item to be inspected based on the configuration information, and to inspect the running status based on the created inspection task. Each item to be inspected includes the system layer basic environment, the application services of the target maintenance object, and the middleware status.

[0020] In one implementation, the inspection task execution subunit is specifically used for: In response to the request to create an inspection task, the inspection task's detection parameter configuration interface is displayed. The detection parameter configuration interface is used to configure the detection parameters of the inspection task, including the detection start time, detection end time, and detection frequency. After the inspection task is configured, the operating status of each inspection item is compared with the corresponding standard operating indicators, and abnormal inspection items that do not meet the corresponding standard operating indicators are marked.

[0021] In one implementation, the second calling unit includes: The inspection report viewing sub-unit is used to display the inspection report of any inspection task on the current interface when a viewing request for the inspection report of any inspection task is received. The runtime log display subunit is used to display the runtime log of the exception detection item when a request to view the runtime log of the exception detection item is received. The target operation and maintenance tool determination subunit is used to determine the target operation and maintenance tool corresponding to the anomaly detection item based on the operation log.

[0022] In one embodiment, the apparatus provided in this application further includes: The operation and maintenance task generation module is used to generate operation and maintenance tasks corresponding to the target operation and maintenance tool after the target operation and maintenance tool is invoked.

[0023] In one embodiment, the apparatus provided in this application further includes: The task details viewing module is used to display the task details corresponding to any type of operation and maintenance task when a viewing request is received. The types of operation and maintenance tasks include: operation and maintenance tasks in progress, completed historical operation and maintenance tasks, inspection tasks, and task plans.

[0024] In one embodiment, the apparatus provided in this application further includes: The task plan generation module is used to respond to the task plan creation request after the operation and maintenance tools are added and display the task plan execution strategy setting interface. The execution strategy setting interface is used to configure the target operation and maintenance tools and task triggering rules corresponding to the task plan. The task triggering rules include task start time, task end time, task running frequency and task repeat execution time. The task scheduling and execution module is used to execute corresponding tasks according to the execution parameters of the target operation and maintenance tool and the configured task triggering rules after the execution strategy has been configured.

[0025] In one implementation, the functional models corresponding to each operation and maintenance tool are built through the following modules: The data layer creation module is used to create data layer Action entities for the operation and maintenance tools, which serve as the carrier of the operation and maintenance tools. The action association module is used to configure the type field of the Action entity, so as to establish an association relationship between the type field and the class name of the action to be executed by the operation and maintenance tool, and to bind the action type corresponding to the operation and maintenance tool. The interface deployment module is used to deploy the metadata interface for executing actions, enabling the metadata interface to query the type field corresponding to the Action entity. The metadata interface is used to provide the front-end application layer with services for obtaining, enumerating, and configuring tool types.

[0026] In one implementation, the operation and maintenance tools include: disk cleanup tools, product configuration modification tools, product service recovery tools, environment anomaly recovery tools, and data recovery and backup tools, wherein each operation and maintenance tool is generated through an Agent.

[0027] Thirdly, embodiments of this application provide an electronic device, which includes a memory and a processor. The memory and the processor communicate with each other via an internal connection path. The memory stores instructions, and the processor executes the instructions stored in the memory. When the processor executes the instructions stored in the memory, it causes the processor to perform the method in any of the embodiments described above.

[0028] Fourthly, embodiments of this application provide a computer-readable storage medium that stores a computer program, wherein when the computer program is run on a computer, the methods in any of the above-described embodiments are executed.

[0029] The advantages or beneficial effects of the above technical solution include at least the following: During the operation and maintenance of the target object, by obtaining the configuration information of the target object in the current operating environment and calling the target operation and maintenance tool based on the configuration information and operation and maintenance requirements, the operation and maintenance tool can be used to execute operations corresponding to the operation and maintenance requirements. This solves the problem of low operation and maintenance efficiency caused by the high dependence on personal experience, slow operation execution, and easy error in the manual operation and maintenance mode, and achieves a breakthrough improvement in operation and maintenance efficiency. By encapsulating operation and maintenance operations into standardized operation and maintenance tools and integrating a unified operation and maintenance tool library into the operation and maintenance tool platform, operation and maintenance operations that originally required long-term manual input of commands and verification of steps are replaced by calling operation and maintenance tools. Users no longer need to switch between multiple independent tools or manually build execution environments. They can safely and quickly call standard operation and maintenance tools through the operation and maintenance platform, reducing operation delays and human errors, and effectively improving the automation and intelligence of the operation and maintenance mode.

[0030] The above overview is for illustrative purposes only and is not intended to be limiting in any way. In addition to the illustrative aspects, embodiments, and features described above, further aspects, embodiments, and features of this application will become readily apparent from the accompanying drawings and the following detailed description. Attached Figure Description

[0031] In the accompanying drawings, unless otherwise specified, the same reference numerals throughout the various drawings denote the same or similar parts or elements. These drawings are not necessarily drawn to scale. It should be understood that these drawings depict only some embodiments disclosed in this application and should not be construed as limiting the scope of this application.

[0032] Figure 1a This is a framework design structure diagram of the operation and maintenance tool platform provided in Embodiment 1 of the present invention; Figure 1b A schematic diagram of the logical architecture of the operation and maintenance tool platform provided in Embodiment 1 of the present invention; Figure 1cThis is a schematic diagram of the technical architecture of an operation and maintenance tool platform provided in Embodiment 1 of the present invention; Figure 2a This is a flowchart of a product operation and maintenance method based on RPA, AI, and LLM to implement an agent, as provided in Embodiment 2 of the present invention. Figure 2b This is a schematic diagram of the configuration information interface of the operation and maintenance object provided in Embodiment 2 of the present invention; Figure 2c This is a screenshot of the parameter configuration interface of the operation and maintenance tool provided in Embodiment 2 of the present invention; Figure 2d This is a schematic diagram of the operation and maintenance tool interface provided in Embodiment 2 of the present invention; Figure 2e This is a screenshot of the task plan creation interface provided in Embodiment 2 of the present invention; Figure 2f This is a schematic diagram of the status of historical tasks provided in Embodiment 2 of the present invention; Figure 2g This is a screenshot of the operation and maintenance log interface provided in Embodiment 2 of the present invention; Figure 2h A flowchart illustrating the method for determining the target operation and maintenance tool provided in Embodiment 2 of the present invention; Figure 2i This is a schematic diagram of the inspection report for the inspection task provided in Embodiment 2 of the present invention; Figure 3 This is a structural block diagram of an operation and maintenance device for an agent-based server product provided in Embodiment 3 of the present invention; Figure 4 This is a structural block diagram of an electronic device provided in Embodiment 4 of the present invention. Detailed Implementation

[0033] The embodiments of this application are described in detail below. Examples of these embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and are only used to explain this application, and should not be construed as limiting this application.

[0034] In the description of this application, the term "multiple" means two or more.

[0035] In the description of this application, the implementation of the Digital Employee Platform (WEP) has gone through three stages. The first stage is the automation stage: for RPA stages with very low business complexity, software automation technology is used to automate rule-based, predefined procedural tasks. The second stage is the intelligence stage: extending the boundaries of RPA with the help of AI, such as processing unstructured documents and making judgments and decisions based on data. The third stage is the human-machine collaboration stage: utilizing the understanding, planning, and execution capabilities of large models to automate complex tasks end-to-end.

[0036] In the human-machine collaboration phase, the digital employee platform serves as a bridge connecting workers and systems, workers and data, and systems and data. It is capable of: operating complex systems, processing various types of data, and interacting and collaborating with employees. The digital employee platform helps industries build large-scale, model-enabled digital employees (i.e., intelligent agents), achieving automation, intelligence, and human-machine collaboration in business processes.

[0037] The digital employee platform can seamlessly integrate multiple capabilities such as Agentic Process Automation (APA), Agentic Document Processing (ADP), and Agentic Business Insights (ABI). It has five major functions: "business understanding", "process creation", "run anywhere", "centralized management and control" and "human-machine collaboration". It enables enterprises to achieve end-to-end intelligent automation of business processes, replace manual operations, further improve business efficiency, and accelerate digital transformation.

[0038] In the description of this application, the term "Operation and Maintenance Object" refers to intelligent automation products, including but not limited to: RPA server-side platforms, intelligent document processing platforms, intelligent agent process automation platforms, and intelligent agent document processing platforms. Each Operation and Maintenance Object can be integrated into a digital employee platform for unified maintenance and management, or it can be used as a standalone platform. The purpose of operation and maintenance is to ensure the stable and efficient operation of these products. The RPA server-side platform refers to the Robot Commander, used to assign tasks to RPA robots and monitor them in real time. Furthermore, it provides processes with data, credentials, and files provided by the process owner. The intelligent document processing platform is an enterprise-level AI platform centered on OCR (Optical Character Recognition), NLP (Natural Language Processing), and large language models. Through multimodal document parsing capabilities, it automatically identifies, extracts, classifies, compares, and reviews various structured / unstructured documents (such as contracts, invoices, and reports), transforming paper and electronic documents into actionable structured data assets, accelerating the process of "entering" enterprise data resources into tables. The intelligent agent document processing platform, based on large language models and visual language models and combined with intelligent agent technology, can handle complex document processing tasks involving multiple formats and languages ​​with a lighter and more flexible user interaction method. It forms a complete closed loop from document input to business decision-making and human-machine collaboration, propelling document processing from the tool era to the intelligent agent era. The intelligent agent process automation platform provides reliable process automation for intelligent agents. As a low-code platform, it helps enterprises quickly build, deploy, manage, and run automated processes, freeing up human resources and improving business efficiency.

[0039] In the description of this application, the term "operation and maintenance tool platform" can be used to perform operations such as monitoring, troubleshooting, and resource management on operation and maintenance objects. It is the workbench of operation and maintenance tools, and all operations on operation and maintenance objects are completed through the operation and maintenance tool platform.

[0040] In the description of this application, the term "operation and maintenance tools" refers to the collective term for functional software, program modules, applications, or integrated components developed in the operation and maintenance system to meet the operation and maintenance-related needs such as status monitoring, anomaly identification, fault diagnosis, problem handling, and performance optimization of the operation and maintenance objects.

[0041] In the description of this application, the term "operation and maintenance operation" refers to the specific implementation of operation and maintenance functions, which may include disk cleanup, system inspection, configuration modification, and one-click service restart.

[0042] In the description of this application, the term "running environment" refers to the physical hardware (such as CPU (Central Processing Unit), memory, and disk), operating system kernel resources, and middleware of the server deployed on the target maintenance object and the current maintenance tool platform.

[0043] In the description of this application, the term "basic environment" refers to the infrastructure environment provided by the customer, including: network, disk, CPU, GPU (Graphics Processing Unit), memory, firewall, server configuration, and operating system, etc.

[0044] In the description of this application, the term "execution action" is a minimal executable operation and maintenance configuration file, which is a component of operation and maintenance tools.

[0045] In the description of this application, the term "execution parameter" refers to a parameter that can be specified when an operation and maintenance tool is defined and executed. For example, the execution parameters that a screen recording cleanup tool can configure include "retention duration".

[0046] In the description of this application, the term "task plan" is a prerequisite configuration item for operation and maintenance tasks, used to define the start time, end time, running frequency and repeated execution time of operation and maintenance tasks, and is the core basis for realizing the automated and standardized scheduling of operation and maintenance tasks.

[0047] In the description of this application, the term "inspection task" refers to a continuous and standardized operation and maintenance verification process that is automatically initiated by the operation and maintenance tool platform or manually created by operation and maintenance personnel. It is a preventive step in operation and maintenance and a core means of discovering abnormal problems.

[0048] In the description of this application, the term "operation and maintenance task" refers to an operation and maintenance event generated after the user configures execution parameters and calls a specified operation and maintenance tool. It is a record generated each time an operation and maintenance tool, task plan, or inspection task is executed. The record includes the type of operation and maintenance tool used, the task status (e.g., execution successful, execution failed), and information such as the parameters and time at the time of execution.

[0049] In the description of this application, the term "task log" refers to the log information generated by the execution of operation and maintenance tasks, which is embedded in the "execution actions" during development to assist in execution analysis.

[0050] In the description of this application, the term "application service of the target operation and maintenance object" refers to the collective term for various applications, service processes, business modules, and functional interfaces that run on the target operation and maintenance object and provide business capabilities to the outside world.

[0051] In the description of this application, the term "middleware" refers to third-party components that a program needs to rely on, including but not limited to: MySQL (relational database management system), Redis (key-value storage system), RabbitMQ (open-source message broker software based on the Advanced Message Queuing Protocol), Minio (high-performance distributed object storage system based on open-source technology), Kubernetes (open-source container orchestration system for automating the deployment, scaling, and management of containerized applications), Docker (application container engine), Nginx (high-performance HTTP (Hypertext Transfer Protocol) and reverse proxy web (global wide area network) server), Etcd (distributed key-value storage system), Harbor (core component for handling API requests), and Helm (Kubernetes package management tool for simplifying application deployment), etc.

[0052] In the description of this application, the term "Action entity" refers to the core data layer entity created in the data model architecture of operation and maintenance tools to realize the concrete carrier of operation and maintenance tools. Its essence is the data layer mapping carrier of "tools" in the product form, which is used to store the core related information of operation and maintenance tools (such as the action type identifier) ​​and is the basic data unit for tool creation, management and execution.

[0053] In the description of this application, the term "type field" refers to the pre-defined type identifier field in the Action entity, which is the core bridge between binding tools and execution logic. Its field value is used to uniquely identify the type of execution action corresponding to the operation and maintenance tool. By establishing an association with the built-in execution action class name through this field, it is ensured that the tool can accurately match the corresponding functional implementation logic when it is called.

[0054] In the description of this application, the term "class name of the action to be executed" refers to the name of the code class that has been developed in advance in the system and has specific tool function implementation logic. It is the underlying implementation carrier of the actual function of the tool. By associating with the type field, the operation and maintenance tool has executable functional logic.

[0055] In the description of this application, the term "metadata interface" refers to a standardized query interface deployed in the operation and maintenance tool platform. Its core function is to provide query, update and synchronization services for the type field in the Action entity. It is a data interaction bridge connecting the data layer (Action entity) and the front end, and supports the front end to obtain tool type information and synchronize tool type update status.

[0056] In the description of this application, the term "monitoring platform" is a system that has a communication connection with the target object being maintained and is used to monitor the operating status of the target object being maintained.

[0057] In the description of this application, the term "NLP" refers to an important research direction in the field of artificial intelligence, integrating knowledge from multiple disciplines such as linguistics, computer science, machine learning, mathematics, and cognitive psychology. It is an interdisciplinary field combining computer science, artificial intelligence, and linguistics, encompassing two main aspects: natural language understanding and natural language generation. Its research content includes multiple levels such as characters, words, phrases, sentences, paragraphs, and texts, serving as a bridge between machine language and human language. This application utilizes NLP services to analyze the monitoring platform's detection reports on the operational status of the target maintenance object.

[0058] In the description of this application, the term "cue word" is a natural language instruction used to guide an agent to perform a specific task, transforming general AI into a powerful tool for solving specific problems by clearly defining the agent's role, capabilities, and behavioral boundaries.

[0059] These and other aspects of the embodiments of this application will become clear from the following description and accompanying drawings. In these descriptions and drawings, some specific implementations of the embodiments of this application are specifically disclosed to illustrate some ways of carrying out the principles of the embodiments of this application; however, it should be understood that the scope of the embodiments of this application is not limited thereto. Rather, the embodiments of this application include all variations, modifications, and equivalents falling within the spirit and scope of the appended claims.

[0060] The following is a detailed description of an operation and maintenance method, apparatus, device, and storage medium for a server-side product based on RPA, AI, and LLM to implement an agent, provided in conjunction with the accompanying drawings and embodiments of this application.

[0061] Example 1 The product operation and maintenance method provided in this embodiment is executed through an operation and maintenance tool platform. This operation and maintenance tool platform and the target object being maintained are deployed on the same server and communicate with each other. The operation and maintenance tool platform includes multiple functional modules tailored to user needs. Figure 1a The framework design structure diagram of the operation and maintenance tool platform provided in Embodiment 1 of the present invention is as follows: Figure 1a As shown, this operation and maintenance tool platform includes the ability to discover the deployment environment of the target operation and maintenance object, including the environment configuration information of the host, middleware, and application services. The platform also includes functions for adding tools, executing tools, configuring execution plans, displaying task lists, and querying task logs. The operation and maintenance tool platform of this invention will be described below from both logical and technical architecture perspectives.

[0062] Figure 1b This is a schematic diagram of the logical architecture of the operation and maintenance tool platform provided in Embodiment 1 of the present invention. Figure 1b As shown, from a logical perspective, the operation and maintenance tool platform provided in this embodiment includes a toolset module, a tool management module, and a user operation module. The toolset module includes functional units corresponding to multiple operation and maintenance tools, such as screen recording cleanup tools, task queue cleanup tools, queue cleanup tools, service log cleanup tools, and service restart tools. The tool management module includes tool configuration units, tool combination units, tool execution units, tool task recording units, and tool log recording units. The user operation module includes unit user management, permission management units, authorization management units, and operation log units. The various functional modules and units communicate and transmit data through pre-defined APIs (Application Programming Interfaces). In practical applications, more functional modules can be set up according to operation and maintenance needs; this embodiment does not specifically limit the type and number of functional modules.

[0063] The tool management module provides a query for the built-in execution action list (metadata). The front end can discover all built-in execution action types and their input / output parameter types, and use this information for type enumeration and parameter editing interface display. It also provides the following types of interface access: Utility class: Provides tool-related interfaces, supporting single and batch queries, and standard interfaces for creating, updating, and deleting; Task category: Interfaces related to tool execution tasks, supporting single and batch queries (incomplete, completed), and creating (tool execution) interfaces; Task Log Class: Logs generated by the tool when executing tasks, which can be queried by the task identifier.

[0064] Specifically, the data module of the tool management module can be divided into the following three layers: A. Data Layer (Action): This layer corresponds to the operation and maintenance tools in the operation and maintenance tool platform product. In code implementation, it can be achieved in the following way: Create an Action entity for the operation and maintenance tool, which serves as the carrier of the operation and maintenance tool; Configure the type field of the Action entity to establish an association between the type field and the class name of the execution action of the operation and maintenance tool, so as to bind the execution action type corresponding to the operation and maintenance tool; The metadata interface for deploying and executing actions enables the metadata interface to query the type field corresponding to the Action entity. The metadata interface is used to provide the front-end application layer with services for obtaining, enumerating, and configuring tool types.

[0065] In this embodiment, by adopting the aforementioned method for generating operation and maintenance tools, standardized binding and unified management of tools and underlying execution actions in the product form are achieved. Using the Action entity as the unified carrier of tools and the type field as the unique link between tools and built-in execution action class names, the technical problems of chaotic logical associations and scattered mapping relationships between tools and execution actions are effectively avoided, ensuring the accuracy of matching operation and maintenance tools with execution actions. Furthermore, a standardized tool type enumeration capability is provided to the front end through the metadata interface of execution actions. The front end can conveniently obtain all supported tool types through a unified interface, realizing unified display and invocation of tool types on the front end, improving the convenience and efficiency of human-computer interaction. In addition, the tool creation mode provided in this embodiment also has good versatility and scalability, facilitating the addition and deletion of tools by operation and maintenance personnel.

[0066] B. Task Recording Layer (ActionRecord) The task recording layer includes an in-process task recording layer and a historical task recording layer. The in-process task recording layer corresponds to the execution tasks in the operations and maintenance tool platform product. Each time the tool is triggered, a corresponding record is generated. When the task is completed (whether successfully or unsuccessfully), relevant task information (such as task start time, task end time, and task running status) is moved to the historical task recording layer, which records information related to completed tasks.

[0067] C. Task Storage Layer Log records generated from each task execution will be stored in the task storage layer.

[0068] In this embodiment, by designing the tool management module according to the above three-layer architecture, the separation of responsibilities and logical decoupling of each link of task management are realized. This facilitates independent optimization and iteration of each functional unit, reduces the development and maintenance costs of the module, and enables standardized recording and unified storage of task data, which helps to improve the overall efficiency of task management on the operation and maintenance platform.

[0069] In this embodiment, the generation of various operation and maintenance tools can be achieved through an Agent. When generating operation and maintenance tools using an Agent, prompts need to be input into the Agent, including: 1. Basic instructions, telling the agent what kind of operation and maintenance tool to generate; 2. Specific tool examples, including environment information, callable tool interfaces, etc.; 3. Functional requirements and execution logic, including the input and output parameters corresponding to tools with different functions, as well as the processing flow of operation and maintenance operations, etc. By training the Agent with the above prompts, the trained agent can automatically complete the creation of operation and maintenance tools, the association of execution actions, and the configuration of metadata according to preset rules, greatly reducing manual operation steps and effectively improving the creation efficiency of operation and maintenance tools.

[0070] Figure 1c This is a schematic diagram of the technical architecture of an operation and maintenance tool platform provided in Embodiment 1 of the present invention, as shown below. Figure 1c As shown, the operation and maintenance tool platform can be divided into four layers in terms of technical architecture: front-end application layer 1, back-end service layer 2, back-end execution layer 3, and storage layer 4. These layers communicate and transfer data through pre-defined APIs (Application Programming Interfaces). Front-end application layer 1 is configured with a user interface to receive creation or execution requests for various operation and maintenance tools, as well as the corresponding execution parameter information for each tool. The user interface includes components for users to add tools and configure parameters. Users can access the parameter configuration entry point by triggering these components.

[0071] Backend service layer 2 is used to send execution instructions to backend execution layer 3 based on the creation or running request of the operation and maintenance tool. The instructions include execution parameter information and environment configuration information.

[0072] The backend execution layer 3 is configured with an execution action module, which is used to execute corresponding operation and maintenance operations according to execution instructions, and send the operation and maintenance results to the backend service layer 2 and the operation and maintenance logs to the storage layer 4. The execution action module is an abstraction of built-in execution actions, mainly used to implement the action execution process. The execution action module provides functions for creating actions, executing actions, and issuing completion notifications. To support dynamic expansion, it also supports the definition and retrieval of metadata and can automatically enumerate the built-in supported action types.

[0073] Storage layer 4 is used to store the configuration information of the target operation and maintenance object in the current operating environment, as well as the operation and maintenance logs and user operation logs of various operation and maintenance tools. For example, SQLite (a lightweight database) can be used for data storage.

[0074] In this embodiment, the creation of the operation and maintenance tool platform enables diversified operations on operation and maintenance tools, including adding, configuring, and running them. This covers the three stages of the operation and maintenance process: problem discovery or prevention, problem analysis, and problem resolution. Particularly regarding the problem resolution stage, by analyzing historical operation and maintenance issues encountered by the target object during operation, operation and maintenance tools can be configured to solve different problems. In other words, these tools can quickly and effectively resolve various issues encountered by the target object during operation, thereby improving operation and maintenance efficiency.

[0075] After the operation and maintenance tool platform is built, it can be applied to the operation and maintenance process of the target operation and maintenance object. Please refer to Example 2 below.

[0076] Example 2 Figure 2a This is a flowchart illustrating a product operation and maintenance method based on RPA, AI, and LLM for implementing an agent, as provided in Embodiment 2 of the present invention. This method can be executed by a server-side product operation and maintenance device based on RPA, AI, and LLM for implementing an agent. The server-side product can be various types of intelligent automation platforms, such as an RPA server-side platform, an intelligent document processing platform with AI functionality, an intelligent agent document processing platform, or an intelligent agent process automation platform, etc. These server-side products are the operation and maintenance objects mentioned in this embodiment. The operation and maintenance tool platform provided in this embodiment is deployed on the same server as the target running object. Figure 2a As shown, the method provided in this embodiment includes: S210. Obtain the configuration information of the target operation and maintenance object in the current operating environment.

[0077] The configuration information of the target maintenance object in its current operating environment includes host configuration information, middleware configuration information, and service configuration information. Host configuration information includes host type, hostname, IP (Internet Protocol) address, SSH (Secure Shell) port, SSH username, SSH password, whether SSH is used as ROOT (root user), and whether it is a master node. Middleware configuration information includes middleware type, connection address, username, and deployment type. Service configuration information includes the service name provided by the target maintenance object (e.g., OCR service, NLP service provided by the intelligent document processing platform), the product, namespace, and version information.

[0078] In this embodiment, the operation and maintenance tool platform has the function of obtaining the configuration information of the operation and maintenance objects in the current operating environment. For example, after the operation and maintenance tool platform is successfully deployed on the server, it can automatically perform the deployment information acquisition operation. Alternatively, operation and maintenance personnel can generate a configuration information acquisition request by clicking the "Configuration Discovery" button in the front-end user interface of the operation and maintenance tool platform. Based on this request, the operation and maintenance tool platform can display all the operation and maintenance objects deployed in the current environment, as well as related database and storage connection information, on the user interface. Operation and maintenance personnel can select the target operation and maintenance object from multiple operation and maintenance objects. The operation and maintenance tool platform will display the host configuration information, middleware configuration information, and product service configuration information corresponding to the target operation and maintenance object on the user interface. Figure 2bAs shown, if operations and maintenance personnel find that the currently deployed maintenance objects in the operating environment are inconsistent with the actual deployed and installed products, they can add a new product (i.e., the target maintenance object) through the "Add Product" button and fill in the relevant configuration information, such as database connection information, access path, access user, access port, and access password. The operations and maintenance tool platform will display the host configuration information, middleware configuration information, and product service configuration information corresponding to the newly added maintenance object on the user interface. If operations and maintenance personnel find any of the above configuration information to be incorrect, they can click the "Configuration Discovery" button again to retrieve the configuration information or manually correct the configuration information.

[0079] In this embodiment, obtaining the configuration information of the target maintenance object in the current operating environment is the core prerequisite for the smooth operation of the entire maintenance work. By accurately discovering the deployment and configuration information of the target maintenance object, a solid and reliable input condition is provided for the efficient operation of subsequent maintenance tools, ensuring that every step of the maintenance work is accurate and error-free.

[0080] S220. Based on the configuration information and maintenance requirements of the target maintenance object in the current operating environment, the target maintenance tool is invoked to perform maintenance operations corresponding to the maintenance requirements through the target maintenance tool.

[0081] The operational and maintenance requirements can be determined based on the actual application scenario. For example, these could include disk cleanup, system inspection, configuration modification, or one-click service restart. This embodiment does not impose specific limitations on these requirements. In this embodiment, there are various types of operational and maintenance tools, which can be configured according to the historical problems encountered by the target operational and maintenance object to meet different operational and maintenance needs. These tools may include: disk cleanup tools, product configuration modification tools, product service recovery tools, environment anomaly recovery tools, data recovery and backup tools, etc.

[0082] In this embodiment, the target operation and maintenance tool is invoked based on the configuration information and operation and maintenance requirements of the target operation and maintenance object in the current operating environment. This can be achieved through the following optional implementation methods: Implementation Method 1: Operational requirements can be input into the operations and maintenance (O&M) tool platform by sending commands. Upon receiving the command, the O&M tool platform can determine the target O&M tool corresponding to the command, and then invoke that target O&M tool to execute the corresponding O&M operation based on the configuration information. For example, if the O&M tool platform receives a disk cleanup command, the target O&M tool invoked will be the disk cleanup tool.

[0083] Implementation Method 2: Operation and maintenance personnel can add target operation and maintenance tools according to actual operation and maintenance needs, and can trigger the operation and maintenance tools to run, so as to perform corresponding operation and maintenance operations through the operation and maintenance tools.

[0084] Optionally, after adding an operation and maintenance tool, the operation and maintenance personnel can manually trigger the execution of the target operation and maintenance tool.

[0085] In this embodiment, the user interface of the operation and maintenance tool platform is configured with a tool adding component. Users can initiate a tool adding request by clicking the "Tool Add" button. After receiving the tool adding request, the operation and maintenance tool platform will display the parameter configuration interface of the operation and maintenance tool. Figure 2c This is a screenshot of the parameter configuration interface of the operation and maintenance tool provided in Embodiment 2 of the present invention, such as... Figure 2c As shown, the tool parameters to be configured include tool name, tool type, execution action, and execution parameters. Operations personnel can configure these parameters according to their actual operational needs. After configuration, clicking the "Save" button completes the addition of the target tool. Operations personnel can disable or enable added operations tools. After enabling a specific operations tool, it can be viewed and used on the operations tool page of the operations tool platform. Figure 2d This is a schematic diagram of the operation and maintenance tool interface provided in Embodiment 2 of the present invention. Figure 2d As shown, for each operation and maintenance tool in the "Started" state, the user can select the target operation and maintenance tool according to the actual operation and maintenance needs. For example, if the current operation and maintenance need is screen recording to disk, the user can click the "Run Tool" button corresponding to the screen recording cleanup tool. If the current operation and maintenance need is disk cleanup, the user can click the "Run Tool" button corresponding to the disk cleanup tool. If the current operation and maintenance need is service restart, the user can click the "Run Tool" button corresponding to the service restart tool. The user's operation of clicking the "Run Tool" button sends a run request for the target operation and maintenance tool to the operation and maintenance tool platform. In this embodiment, if the operation and maintenance tool platform receives the run request for the target operation and maintenance tool, it will call the interface of the target operation and maintenance tool. The target operation and maintenance tool will perform the corresponding operation and maintenance operation based on the configuration information of the target operation and maintenance object in the current running environment and according to its tool parameter information. Furthermore, in order to ensure that the operation and maintenance operation performed by the operation and maintenance tool meets the user's needs, when the operation and maintenance tool platform receives the run request for the target operation and maintenance tool, it can display the execution parameters corresponding to the target operation and maintenance tool on the user interface for operation and maintenance personnel to confirm or modify. Once the user has confirmed that everything is correct or has completed the modifications, clicking the "Confirm" button will trigger the operation and maintenance tool to begin executing the task.

[0086] Optionally, the invocation of the target operation and maintenance tools can also be automatically triggered according to the created execution plan.

[0087] In this embodiment, operations and maintenance personnel can send an execution plan creation request to the operations and maintenance tool platform through the task plan "creation" component provided in the user interface. Upon receiving the creation request, the operations and maintenance tool platform will display the task plan parameter settings interface, such as... Figure 2eAs shown, this parameter setting interface is used to configure the target operation and maintenance tool and task triggering rules corresponding to the task plan. The task triggering rules include task start time, task end time, task execution frequency, and task repetition time. After configuration, the operation and maintenance tool platform will execute the corresponding task according to the execution parameters of the target operation and maintenance tool and the configured task triggering rules. For example, it can restart the service of the target operation and maintenance object at a certain time period through the "Restart Service Tool".

[0088] Furthermore, after the execution plan is created, its running status can be viewed on the plan page. The execution plan status is divided into two types: start / stop and active. The start / stop status includes two states: enabled and disabled. The enabled state indicates that the plan is running according to the set time and rules. The plan enters the enabled state after the operations personnel successfully create or rerun the plan, or manually enable the plan. The disabled state indicates that the plan has been disabled. The plan enters the disabled state when the user manually disables the plan or when the plan reaches its specified deadline. The active status includes three types: pending activation, in effect, and completed. The pending activation state indicates that the current time has not yet reached the plan's start time; the in effect state indicates that the current time is between the plan's start and end times; and the completed state indicates that the current time has exceeded the plan's end time.

[0089] It should be noted that regardless of whether the target operation and maintenance tool is invoked manually or automatically, the operation and maintenance tool platform will generate an execution task corresponding to that tool after it is invoked. The execution task status includes the following: successful, failed, running, canceled, and timed out. Furthermore, the operation and maintenance tool platform has a task information query function, including querying running tasks and historical tasks. In the user interface, operation and maintenance personnel can view the corresponding operation and maintenance tasks by fields such as task number, operation and maintenance tool name, or task creation time. Figure 2f This is a schematic diagram of the status of historical tasks provided in Embodiment 2 of the present invention, such as... Figure 2f As shown, by entering the task creation time, users can retrieve relevant information for all historical tasks within that time period, including task number, tool name, tool category, creation time, task status, and operations. Furthermore, users can click the "Re-execute" button to repeat the execution of the triggered historical task as needed. In this embodiment, by setting up a task viewing function in the operations and maintenance tool platform, previously scattered and isolated operations and maintenance work becomes standardized and visualized, enabling operations and maintenance personnel to instantly understand the operational status of each task and improving operational efficiency.

[0090] Furthermore, for each operation and maintenance task, when the operation and maintenance tool platform receives a viewing request for the task, it can display the task details corresponding to the viewing request. Operation and maintenance tasks include any of the following types: ongoing operation and maintenance tasks, completed historical operation and maintenance tasks, inspection tasks, and task plans. The task details include basic task information (e.g., tool name, tool category, creator, and creation time), running parameters (e.g., timeout duration, whether a forced restart is required), and running information (e.g., runtime, start time, and end time). This task detail transforms the originally scattered and implicit operational data into centralized and explicit structured records. In this embodiment, by providing an integrated details view for each operation and maintenance task, the transparency, traceability, and reusability of operation and maintenance operations are significantly improved. This allows operation and maintenance personnel to clearly, completely, and comprehensively understand the specific details of task execution, enabling rapid and accurate problem localization when anomalies occur, and providing a reliable data foundation for continuous optimization of the operation and maintenance process.

[0091] Furthermore, for the operational tasks executed by each operational tool, the operational tool platform can generate corresponding operational logs. Figure 2g This is a screenshot of the operation and maintenance log interface provided in Embodiment 2 of the present invention. Figure 2g As shown, the task log records detailed cleanup task data. This operations log can serve as a unified, structured, and observable data source, transforming the previously scattered and unstructured system operation data into high-value operations assets. It provides an accurate data foundation for analyzing abnormal operations and improves operations efficiency.

[0092] Implementation Method 3: Detect the running status of the target operation and maintenance object based on the configuration information, determine the corresponding target operation and maintenance tool according to the abnormal detection items in the detection results, and call the target operation and maintenance tool.

[0093] In this embodiment, detecting the running status of the target operation and maintenance object involves detecting the running status of each item to be detected, including the system-level basic environment, the application services of the target operation and maintenance object, and the middleware status. Based on the configuration information of the target operation and maintenance object in the current running environment, the running status of each item to be detected can be obtained. Specifically, each item to be detected includes the system-level basic environment, the application services of the target operation and maintenance object, and the middleware status.

[0094] The operational status of the system-level infrastructure includes CPU utilization, load, memory utilization, disk read speed, disk write speed, firewall status, automatic data disk loading, maximum number of file system handles, and disk capacity utilization. Middleware status includes middleware connection status. The operational status of the target operation and maintenance object's application services refers to the operational status of various applications and service processes running on the target operation and maintenance object that provide external business capabilities.

[0095] Optionally, the operation and maintenance tool platform can detect the running status of the target operation and maintenance object based on the configuration information in the following ways: By obtaining the monitoring platform's detection report on the target operation and maintenance object, the platform obtains the detection results of the target operation and maintenance object's operational status. These results record the actual operational metrics of each item to be detected and the prompts for abnormal detection items. The monitoring platform can compare the actual operational metrics of each item to be detected with the corresponding standard operational metric values ​​and identify those that do not meet the standard values ​​as abnormal detection items. Furthermore, the monitoring platform can analyze each abnormal detection item by calling NLP services to obtain abnormal prompts for the target operation and maintenance object. The operation and maintenance tool platform can determine the corresponding target operation and maintenance tool based on the abnormal detection items in the identification results and invoke it. For example, if the abnormal prompt indicates excessive memory usage and the need for memory cleanup, the operation and maintenance tool platform can determine the target operation and maintenance tool as a memory cleanup tool and invoke it to clean up cached data in memory or files in the junk file. Before confirming the cleanup, a cleanup message can be sent to the user for confirmation.

[0096] Optionally, the operation and maintenance tool platform can also detect the running status of the target operation and maintenance object based on the configuration information in the following ways: The operation and maintenance tool platform can obtain the running status of each item to be detected of the target operation and maintenance object based on the configuration information of the target operation and maintenance object in the current running environment, and detect the running status of each item to be detected based on the created inspection task. Then, it can determine the corresponding target operation and maintenance tool based on the abnormal detection items in the detection results and call the target operation and maintenance tool.

[0097] The inspection task can be manually triggered by maintenance personnel after creation, or it can be triggered periodically by creating a task execution plan. This embodiment does not specifically limit this. Specifically, the process of creating an inspection task is as follows: When the operations and maintenance (O&M) tool platform receives a request to create an inspection task, it displays the inspection task's detection item configuration interface. This interface is used to configure the inspection parameters for the inspection task, including the start time, end time, and frequency. The request to create an inspection task can be triggered when the O&M personnel select "Product Inspection" as the action to be executed by the created O&M tool. After the inspection task is configured, the O&M tool platform will execute the inspection task according to the detection parameters. In this embodiment, by providing a standardized inspection task creation function on the O&M tool platform, the system health check process, which originally relied on manual experience and was executed discretely, is transformed into a standardized O&M operation that is definable, schedulable, and traceable. This enables proactive and preventative detection of the system environment, middleware status, and application service status, thereby shifting the timing of fault discovery from reactive post-event response to pre-event warning or early-stage fault detection, significantly improving the normal operation and stability of the target O&M object.

[0098] Similar to the execution of tasks by the operations and maintenance tools, when an inspection task begins, the operations and maintenance tool platform will generate a view list for the inspection task. This list records the inspection task number, inspection date, inspected products, and inspection status. Through this view list, operations and maintenance personnel can clearly, completely, and comprehensively understand the basic information of the inspection task.

[0099] In this embodiment, the inspection task is performed to detect the operational status of each item to be inspected within the target maintenance object, thereby identifying abnormal items. For example, it determines whether the actual CPU utilization is abnormal, whether the disk capacity is abnormal, whether the middleware connection is abnormal, and whether the application service process is abnormal. Specifically, standard operational indicators for the operational status of each item to be inspected can be preset. During the inspection process, the operational status of each item can be compared with the corresponding standard operational indicators, and abnormal items that do not meet the corresponding standard operational indicators are marked. For example, the actual CPU utilization is compared with a preset utilization threshold; if the actual CPU utilization exceeds the corresponding utilization threshold, the CPU utilization is determined to be abnormal. Similarly, the remaining disk capacity is compared with a corresponding capacity threshold; if the remaining disk capacity is less than the corresponding capacity threshold, the disk capacity is determined to be abnormal. In this embodiment, various operational indicators can be compared simultaneously.

[0100] In this embodiment, determining the corresponding target maintenance tool based on the abnormal detection items in the inspection task's detection results can be achieved through the following steps S221~S224. For details, please refer to [link to relevant documentation]. Figure 2h .

[0101] S221. Obtain the running status of each item to be detected based on the configuration information, and detect the running status based on the created inspection task.

[0102] S222. When a request to view the inspection report of any inspection task is received, the inspection report of that inspection task is displayed on the current interface.

[0103] Specifically, the operation and maintenance tool platform will record the actual operating indicators detected for each item to be tested in each inspection task, and mark the status of abnormal detection items. Figure 2i This is a schematic diagram of the inspection report for the inspection task provided in Embodiment 2 of the present invention, as shown below. Figure 2i As shown, each inspection task has a corresponding inspection report, which records the actual operational indicators of each inspection item. Through this report, operations and maintenance personnel can perform real-time, quantitative assessments of the system's health status, quickly identify abnormal operational items and potential risk points, and elevate problem localization from data filtering at the raw log level to anomaly localization at the report level, greatly improving the efficiency of anomaly detection. For example, Figure 2i As shown, maintenance personnel can directly learn that CPU utilization is abnormal by viewing the test report, which helps to locate the problem and conduct further investigation.

[0104] S223. When a request to view the runtime log of an anomaly detection item is received, the runtime log of the anomaly detection item is displayed.

[0105] Furthermore, for abnormal detection items in the detection report, the operations and maintenance tool platform displays the operation logs of the abnormal detection items upon receiving a request to view their runtime logs. For example, by identifying... Figure 2i The anomaly detection item markers shown identify the anomaly detection item that has occurred, allowing for analysis of its runtime logs to pinpoint the specific operational stage where the anomaly occurred. In this embodiment, the operation and maintenance tool platform can automatically identify anomaly detection items by recognizing keywords in the detection report, such as "anomaly," "error," and "fault." After identifying the anomaly detection item, it can automatically download the corresponding runtime log and display it to the user. Alternatively, after identifying anomaly detection items by viewing the inspection task's detection report, the user can trigger a log download request for that anomaly detection item by clicking the "Log Download" button corresponding to that anomaly detection item on the user interface.

[0106] S224. Determine the target operation and maintenance tool that matches the anomaly detection item based on the operation log.

[0107] In this embodiment, the operation and maintenance tool platform can identify the target operation and maintenance tool corresponding to the specific anomaly detection item by analyzing its runtime logs, and then call and run that target operation and maintenance tool. For example, if the anomaly detection item is a middleware connection anomaly, and analysis of the middleware runtime logs reveals a connection problem with a specific middleware component, then the target operation and maintenance tool can be identified as a middleware configuration recovery tool, and this tool can be called and run. Alternatively, if the anomaly detection item is a product service anomaly, and analysis of the product service runtime logs reveals a process interruption, then the target operation and maintenance tool can be identified as a service recovery tool, which can be called to restore the service of the target operation and maintenance object.

[0108] In this embodiment, by setting up a log viewing function for anomaly detection items on the operation and maintenance tool platform, operation and maintenance personnel no longer need to manually search and piece together log fragments using complex command-line tools. They can directly locate the complete and fully related operation logs in the operation and maintenance platform by using the anomaly events in the detection report as an index. This changes the access mode of operation logs, solves the problem of operation logs being difficult to find and utilize in related technologies, and transforms operation logs from hidden and passive technical data into active and directly viewable data resources, greatly reducing the path and time for anomaly investigation.

[0109] Furthermore, the operations and maintenance platform records user operation information, including user login and maintenance operations, which can be viewed, searched, and exported in log management. The log format includes module name, operator, operation content, IP address, and operation time. Users can export the required operations and maintenance logs from the operations and maintenance tool platform by clicking the export button. In this embodiment, a user operation log viewing function is set up in the operations and maintenance tool platform, transforming each user interaction into a structured record with precise timestamps, operator identity, and complete operation details, solving the problems of invisible and untraceable operations and maintenance operations in related technologies.

[0110] Furthermore, the operation and maintenance tool platform provided in this embodiment supports automatic cleanup of completed historical tasks, completed plans, task logs, and operation logs. If the storage time of any of the above data records exceeds a preset time threshold, the data record will be automatically deleted.

[0111] It should be noted that the maintenance personnel mentioned in this embodiment of the invention are specific end users with access permissions to the maintenance tool platform. The maintenance tool platform allows for the whitelisting of specific end users' IP addresses to ensure the security of end-user usage.

[0112] The technical solution provided in this embodiment, during the operation and maintenance of the target maintenance object, obtains the configuration information of the target maintenance object in the current operating environment, and calls the target maintenance tool based on the configuration information and maintenance requirements. The maintenance tool can then execute operations corresponding to the maintenance requirements, solving the problems of low maintenance efficiency caused by high reliance on personal experience, slow operation execution, and susceptibility to errors in manual maintenance mode. This achieves a breakthrough improvement in maintenance efficiency. By encapsulating maintenance operations into standardized maintenance tools and integrating a unified maintenance tool library into the maintenance tool platform, operations that originally required lengthy manual command input and step verification are replaced by calling maintenance tools. Users no longer need to switch between multiple independent tools or manually build execution environments; they can safely and quickly call standard maintenance tools through the maintenance platform interface, reducing operation delays and human errors, and effectively improving the automation and intelligence of the maintenance mode.

[0113] Example 3 Figure 3 This is a structural block diagram of an operation and maintenance device for an agent-based server product provided in Embodiment 3 of the present invention, as shown in the figure. Figure 3 As shown, the device includes: a configuration information acquisition module 310 and a target operation and maintenance tool invocation module 320, wherein, The configuration information acquisition module 310 is used to acquire the configuration information of the target operation and maintenance object in the current operating environment. The target operation and maintenance object and the current operation and maintenance tool platform are deployed on the same server. The configuration information includes host configuration information, middleware configuration information and service configuration information. The target operation and maintenance object includes the RPA server platform, intelligent document processing platform, intelligent agent document processing platform and intelligent agent process automation platform. The target operation and maintenance tool invocation module 320 is used to invoke the target operation and maintenance tool based on configuration information and operation and maintenance requirements, so as to execute the operation and maintenance operations corresponding to the operation and maintenance requirements through the target operation and maintenance tool.

[0114] In one implementation, the target operation and maintenance tool invocation module 320 includes: The first invocation unit is used to respond to the request to add an operation and maintenance tool, display the parameter configuration interface of the operation and maintenance tool, and after completing the configuration of the target operation and maintenance tool, if a run request for the target operation and maintenance tool is received, invoking the corresponding target operation and maintenance tool based on the configuration information and the configured operation and maintenance tool parameter information. The operation and maintenance tool parameters include the tool name, tool type, execution action, and execution parameters; or, The second invocation unit is used to detect the running status of the target operation and maintenance object based on the configuration information, determine the corresponding target operation and maintenance tool according to the abnormal detection items in the detection results, and invoke the target operation and maintenance tool.

[0115] In one implementation, the second calling unit includes: An external detection report identification and acquisition subunit is used to acquire the detection report of the target maintenance object from the monitoring platform, and determine the operating status of the target maintenance object based on the detection results in the inspection report. The detection results include abnormal prompts and corresponding handling methods. The handling methods are obtained by the monitoring platform through natural language processing (NLP) services analyzing the actual operating indicators of each item to be detected; or... The inspection task execution subunit is used to obtain the running status of each item to be inspected based on the configuration information, and to inspect the running status based on the created inspection task. Each item to be inspected includes the system layer basic environment, the application services of the target maintenance object, and the middleware status.

[0116] In one implementation, the inspection task execution subunit is specifically used for: In response to the request to create an inspection task, the inspection task's detection parameter configuration interface is displayed. The detection parameter configuration interface is used to configure the detection parameters of the inspection task, including the detection start time, detection end time, and detection frequency. After the inspection task is configured, the operating status of each inspection item is compared with the corresponding standard operating indicators, and abnormal inspection items that do not meet the corresponding standard operating indicators are marked.

[0117] In one implementation, the second calling unit includes: The inspection report viewing sub-unit is used to display the inspection report of any inspection task on the current interface when a viewing request for the inspection report of any inspection task is received. The runtime log display subunit is used to display the runtime log of the exception detection item when a request to view the runtime log of the exception detection item is received. The target operation and maintenance tool determination subunit is used to determine the target operation and maintenance tool corresponding to the anomaly detection item based on the operation log.

[0118] In one embodiment, the apparatus provided in this application further includes: The operation and maintenance task generation module is used to generate operation and maintenance tasks corresponding to the target operation and maintenance tool after the target operation and maintenance tool is invoked.

[0119] In one embodiment, the apparatus provided in this application further includes: The task details viewing module is used to display the task details corresponding to any type of operation and maintenance task when a viewing request is received. The types of operation and maintenance tasks include: operation and maintenance tasks in progress, completed historical operation and maintenance tasks, inspection tasks, and task plans.

[0120] In one embodiment, the apparatus provided in this application further includes: The task plan generation module is used to respond to the task plan creation request after the operation and maintenance tools are added and display the task plan execution strategy setting interface. The execution strategy setting interface is used to configure the target operation and maintenance tools and task triggering rules corresponding to the task plan. The task triggering rules include task start time, task end time, task running frequency and task repeat execution time.

[0121] The task scheduling and execution module is used to execute corresponding tasks according to the execution parameters of the target operation and maintenance tool and the configured task triggering rules after the execution strategy has been configured.

[0122] In one implementation, the functional models corresponding to each operation and maintenance tool are built through the following modules: The data layer creation module is used to create data layer Action entities for the operation and maintenance tools, which serve as the carrier of the operation and maintenance tools. The action association module is used to configure the type field of the Action entity, so as to establish an association relationship between the type field and the class name of the action to be executed by the operation and maintenance tool, and to bind the action type corresponding to the operation and maintenance tool. The interface deployment module is used to deploy the metadata interface for executing actions, enabling the metadata interface to query the type field corresponding to the Action entity. The metadata interface is used to provide the front-end application layer with services for obtaining, enumerating, and configuring tool types.

[0123] In one implementation, the operation and maintenance tools include: disk cleanup tools, product configuration modification tools, product service recovery tools, environment anomaly recovery tools, and data recovery and backup tools, wherein each operation and maintenance tool is generated through an Agent.

[0124] The functions of each module in each device in the embodiments of this application can be found in the corresponding descriptions in the above methods, and will not be repeated here.

[0125] Example 4 Figure 4 This diagram illustrates a structural block diagram of an electronic device according to Embodiment 4 of this application. Figure 4 As shown, the electronic device includes a memory 910 and a processor 920. The memory 910 stores a computer program that can run on the processor 920. When the processor 920 executes the computer program, it implements the operation and maintenance method of the agent-based server product based on RPA, AI, and LLM in the above embodiments. The number of memories 910 and processors 920 can be one or more.

[0126] The electronic device also includes: The communication interface 930 is used to communicate with external devices and exchange and transmit data.

[0127] If the memory 910, processor 920, and communication interface 930 are implemented independently, they can be interconnected via a bus to communicate with each other. This bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. This bus can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 4 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0128] Optionally, in a specific implementation, if the memory 910, processor 920, and communication interface 930 are integrated on a single chip, then the memory 910, processor 920, and communication interface 930 can communicate with each other through an internal interface.

[0129] This application provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the method provided in this application.

[0130] This application also provides a chip, which includes a processor for calling and executing instructions stored in a memory, causing a communication device equipped with the chip to execute the operation and maintenance method of the server-side product based on RPA, AI, and LLM to implement the agent provided in this application.

[0131] This application also provides a chip, including: an input interface, an output interface, a processor, and a memory. The input interface, output interface, processor, and memory are connected through an internal connection path. The processor is used to execute code in the memory. When the code is executed, the processor is used to execute the method provided in the application embodiment.

[0132] It should be understood that the aforementioned processor can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. General-purpose processors can be microprocessors or any conventional processor. It is worth noting that the processor can be a processor supporting the Advanced Reduced Instruction Set Computing (RISC) machine (ARM) architecture.

[0133] Further, optionally, the aforementioned memory may include read-only memory and random access memory, and may also include non-volatile random access memory. The memory may be volatile or non-volatile, or may include both. Non-volatile memory may include read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory may include random access memory (RAM), which serves as an external cache. Many forms of RAM are available by way of example, but not limitation. Examples include static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).

[0134] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. A computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the flow or function according to this application is generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another.

[0135] In the description of this specification, the references to terms such as "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of this application. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples. Moreover, without contradiction, those skilled in the art can combine and integrate the different embodiments or examples described in this specification, as well as the features of those different embodiments or examples.

[0136] Any process or method description in the flowchart or otherwise herein can be understood as representing a module, segment, or portion of code comprising one or more executable instructions for implementing a particular logical function or process. Furthermore, the scope of the preferred embodiments of this application includes additional implementations in which functions may be performed not in the order shown or discussed, including substantially simultaneously or in reverse order depending on the functionality involved.

[0137] The logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as a sequenced list of executable instructions for implementing logical functions, and can be embodied in any computer-readable medium for use by, or in conjunction with, an instruction execution system, apparatus or device (such as a computer-based system, a processor-included system or other system that can fetch and execute instructions from, an instruction execution system, apparatus or device).

[0138] It should be understood that various parts of this application can be implemented using hardware, software, firmware, or a combination thereof. In the above embodiments, multiple steps or methods can be implemented using software or firmware stored in memory and executed by a suitable instruction execution system. All or part of the steps of the methods in the above embodiments can be implemented by a program instructing related hardware, the program being stored in a computer-readable storage medium, which, when executed, includes one or a combination of the steps of the method embodiments.

[0139] Furthermore, the functional units in the various embodiments of this application can be integrated into a processing module, or each unit can exist physically separately, or two or more units can be integrated into a module. The integrated module can be implemented in hardware or as a software functional module. If the integrated module is implemented as a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. This storage medium can be a read-only memory, a disk, or an optical disk, etc.

[0140] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any person skilled in the art can easily conceive of various variations or substitutions within the technical scope disclosed in this application, and these should all be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for operating and maintaining a server-side product based on Robotic Process Automation (RPA), Artificial Intelligence (AI), and Large Language Modeling (LLM) to implement an intelligent agent, characterized in that, The operation and maintenance method is applied to an operation and maintenance tool platform. The operation and maintenance tool platform is configured with an operation and maintenance tool library, which contains multiple operation and maintenance tools. Each operation and maintenance tool is used to perform different operation and maintenance operations. The operation and maintenance method includes: Obtain the configuration information of the target operation and maintenance object in the current operating environment. The configuration information includes host configuration information, middleware configuration information and service configuration information. The target operation and maintenance object and the current operation and maintenance tool platform are deployed on the same server. The operation and maintenance object includes the RPA server platform, intelligent document processing platform, intelligent agent document processing platform and intelligent agent process automation platform. Based on the configuration information and operation and maintenance requirements, the target operation and maintenance tool is invoked to perform the operation and maintenance operations corresponding to the operation and maintenance requirements.

2. The method according to claim 1, characterized in that, The step of invoking the target operation and maintenance tool based on the configuration information and operation and maintenance requirements includes: In response to the request to add an operation and maintenance tool, the parameter configuration interface of the operation and maintenance tool is displayed. After the configuration of the target operation and maintenance tool is completed, if a run request for the target operation and maintenance tool is received, the corresponding target operation and maintenance tool is called based on the configuration information and the configured operation and maintenance tool parameter information. The operation and maintenance tool parameters include tool name, tool type, execution action and execution parameters. or, The running status of the target operation and maintenance object is detected based on the configuration information, and the corresponding target operation and maintenance tool is determined according to the abnormal detection items in the detection results, and the target operation and maintenance tool is invoked.

3. The method according to claim 2, characterized in that, The step of detecting the running status of the target maintenance object based on the configuration information includes: Obtain the monitoring platform's detection report on the target maintenance object, and determine the operating status of the target maintenance object based on the detection results in the inspection report. The detection results include abnormal prompt information and corresponding handling methods. The handling methods are obtained by the monitoring platform through calling the Natural Language Processing (NLP) service to analyze the actual operating indicators of each item to be detected. or, The running status of each item to be detected is obtained based on the configuration information, and the running status is detected based on the created inspection task. Each item to be detected includes the system layer basic environment, the application services of the target maintenance object, and the middleware status.

4. The method according to claim 3, characterized in that, The detection of the operating status based on the created inspection task includes: In response to the request to create an inspection task, the detection parameter configuration interface of the inspection task is displayed. The detection parameter configuration interface is used to configure the detection parameters of the inspection task, wherein the detection parameters include the detection start time, the detection end time, and the detection frequency. After the inspection task is configured, the operating status of each inspection item is compared with the corresponding standard operating indicators, and abnormal inspection items that do not meet the corresponding standard operating indicators are marked.

5. The method according to claim 2, characterized in that, The step of determining the corresponding target operation and maintenance tool based on the abnormal detection items in the detection results includes: When a request to view the inspection report of any inspection task is received, the inspection report of the inspection task is displayed on the current interface. The inspection report records the actual operating indicators of each inspection item. When a request to view the runtime log of the anomaly detection item is received, the runtime log of the anomaly detection item is displayed; The target operation and maintenance tool that matches the anomaly detection item is determined based on the operation log.

6. The method according to any one of claims 1-5, characterized in that, After invoking the target operations and maintenance tool, the method further includes: Generate maintenance tasks corresponding to the target maintenance tool.

7. The method according to claim 6, characterized in that, The method further includes: When a viewing request for any type of operation and maintenance task is received, the task details corresponding to the viewing request are displayed. The types of operation and maintenance tasks include: operation and maintenance tasks in progress, completed historical operation and maintenance tasks, inspection tasks, and task plans.

8. The method according to claim 2, characterized in that, After adding the aforementioned operation and maintenance tools, the method further includes: In response to the task plan creation request, the execution strategy setting interface of the task plan is displayed. The execution strategy setting interface is used to configure the target operation and maintenance tools and task triggering rules corresponding to the task plan. The task triggering rules include task start time, task end time, task running frequency and task repeated execution time. After configuring the execution strategy, the corresponding task is executed according to the execution parameters of the target operation and maintenance tool and the configured task triggering rules.

9. The method according to claim 1, characterized in that, The functional models corresponding to each operation and maintenance tool are constructed using the following method: Create a data layer Action entity for the operation and maintenance tool, which serves as the carrier of the operation and maintenance tool; Configure the type field of the Action entity to establish an association between the type field and the class name of the execution action of the operation and maintenance tool, so as to bind the execution action type corresponding to the operation and maintenance tool; Deploy the metadata interface for the execution action, enabling the metadata interface to query the type field corresponding to the Action entity. The metadata interface is used to provide the front-end application layer with services for obtaining, enumerating, and configuring tool types.

10. The method according to claim 1, characterized in that, The operation and maintenance tools include: disk cleanup tools, product configuration modification tools, product service recovery tools, environment anomaly recovery tools, and data recovery and backup tools. Each operation and maintenance tool is generated through an Agent.

11. An operation and maintenance device for server-side products implementing agents based on RPA, AI, and LLM, characterized in that, include: The configuration information acquisition module is used to acquire the configuration information of the target operation and maintenance object in the current operating environment. The configuration information includes host configuration information, middleware configuration information and service configuration information. The target operation and maintenance object and the current operation and maintenance tool platform are deployed on the same server. The operation and maintenance object includes the RPA server platform, intelligent document processing platform, intelligent agent document processing platform and intelligent agent process automation platform. The target operation and maintenance tool invocation module is used to invoke the target operation and maintenance tool based on the configuration information and operation and maintenance requirements, so as to execute the operation and maintenance operation corresponding to the operation and maintenance requirements through the target operation and maintenance tool.

12. The apparatus according to claim 11, characterized in that, The target operation and maintenance tool invocation module includes: The first calling unit is used to respond to the request to add an operation and maintenance tool, display the parameter configuration interface of the operation and maintenance tool, and after completing the configuration of the target operation and maintenance tool, if a run request for the target operation and maintenance tool is received, call the corresponding target operation and maintenance tool based on the configuration information and the configured operation and maintenance tool parameter information. The operation and maintenance tool parameters include tool name, tool type, execution action and execution parameters. or, The second invocation unit is used to detect the running status of the target operation and maintenance object based on the configuration information, determine the corresponding target operation and maintenance tool according to the abnormal detection items in the detection results, and invoke the target operation and maintenance tool.

13. The apparatus according to claim 12, characterized in that, The second calling unit includes: An external detection report identification and acquisition subunit is used to acquire the detection report of the monitoring platform on the target operation and maintenance object, and determine the operating status of the target operation and maintenance object based on the detection results in the inspection report. The detection results include abnormal prompt information and corresponding processing methods. The processing methods are obtained by the monitoring platform by calling the Natural Language Processing (NLP) service to analyze the actual operating indicators of each item to be detected. or, The inspection task execution subunit is used to obtain the running status of each item to be inspected based on the configuration information, and to inspect the running status based on the created inspection task. Each item to be inspected includes the system layer basic environment, the application services of the target maintenance object, and the middleware status.

14. The apparatus according to claim 13, characterized in that, The inspection task execution subunit is specifically used for: In response to the request to create an inspection task, the detection parameter configuration interface of the inspection task is displayed. The detection parameter configuration interface is used to configure the detection parameters of the inspection task, wherein the detection parameters include the detection start time, the detection end time, and the detection frequency. After the inspection task is configured, the operating status of each inspection item is compared with the corresponding standard operating indicators, and abnormal inspection items that do not meet the corresponding standard operating indicators are marked.

15. The apparatus according to claim 12, characterized in that, The second calling unit includes: The inspection report viewing sub-unit is used to display the inspection report of any inspection task on the current interface when a viewing request for the inspection report of any inspection task is received. The operation log display subunit is used to display the operation log of the anomaly detection item when a viewing request for the operation log of the anomaly detection item is received; The target operation and maintenance tool determination subunit is used to determine the target operation and maintenance tool that matches the anomaly detection item based on the operation log.

16. The apparatus according to claim 11, characterized in that, The device further includes: The operation and maintenance task generation module is used to generate operation and maintenance tasks corresponding to the target operation and maintenance tool after the target operation and maintenance tool is invoked.

17. An electronic device, characterized in that, include: A processor and a memory, wherein instructions are stored in the memory and loaded and executed by the processor to implement the method as claimed in any one of claims 1 to 10.

18. A computer-readable storage medium storing a computer program that, when executed by a processor, implements the method as described in any one of claims 1-10.

Images