Software function monitoring method, computer readable storage medium and intelligent equipment

Abstract

The invention relates to the technical field of data monitoring, particularly provides a software function monitoring method, a computer readable storage medium and intelligent equipment, and aims to solve the problem of low software function test efficiency in the prior art. In order to achieve the purpose, the software function monitoring method comprises the steps of directly obtaining a to-be-monitored target range, a to-be-monitored data source, a model architecture and a monitoring task execution condition through an interactive interface, and converting the to-be-monitored target range, the to-be-monitored data source, the model architecture and the monitoring task execution condition into a monitoring program, so that test logic can be conveniently set, the test difficulty can be reduced, and the monitoring range can be flexibly selected; and the test of the to-be-monitored target in a relatively large range can be conveniently realized, so that the test efficiency of the software function can be effectively improved.

Description

Technical Field

[0001] This application relates to the field of data monitoring technology, specifically providing a software function monitoring method, a computer-readable storage medium, and a smart device. Background Technology

[0002] In the era of software-defined vehicles, the software components of new energy vehicles are expanding rapidly, and the significantly shortened software iteration cycle poses a major challenge to testing efficiency. Traditional manual testing methods are not only costly, but their limitations become increasingly apparent when dealing with the complex and multifunctional ECUs of new energy vehicles. The software functional testing process requires testers with a comprehensive understanding of functional logic, which makes in-depth cross-domain understanding difficult for non-specialist personnel, exacerbating the difficulty and cost of testing.

[0003] Furthermore, how to effectively collect, securely transmit, and intelligently analyze vehicle feedback data to support continuous vehicle optimization, functional expansion, and after-sales service has become a critical issue that the new energy vehicle industry urgently needs to address. Currently, cross-domain data and low-frequency data are easily overlooked and not effectively utilized. Summary of the Invention

[0004] This application aims to solve the aforementioned technical problem, namely, to address the issue of low efficiency in existing software functional testing.

[0005] In a first aspect, this application provides a software function monitoring method, comprising:

[0006] The monitoring requirements are obtained through the interactive interface. The monitoring requirements include setting the scope of the target to be monitored, the data source to be monitored, the model architecture, and the execution conditions of the monitoring task.

[0007] The monitoring requirements are converted into a monitoring program, and the monitoring program is run to monitor the software functions of the target area to be monitored.

[0008] Feedback on the monitoring results of the software functions.

[0009] In some embodiments, obtaining monitoring requirements through an interactive interface includes: obtaining the monitoring requirements based on the user's selection or drag-and-drop operation on the interactive interface.

[0010] In some embodiments, obtaining the monitoring task execution conditions through the interactive interface includes obtaining at least one of the following through the interactive interface: user-defined preconditions, triggering conditions, preset execution results, filtering conditions, execution order of multi-step requirements, input variables and output variables of the execution steps.

[0011] In some embodiments, after obtaining monitoring requirements through an interactive interface, the method further includes responding to any one of the following operations performed by the user on the monitoring requirements: querying, adding, modifying, copying, deleting, and exporting.

[0012] In some embodiments, running the monitoring program to monitor the software functions of the target area includes:

[0013] The monitoring program can be executed once or automatically triggered at preset time points to monitor the software functions of the target area.

[0014] In some embodiments, monitoring the software functions of the target area to be monitored includes:

[0015] Obtain the real-time load of each server node;

[0016] Based on the real-time load and the runtime of the monitoring program, server nodes are allocated to monitor the software functions of the target area.

[0017] In some embodiments, before running the monitoring program to monitor the software functions of the target scope, the method further includes:

[0018] Acquire data from multiple data sources within the target area to be monitored;

[0019] Preprocess the data from the various data sources;

[0020] The preprocessed data is stored in a database;

[0021] Running the monitoring program to monitor the software functions of the target area includes: obtaining data from the data source to be monitored from the database through a standardized interface; and monitoring the software functions of the target area according to the monitoring task execution conditions.

[0022] In some embodiments, preprocessing the data from the multiple data sources includes at least one of timestamp alignment and data cleaning.

[0023] In some embodiments, the feedback on the monitoring results of the software function includes: displaying the monitoring results in a visual manner and sending the monitoring results to the target user.

[0024] In a second aspect, this application provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the software function monitoring method described in any of the preceding claims.

[0025] In a third aspect, this application provides a smart device comprising:

[0026] At least one processor;

[0027] And, a memory communicatively connected to the at least one processor;

[0028] The memory stores a computer program, which, when executed by the at least one processor, implements the software function monitoring method described above.

[0029] Solution 1. A software function monitoring method, characterized in that it includes:

[0030] The monitoring requirements are obtained through the interactive interface. The monitoring requirements include setting the scope of the target to be monitored, the data source to be monitored, the model architecture, and the execution conditions of the monitoring task.

[0031] The monitoring requirements are converted into a monitoring program, and the monitoring program is run to monitor the software functions of the target area to be monitored.

[0032] Feedback on the monitoring results of the software functions.

[0033] Solution 2. The method according to Solution 1, characterized in that, obtaining monitoring requirements through the interactive interface includes: obtaining the monitoring requirements based on the user's selection or drag-and-drop operation on the interactive interface.

[0034] Solution 3. The method described in Solution 1 or 2, characterized in that obtaining the monitoring task execution conditions through the interactive interface includes: obtaining at least one of the following through the interactive interface: user-defined preconditions, triggering conditions, preset execution results, filtering conditions, execution order of multi-step requirements, input variables and output variables of the execution steps.

[0035] Solution 4. The method described in Solution 3 is characterized in that, after obtaining the monitoring requirements through the interactive interface, the method further includes: responding to any one of the following operations by the user on the monitoring requirements: querying, adding, modifying, copying, deleting, and exporting.

[0036] Solution 5. The method described in Solution 1, characterized in that, running the monitoring program to monitor the software functions of the target area to be monitored includes:

[0037] The monitoring program can be executed once or automatically triggered at preset time points to monitor the software functions of the target area.

[0038] Solution 6. The method described in Solution 5, characterized in that monitoring the software functions of the target area to be monitored includes:

[0039] Obtain the real-time load of each server node;

[0040] Based on the real-time load and the runtime of the monitoring program, server nodes are allocated to monitor the software functions of the target area.

[0041] Solution 7. The method according to Solution 5, characterized in that, before running the monitoring program to monitor the software functions of the target area to be monitored, the method further includes:

[0042] Acquire data from multiple data sources within the target area to be monitored;

[0043] Preprocess the data from the various data sources;

[0044] The preprocessed data is stored in a database;

[0045] Running the monitoring program to monitor the software functions of the target area includes: obtaining data from the data source to be monitored from the database through a standardized interface; and monitoring the software functions of the target area according to the monitoring task execution conditions.

[0046] Solution 8. The method described in Solution 7, characterized in that the preprocessing of the data from the multiple data sources includes at least one of timestamp alignment and data cleaning of the data from the multiple data sources.

[0047] Solution 9. The method according to Solution 1, wherein the feedback on the monitoring results of the software function includes: displaying the monitoring results in a visual manner and sending the monitoring results to the target user.

[0048] Solution 10. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program, which, when executed by a processor, implements the software function monitoring method described in any one of Solutions 1 to 9 above.

[0049] Option 11. A smart device, characterized in that it comprises:

[0050] At least one processor;

[0051] And, a memory communicatively connected to the at least one processor;

[0052] The memory stores a computer program, which, when executed by the at least one processor, implements the software function monitoring method described in any one of schemes 1 to 9.

[0053] By adopting the above technical solution, this application can provide a software function monitoring method. By directly obtaining the scope of the target to be monitored, the data source to be monitored, the model architecture, and the execution conditions of the monitoring task based on the interactive interface, and converting them into a monitoring program, it is convenient to set up test logic, reduce the difficulty of testing, and can flexibly select the monitoring scope, making it easy to test a larger range of targets to be monitored, thereby effectively improving the testing efficiency of software functions. Attached Figure Description

[0054] The preferred embodiments of this application are described below with reference to the accompanying drawings, in which:

[0055] Figure 1 This is a schematic flowchart of a software function monitoring method provided in an embodiment of this application;

[0056] Figure 2 This is a schematic diagram of the work order closed-loop process provided in the embodiments of this application;

[0057] Figure 3 This is a schematic flowchart of a software function monitoring method provided in another embodiment of this application;

[0058] Figure 4 This is a schematic diagram of a smart device provided in an embodiment of this application;

[0059] Figure 5 This is a software function monitoring system architecture diagram provided in the embodiments of this application;

[0060] Figure 6 This is an architecture diagram of the monitoring requirement management module provided in the embodiments of this application. Detailed Implementation

[0061] Some embodiments of this application are described below with reference to the accompanying drawings. Those skilled in the art should understand that these embodiments are merely illustrative of the technical principles of this application and are not intended to limit the scope of protection of this application.

[0062] In this embodiment, the interactive interface can be designed based on the PaaS (platform as a service) concept, combined with the model architecture designed by finite state automata.

[0063] See Figure 1 As shown, Figure 1 This is a schematic flowchart of a software function monitoring method provided in an embodiment of this application, which includes steps S11-S13.

[0064] Step S11: Obtain monitoring requirements through the interactive interface. Monitoring requirements include setting the scope of the target to be monitored, the data source to be monitored, the model architecture, and the execution conditions of the monitoring task.

[0065] In some embodiments, step S11 may specifically involve obtaining monitoring requirements based on the user's selection or drag-and-drop operation on the interactive interface.

[0066] The software function monitoring method provided in this application embodiment can be applied to vehicles. Taking vehicles as an example, the target range to be monitored can be the range of vehicles to be monitored. The range of vehicles to be monitored can be obtained by the user selecting the identification information of multiple vehicles to be monitored on the interactive interface, or by selecting filtering conditions such as software model or vehicle model.

[0067] The data source to be monitored can be flexibly configured based on user needs. This application provides multiple data sources for users to choose from, such as sensor data, vehicle network logs, and user interaction records. Different data sources can be accessed through model selection. These models can include bus data models, log data models, and multi-source data models. The bus data model can be based on data from any of CAN (Controller Area Network), LIN (Local Interconnect Network), and SOA (Service-Oriented Architecture). The log data model can be based on system log data. The multi-source data model can be based on various data sources such as bus, logs, and messages. The model architecture can be based on a finite state automaton design.

[0068] In some embodiments, the execution conditions of the monitoring task can be set based on the model architecture. In S11, obtaining the execution conditions of the monitoring task through the interactive interface includes obtaining at least one of the following through the interactive interface: user-defined preconditions, trigger conditions, preset execution results, filtering conditions, execution order of multi-step requirements, input variables and output variables of the execution steps.

[0069] The execution order of a multi-step requirement can include the sequential execution of multiple steps or the parallel execution of some steps followed by the execution of other steps. The input and output variables of the execution steps can be the input and output variables corresponding to each step of the multi-step requirement.

[0070] As an example, when monitoring needs to obtain scenario data such as "Users of Model A fail to unlock the vehicle using a mobile phone Bluetooth key", the data source can be either CAN or LIN, and the corresponding model architecture can adopt a bus data model. The prerequisite can be "all vehicles are locked" and "the state is maintained for 2 seconds", the trigger condition can be "the key is located from zone 3 to zone 2" and "maintained for 2 seconds", the preset execution result can be "all vehicles are locked" and "the state is maintained for 2 seconds", and the filter condition can be "Model A vehicle" and "mobile phone Bluetooth key".

[0071] Step S12: Convert the monitoring requirements into a monitoring program and run the monitoring program to monitor the software functions of the target scope.

[0072] This step parses the monitoring requirements obtained by the user through the interactive interface into SQL code mapping rules. These mapping rules include logical and conditional mappings, such as: logical operator mapping, where "AND," "OR," and "NOT" edited in the interactive interface directly correspond to AND, OR, and NOT in the SQL WHERE clause. If there are multiple levels of nested logic (e.g., (condition 1 AND condition 2) OR condition 3), the parenthesis hierarchy in the interactive interface is preserved, and parentheses are used in SQL to maintain logical priority. Comparison condition mapping: the comparison operations selected in the interactive interface (equal to, greater than, contain, etc.) correspond to the comparison operators and keywords in SQL. Field and table mapping: the data source table name selected in the interactive interface corresponds to the table name after the FROM clause in SQL, and the selected fields correspond to the field list after the SELECT clause.

[0073] When converting monitoring requirements into monitoring programs, this can include: mapping corresponding data tables based on the model architecture; mapping SQL query frameworks based on the Precondition-Action-Result-Filter model architecture; mapping data to fields in the data table based on the parameter types selected according to the monitoring task execution conditions, such as "key location" and "vehicle model"; and mapping data to the numerical relationships of fields, such as "vehicle locked" and "Model A vehicle".

[0074] In some embodiments, step S12, converting monitoring requirements into monitoring programs, includes: executing the monitoring program once or automatically triggering it at preset time points to monitor the software functions of the target scope.

[0075] The monitoring of software functions within the target scope includes: obtaining the real-time load of each server node; and allocating server nodes based on the real-time load and the runtime of the monitoring program to monitor the software functions within the target scope.

[0076] Step S13: Feedback on the monitoring results of the software functions.

[0077] In some embodiments, step 13 may specifically involve: displaying the monitoring results in a visual manner and sending the monitoring results to the target user.

[0078] In some embodiments, the interactive interface can display the running status of monitoring tasks, the frequency and trend of software problems in a visual manner such as pie charts or line graphs. It can also display monitoring results in conjunction with dimensions such as vehicle software version and vehicle mileage to help users intuitively understand the status of monitoring tasks.

[0079] In some embodiments, monitoring results can be displayed visually through an interactive interface. These results can be presented as work orders and sent to the target user via a call to an associated application, such as Lark, for subsequent analysis. Work order creation is triggered by the result table corresponding to the monitoring task, and the work order is stored in a new data table.

[0080] In some embodiments, users can also modify the data table content through clicks on the interactive interface, thereby achieving a closed-loop operation for software issue work orders. The work order closed-loop process is as follows: Figure 2 As shown, when a user creates an issue, it enters the Open state. If the issue is determined to be dirty data, it will directly proceed to the Discard state. Engineers can then analyze the remaining data. If data is found to be missing during the analysis, the issue enters the Tracking state. Once the data is complete, the issue returns to the Analyzing state for further processing. When the root cause (RC) of the issue is confirmed, the issue finally transitions to the Closed state.

[0081] The above is a software function monitoring method provided by the embodiments of this application. By directly obtaining the scope of the target to be monitored, the data source to be monitored, the model architecture, and the execution conditions of the monitoring task based on the interactive interface, and converting them into a monitoring program, it is beneficial to conveniently set up test logic, reduce the difficulty of testing, and flexibly select the monitoring scope, which is convenient for testing a larger range of targets to be monitored, thereby effectively improving the testing efficiency of software functions.

[0082] See Figure 3 As shown, Figure 3 This is a schematic flowchart of a software function monitoring method provided in another embodiment of this application, which may include steps S31-S37.

[0083] Step S31: Obtain data from multiple data sources for the target area to be monitored.

[0084] In some embodiments, the data source may include sensor data, vehicle network logs, and user interaction records.

[0085] Step S32: Preprocess data from multiple data sources.

[0086] In some embodiments, step S32 may specifically involve performing at least one of timestamp alignment and data cleaning on data from multiple data sources.

[0087] Timestamp alignment can be performed by: extracting timestamp information from each data source; converting the extracted timestamps to UTC (Coordinated Universal Time) format to ensure that the time base of all data sources is consistent; and aligning the data by time window, for example, aggregating all data by a 1-second time window to ensure that data within the same time window can be jointly analyzed.

[0088] In some embodiments, other preprocessing can be performed on the data, such as checking the integrity of the data through predefined format validation rules when the data enters the system to ensure that each data record contains necessary fields, such as timestamps and device IDs (identifiers); providing various processing strategies for missing data fields, such as filling in default values, interpolation, or deleting missing records; detecting outliers in the data through statistical methods or machine learning models, for example, using Z-score methods or IQR (interquartile range) methods to identify and process outliers; and normalizing numerical data, such as converting all values ​​to the range between 0 and 1, to facilitate subsequent data analysis.

[0089] Step S33: Store the preprocessed data in the database.

[0090] In vehicle-side data processing, there are many types of data, including but not limited to CAN data, LIN data, log data, and Pcap (Packet Capture) data. These data have different characteristics; some require frequent real-time queries, some require long-term historical data storage, and others require efficient data analysis and aggregation. Therefore, storing this data requires the use of different types of databases to ensure efficient storage and management.

[0091] In some embodiments, the database type may include multiple types such as relational database (MySQL), data warehouse (Hive), high-performance time-series database (Iceberg), and columnar database (Clickhouse).

[0092] To ensure efficient integration and management of different databases, multiple databases can adopt standardized interfaces to facilitate unified access to different databases and ensure data interoperability and consistency.

[0093] In some embodiments, a data synchronization mechanism may also be employed to ensure data consistency between different databases. For example, real-time data may be synchronized from a time-series database to a data warehouse for historical data analysis.

[0094] In some embodiments, performance optimization can also be performed based on the characteristics of different databases. For example, partitioning and indexing can be created for Hive tables to improve query efficiency; columnar storage optimization can be performed for Clickhouse tables to improve query speed; monitoring and maintenance can be carried out by monitoring the database's operating status in real time through a monitoring system to promptly identify and resolve problems, while regular database maintenance can be performed to ensure the stability and reliability of the system.

[0095] In some embodiments, the data described above can be uniformly stored in a high-performance distributed storage system. This storage system supports high-concurrency access and fast retrieval. Specific implementations include: using a distributed file system (such as Hadoop HDFS) or a distributed key-value store (such as Cassandra) to store data, ensuring high availability and scalability; indexing frequently used query fields to improve data retrieval speed, for example, indexing timestamp fields to quickly find data within a specific time range; and sharding data according to time range or data type to ensure even data distribution and avoid hotspot issues.

[0096] Step S34: Obtain monitoring requirements through the interactive interface. Monitoring requirements include setting the scope of the target to be monitored, the data source to be monitored, the model architecture, and the execution conditions of the monitoring task.

[0097] Step S35: Convert the monitoring requirements into a monitoring program and obtain the data from the data source to be monitored from the database through a standardized interface.

[0098] In this embodiment, data from different databases can be accessed by calling standardized interfaces, thus supporting multiple data formats, such as SQL databases, NoSQL (Not Only SQL) databases, time series databases, and file systems.

[0099] Step S36: Monitor the software functions of the target area according to the monitoring task execution conditions.

[0100] Step S37: Provide feedback on the monitoring results of the software functions.

[0101] Steps S34, S36, and S37 can be implemented in the same way as the corresponding steps in S11-S13. For the sake of brevity, they will not be described in detail here. Please refer to the description above for details.

[0102] It should be noted that, in this embodiment, steps S31-S33 are executed first, followed by steps S34-S37. Those skilled in the art will understand that, as long as steps S31-S33 are performed before step S35, any other reasonable change in the order of steps falls within the protection scope of this embodiment.

[0103] This application embodiment supports multiple data sources, which helps ensure data integrity and timeliness, optimizes the utilization of data resources, and facilitates users to easily set monitoring requirements and intuitively monitor and analyze the execution status of monitoring tasks by combining an interactive interface designed based on PaaS thinking. This improves testing efficiency and facilitates users' understanding of the data. By combining a model architecture designed with finite state automata, monitoring requirements are transformed into monitoring programs, which can realize the automatic execution of monitoring logic and the analysis of monitoring results. This is conducive to automatically identifying changes in the state of software functions and realizing the intelligent capture and analysis of low-frequency problem data.

[0104] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments of this application can also be implemented by a computer program instructing related hardware. The computer program can be stored in a computer-readable storage medium, and when executed by a processor, it can implement the steps of the various method embodiments described above. The computer program includes computer program code, which can be in the form of source code, object code, executable files, or certain intermediate forms. The computer-readable storage medium can include any entity or device capable of carrying computer program code, a medium, a USB flash drive, a portable hard drive, a magnetic disk, an optical disk, a computer memory, a read-only memory, a random access memory, an electrical carrier signal, a telecommunication signal, and a software distribution medium, etc.

[0105] Another aspect of this application provides a computer-readable storage medium storing a computer program that, when executed by a processor, can implement the software function monitoring method in any of the above embodiments. This computer-readable storage medium can be a storage device comprising various electronic devices. Optionally, in the embodiments of this application, the computer-readable storage medium is a non-transitory computer-readable storage medium.

[0106] Another aspect of this application provides a smart device.

[0107] In one embodiment of a smart device according to this application, the smart device may include at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores a computer program, which, when executed by the at least one processor, implements the method of any of the above embodiments. The smart device of this application may include driving equipment, smart vehicles, robots, and other devices. See appendix. Figure 4 , Figure 4 The example shows a memory 41 and a processor 42 connected via a bus communication connection.

[0108] In some embodiments of this application, the smart device may further include at least one sensor for sensing information. The sensor is communicatively connected to any type of processor mentioned in this application. Optionally, the smart device may further include an autonomous driving system for guiding the smart device to drive autonomously or assisting in driving. The processor communicates with the sensor and / or the autonomous driving system to perform the methods of any of the above embodiments.

[0109] Figure 5 This is an architecture diagram of a software function monitoring system provided in an embodiment of this application. The software function monitoring method provided in this application can be implemented based on this system, such as... Figure 5 As shown, it can include a presentation layer, an application layer, a data layer, and a database.

[0110] The presentation layer can be used to interact with users, including receiving user input, displaying relevant information to users, or accessing the application layer through an interface and completing user instructions, such as querying monitoring results or executing step S13.

[0111] This system offers two access methods: one is access via a personal computer browser (PC web), which is accessed through a standard web browser; the other is access via the Lark app mini-program on mobile devices.

[0112] The application layer can be used to implement steps S11-S13 or S34-S37, and it can include multiple modules such as monitoring information statistics, monitoring demand management, monitoring task management and monitoring result management.

[0113] The monitoring information statistics module can be used to support users in setting the monitoring target range or query range through field combinations, generating query programs, running query programs, obtaining monitoring result tables and returning them. The interactive interface supports displaying the running status of monitoring tasks in a visual way, such as pie charts and line charts, showing the frequency and trend of software problems, and displaying monitoring results in combination with dimensions such as vehicle software version and vehicle mileage, so as to help users intuitively understand the status of monitoring tasks.

[0114] Figure 6 This is an architecture diagram of the monitoring requirement management module provided in this application embodiment. It can include multiple layers: main functions, model selection, model architecture, and mapping relationships. The main functions layer is configured to implement query, add, modify, copy, delete, and export monitoring requirements sent through an interactive interface. The model selection layer is configured to allow users to set data sources and select specific models based on different data sources, such as bus data models, log data models, and multivariate data models. The model architecture layer is configured to manage the execution conditions of monitoring tasks, including functions such as supporting configuration of preconditions, trigger actions, result judgment, filters, multi-step requirements, and variable generation. Variable generation can include the generation of input and output variables. The mapping relationship layer can be configured to implement logical operator mapping, comparison condition mapping, and field-table mapping to convert monitoring requirements obtained from the interactive interface into monitoring programs, such as SQL code. In some embodiments, when the monitoring results do not meet expectations, the monitoring requirement management module can also be used to respond to any of the following user operations on monitoring requirements: query, add, modify, copy, delete, and export.

[0115] The monitoring task management module can be used to implement functions such as selecting the monitoring target range and task management. For example, it can manage a vehicle range table, recording all vehicle resources of the enterprise, including vehicle attributes and software version information. Users select the vehicle range through an interactive interface, and the front-end parameters add SQL code conditions to limit the monitored vehicle range. This module can load the SQL code converted by the monitoring requirement module, merge the monitoring task execution conditions and monitoring target range, and generate a complete SQL query statement. In some embodiments, this module can also change the state of the SQL node through front-end parameters, thereby determining whether the script runs and the script execution method. The execution method can be divided into single execution and automatic triggering execution at preset time points. In some embodiments, this module can also be used to determine the number of server nodes occupied based on the runtime of the monitoring task. When the runtime exceeds a set threshold, the new monitoring task is configured to run on a new node.

[0116] In some embodiments, when the monitoring results meet expectations, the monitoring task management module can also be used to officially launch the current software based on the user's selected data source, etc.

[0117] The data layer can include data from various data sources, such as CAN data, LIN data, ECU data, vehicle infotainment system data, vehicle-level data, and Ethernet data. The data layer can access data from different databases by calling standardized interfaces. In some embodiments, the data layer can also perform timestamp alignment, data cleaning, or other preprocessing on the received data and store it in a high-performance distributed storage system for rapid retrieval.

[0118] Databases are used to store and manage data. Different types of databases can be used for data storage based on needs such as data source, query frequency, query time, and ease of efficient data analysis and aggregation. Figure 5 As shown, the database can include MySQL, Hive, Iceberg, ClickHouse, and other similar databases.

[0119] The relevant user personal information that may be involved in the various embodiments of this application is processed in strict accordance with the requirements of laws and regulations, following the principles of legality, legitimacy, and necessity, based on the reasonable purpose of the business scenario, and includes personal information that users actively provide or that is generated as a result of using the product / service, as well as personal information obtained with user authorization.

[0120] The personal information processed in this application will vary depending on the specific product / service scenario and will be based on the specific scenario in which the user uses the product / service. This may involve the user's account information, device information, driving information, vehicle information, or other related information. This application will treat the user's personal information and its processing with the utmost diligence.

[0121] This application attaches great importance to the security of users' personal information and has taken reasonable and feasible security protection measures that comply with industry standards to protect users' information and prevent unauthorized access, disclosure, use, modification, damage or loss of personal information.

[0122] The technical solutions of this application have been described above with reference to the preferred embodiments shown in the accompanying drawings. However, it will be readily understood by those skilled in the art that the scope of protection of this application is obviously not limited to these specific embodiments. Without departing from the principles of this application, those skilled in the art can make equivalent changes or substitutions to the relevant technical features, and the technical solutions after these changes or substitutions will all fall within the scope of protection of this application.

Claims

1. A software function monitoring method characterized by, The method comprises the following steps: obtaining monitoring requirements through an interactive interface, wherein the monitoring requirements include setting a target range to be monitored, a data source to be monitored, a model architecture, and a monitoring task execution condition; converting the monitoring requirements into a monitoring program, and running the monitoring program to monitor software functions of the target range to be monitored; feeding back monitoring results of the software functions.

2. The method of claim 1, wherein, The step of obtaining monitoring requirements through an interactive interface comprises the following steps:

3. The method according to claim 1 or 2, characterized in that, obtaining the monitoring requirements according to selection or drag-and-drop operations of a user on the interactive interface.

4. The method of claim 3, wherein, The step of obtaining a monitoring task execution condition through the interactive interface comprises the following steps:

5. The method of claim 1, wherein, obtaining at least one of a precondition, a trigger condition, a preset execution result, a filtering condition, an execution order of multiple steps, an input variable, and an output variable of an execution step, which are customized by a user. After obtaining the monitoring requirements through the interactive interface, the method further comprises the following steps:

6. The method of claim 5, wherein, responding to any one of the following operations of a user on the monitoring requirements: querying, adding, modifying, copying, deleting, and exporting. The step of running the monitoring program to monitor software functions of the target range to be monitored comprises the following steps: running the monitoring program once or automatically triggering the monitoring program to monitor the software functions of the target range to be monitored at preset time points.

7. The method of claim 5, wherein, The step of monitoring software functions of the target range to be monitored comprises the following steps: obtaining real-time load of each server node; allocating server nodes to monitor the software functions of the target range to be monitored according to the real-time load and a running time length of the monitoring program. Before the step of running the monitoring program to monitor software functions of the target range to be monitored, the method further comprises the following steps: obtaining data of multiple data sources of the target range to be monitored; 8. The method of claim 7, wherein, preprocessing the data of the multiple data sources; 9. The method of claim 1, wherein, storing the preprocessed data into a database; 10. A computer-readable storage medium, characterized in that, The step of running the monitoring program to monitor software functions of the target range to be monitored comprises the following steps: obtaining data of the data source to be monitored from the database through a standardized interface; and monitoring the software functions of the target range to be monitored according to the monitoring task execution condition. The step of preprocessing the data of the multiple data sources comprises the following steps: performing at least one of time stamp alignment and data cleaning on the data of the multiple data sources. The step of feeding back monitoring results of the software functions comprises the following steps: displaying the monitoring results in a visual manner, and sending the monitoring results to a target user. The computer readable storage medium stores a computer program, and the computer program is executed by a processor to implement the software function monitoring method in any one of claims 1 to 9.

Images