Fault handling method, device, equipment and storage medium based on report development

By cleaning and aggregating the risk prevention and control information and fault statistics in the data warehouse, and generating fault processing reports using the report platform, the problem of data processing time and inaccurate results in the existing technology is solved, and the fault is achieved The functions of accurate monitoring and performance assessment improve the company's operational quality and customer satisfaction.

CN115033649BActive Publication Date: 2024-11-19XINAO SHUNENG TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202210613123.7
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2022-05-31
Publication Date
2024-11-19
Estimated Expiration
2042-05-31

AI Technical Summary

Technical Problem

The existing data warehouse has problems such as long data processing time, inaccurate data processing results, and inability to clarify the cause of the failure. It lacks statistics on risk classification, risk type, fault completion status and quality classification of each business domain. Analysis leads to difficulties in evaluating team and individual performance.

Method used

By grouping preset risk types, determining business domains, and obtaining risk prevention and control information and fault statistics from the distributed task platform, cleaning and aggregating data, using the report platform to generate fault processing reports, and achieving the target enterprise object Fault monitoring and performance assessment.

Benefits of technology

It reduces the time-consuming data processing, improves data processing efficiency, can accurately obtain fault-related information, improves employees' enthusiasm for solving faults, and increases customers' trust and satisfaction with the company.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN115033649B_ABST
    Figure CN115033649B_ABST
Patent Text Reader

Abstract

The present disclosure provides a fault handling method, device, equipment and storage medium based on report development. The method includes: using risk prevention and control information, online fault statistics information, fault completion status statistics information, quality score statistics information and test fault statistics information as initialization information, synchronizing the initialization information to the data warehouse; using the data warehouse to process the initialization information into table data, and performing data cleaning and aggregation on the table data, summarizing the cleaned and aggregated tables according to the business theme to obtain summary table data; using a preset report platform to query the summary table data stored in the data warehouse, based on the queried target table data and the pre-created report configuration, generate a fault handling report, and monitor the faults of the business domain of the target enterprise object based on the fault handling report. The present disclosure reduces the time consumption of data processing, improves the efficiency of data processing, and can accurately obtain fault-related information.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates to the field of data processing technology, and in particular to a fault handling method, device, equipment and storage medium based on report development. Background Art

[0002] The data warehouse of the traditional big data platform is generally divided into the source data layer, data warehouse layer, data mart layer and data application layer. The data warehouse layer is used to clean the data in the source data layer and summarize the fields of the same granularity so as to provide it to the upper data mart layer for better use. In real applications, data warehouses are mainly used to store, clean and process various data, so as to provide users with the required data based on the data processing results of the data warehouse.

[0003] In the prior art, when using data warehouses to process data, data is simply layered without strict division of data layers, resulting in a chaotic data table in the data warehouse, which is not conducive to the expansion of the data warehouse; in addition, when generating relevant data for fault processing, there is no statistical analysis of risk points and risk types for each business domain, no statistics on the status of online faults and their completion, no evaluation of the quality points of each team in the enterprise, resulting in the inability to assess the performance of teams and individuals, and no statistics on the status of testers' testing problems, etc. Therefore, the existing data warehouse data processing methods have the problems of long data processing time, inaccurate data processing results, and inability to clarify the cause of the fault. Summary of the invention

[0004] In view of this, the embodiments of the present disclosure provide a fault handling method, apparatus, device and storage medium based on report development to solve the problems existing in the prior art, such as long data processing time, inaccurate data processing results, and inability to clearly identify the cause of the fault.

[0005] In a first aspect of an embodiment of the present disclosure, a fault handling method based on report development is provided, including: grouping preset risk types and determining business domains, and determining risk scores and risk types corresponding to each business domain of a target enterprise object based on the risk type and business domain; obtaining risk prevention and control information corresponding to the business domain of the target enterprise object from a distributed task platform, and counting online faults corresponding to the business domain to obtain online fault statistical information, and counting fault completion status based on online faults to obtain fault completion status statistical information; counting the total quality score, R&D quality score, online quality score and fault quality score of the target enterprise object according to a pre-configured quality score statistical method, and determining quality score statistical information corresponding to the target enterprise object based on the statistical results; obtaining the test personnel's The test information generated when a test failure occurs is counted to obtain test failure statistics information, and the risk prevention and control information, online failure statistics information, failure completion statistics information, quality score statistics information and test failure statistics information are used as initialization information, and the initialization information is synchronized to the data warehouse; the data warehouse is used to process the initialization information into tabular data, and the tabular data is cleaned and aggregated. The tables after data cleaning and aggregation are summarized according to preset business topics to obtain summarized tabular data; the preset reporting platform is used to query the summarized tabular data stored in the data warehouse, and a fault handling report is generated based on the queried target tabular data and the pre-created report configuration, and the faults in the business domain of the target enterprise object are monitored based on the fault handling report.

[0006] According to a second aspect of the disclosed embodiments, a fault handling device based on report development is provided, including: a determination module, configured to group preset risk types and determine business domains, and determine the risk points and risk types corresponding to each business domain of the target enterprise object based on the risk type and business domain; an acquisition module, configured to obtain risk prevention and control information corresponding to the business domain of the target enterprise object from the distributed task platform, and to count online faults corresponding to the business domain to obtain online fault statistical information, and to count fault completion status according to online faults to obtain fault completion status statistical information; a statistical module, configured to count the total quality score, R&D quality score, online quality score and fault quality score of the target enterprise object according to a pre-configured quality score statistical method, and determine the quality score statistical information corresponding to the target enterprise object according to the statistical results; a synchronization module, configured to The system is configured to obtain the test information generated by the test personnel when testing failures, to obtain test failure statistics by statistics on the test information, to use the risk prevention and control information, online failure statistics, failure completion statistics, quality score statistics and test failure statistics as initialization information, and to synchronize the initialization information to the data warehouse; the processing module is configured to use the data warehouse to process the initialization information into table data, and to perform data cleaning and aggregation on the table data, and to summarize the cleaned and aggregated tables according to preset business themes to obtain summary table data; the monitoring module is configured to use the preset report platform to query the summary table data stored in the data warehouse, to generate a fault handling report based on the queried target table data and the pre-created report configuration, and to monitor the faults of the business domain of the target enterprise object based on the fault handling report.

[0007] At least one of the above technical solutions adopted in the embodiments of the present disclosure can achieve the following beneficial effects:

[0008] By taking risk prevention and control information, online fault statistics, fault completion statistics, quality score statistics and test fault statistics as initialization information, the initialization information is synchronized to the data warehouse; the data warehouse is used to process the initialization information into table data, and the table data is cleaned and aggregated, and the cleaned and aggregated tables are summarized according to business themes to obtain summary table data; the summary table data stored in the data warehouse is queried using a preset report platform, and a fault processing report is generated based on the queried target table data and the pre-created report configuration, and the faults of the business domain of the target enterprise object are monitored based on the fault processing report. The disclosure reduces the time consumption of data processing, improves the efficiency of data processing, and can accurately obtain fault-related information. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present disclosure. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0010] Figure 1 It is a flowchart of a fault handling method based on report development provided by an embodiment of the present disclosure;

[0011] Figure 2 It is a structural diagram of a fault handling device based on report development provided by an embodiment of the present disclosure;

[0012] Figure 3 It is a schematic diagram of the structure of an electronic device provided by an embodiment of the present disclosure. DETAILED DESCRIPTION

[0013] In the following description, specific details such as specific system structures and technologies are provided for the purpose of illustration rather than limitation, so as to provide a thorough understanding of the embodiments of the present disclosure. However, it should be clear to those skilled in the art that the present disclosure may be implemented in other embodiments without these specific details. In other cases, detailed descriptions of well-known systems, devices, circuits, and methods are omitted to avoid obstructing the description of the present disclosure with unnecessary details.

[0014] Many businesses of enterprises are very complex, and they are connected to many third-party systems. Online failures often occur. Once a failure occurs, it takes several hours to recover. Every time a failure occurs, it must be repaired urgently and put online urgently. Fixing a problem often brings new problems. The problem here is that there is no emergency plan for failures, data monitoring and availability monitoring of core businesses, inspection mechanisms, etc. The existing fault handling system does not count the status of online faults raised and completed; it does not evaluate the quality score of each team in the enterprise, resulting in the inability to assess the performance of teams and individuals; it does not count the situation of testers testing problems, etc.

[0015] In order to ensure the stability and security of the service, it is necessary to introduce norms and processes. In order to ensure the quality of delivery and operation, enterprises will formulate reward and punishment rules. Formal companies will not directly and arbitrarily determine the responsibility for problems found online. The omission of problems involves a wide range of areas. Only after the problem is analyzed clearly can we decide which field is the main responsibility and which field is the secondary responsibility, so that closed-loop improvements can be made. However, this disclosure comprehensively evaluates employee performance by the risk level and type of faults, the completion of online faults, and the quality score of employees, so as to achieve a degree of reward and punishment. It can also conduct risk assessment and contingency plans before the service goes online based on experience and lessons, realize system monitoring, set fault levels, and perform fault stop loss and recovery. This disclosure can improve the enthusiasm of employees to solve faults and problems, and accumulate experience and lessons, so that existing problems will not fail again, and improve customers' trust and satisfaction with the company, which is very beneficial to the long-term development of the company.

[0016] The following describes in detail the risks that may exist in the business domain of the existing target enterprise object in conjunction with specific embodiments. In actual work, there are many risks in the business domain, which generally include security risks, operational risks, and technical risks.

[0017] 1. The main security risks are as follows:

[0018] (1) Information asset security risks: ① Data leakage behavior: monitoring and alarm mechanism for data usage behavior; ② Data desensitization: the effectiveness of the data desensitization mechanism.

[0019] (2) Third-party interaction risks: ① Encrypted text transmission: encrypted text transmission of third-party interaction request information; ② Whitelist control: whether there are whitelist restrictions on third-party interaction.

[0020] (3) Network security risks: ① Network attacks: detection and protection against network attacks; installation and updating of antivirus software for detection and protection against network attacks; ② Network protection: validity period of certificates and firewalls; ③ Network isolation: whether the production network is effectively isolated from other networks, resulting in the online environment calling the test environment.

[0021] II. Operational risks are mainly as follows:

[0022] (1) Business operation function risks: ① Risk of core changes in the background being released without review: If the parameter settings lack appropriate approval authorization and review mechanisms, it may lead to erroneous operations and bring business risks; ② Effectiveness of log management: Clarify the content, desensitization, access and storage requirements of log records. If the log retention period is insufficient or there are no log records, it may lead to a lack of logs for responsibility tracing; ③ Reasonableness of authority design / allocation risk: The system authority design authority granularity is too coarse and the authority allocation is unreasonable, which may lead to excessive authorization and bring fraud / operation risks; ④ Behavioral audit: Regular audits are established for key operations to identify operational risks in a timely manner; whether the audit diary framework is connected.

[0023] (2) Release change risks: ① Release permission control risk: There is no control process for online release, and too much permission is granted; ② Domain name configuration change: Changes to the primary domain name, secondary domain name, and jump link are not verified, and the diversion plan causes users to fail to access the old domain name; ③ Configuration change risk: Online release, frequent updates of configuration files lead to configuration errors and omissions;

[0024] (3) Database operation risks: ①DB permission management: The database has no restriction functions, for example, the local can directly connect to the production database; ②Data export control: There are no restrictions or processes for exporting data from the database, such as sensitive data desensitization and data export approval process.

[0025] 3. The main technical risks are as follows:

[0026] (1) Middleware and data storage risks: ① Master-slave mechanism: The core service database does not have a master-slave mechanism, and database anomalies lead to the unavailability of the entire business; ② Processing large data sets: Too much data is processed at one time, resulting in resource exhaustion, poor performance, response delays, timeout failures, and even downtime; ③ Message backlog and fault tolerance mechanism: Message backlogs and message consumption failures in the core link lead to abnormal business processes on the consumer side; ④ Index missing: Database indexes sort data for easy search. If a field is used as a SQL filter condition (such as querying orders based on user ID), index missing will cause each data query to traverse the entire data, resulting in poor performance. When the data volume of the data table is relatively large (may not much at present, but will increase over time) and the query operation is frequent, the risk level is high; ⑤ Cache usage strategy: The core service cache avalanche and penetration occur, and all traffic directly queries the table, resulting in database anomalies and unavailability; ⑥ Read-write separation: Read-write separation, the master and backup databases have long delays, resulting in inaccurate query business data.

[0027] (2) Transaction risks: ① Transaction consistency: Transaction inconsistency, such as a successful order placement but a failed inventory deduction, resulting in oversold inventory; ② Distributed transactions: Data inconsistency. The lack of distributed locks in distributed transactions leads to data inconsistency between multiple parallel transactions, resulting in business anomalies.

[0028] (3) Performance and capacity risks: ① Capacity planning: core services have no capacity planning, resulting in service unavailability due to large traffic; ② Batch export restrictions: batch export or import operations cause service memory overflow and service unavailability; ③ Data growth predictability: whether the data volume growth is reasonably estimated, resulting in service unavailability (such as an increase in the number of users); ④ Service dynamic planning: whether the core service has a dynamic expansion plan; ⑤ Traffic limiting: whether the core service has traffic limiting measures when encountering large traffic.

[0029] (4) Service dependency risks: ① Interface incompatibility: When an interface changes, the dependent party must be notified to assess the impact and conduct joint debugging. Otherwise, the interface will be incompatible and cannot be debugged. When an interface changes, the upstream and client joint debugging must be notified. If a third party is involved, the third-party joint debugging must also be notified. We must also be notified of changes to the third-party interface, and if we cannot debug the third-party interface, we need to log an error level and immediately trigger a monitoring alarm. ② Service unavailability: When an external dependency is unavailable, how is the business handled? Is it interrupted, rolled back, continued, or retried? Does it meet business requirements? Are there any monitoring alarms for the faulty application and the upstream application? Is there a downgrade plan for the upstream application? ③ Lack of monitoring and alarm: Failure to connect to the APM full-link and monitoring and alarm platform makes it difficult to detect and locate faults in a timely manner; ④ Unreasonable timeout mechanism: If the timeout is too short, normal requests will also fail; If the timeout is too long, when the human-machine recognition service is unavailable or responds slowly, the application threads will be full and a large number of user requests will time out; The processing method after the timeout does not meet product expectations, resulting in business abnormalities; When the downstream application responds to the timeout, how should the upstream application handle it? Whether to retry, and whether the business is considered successful, failed, or unknown after the retry reaches the upper limit; Human-machine recognition and risk control protection services, whether to retry after the timeout, and whether to default to release or default to intercept after the retry reaches the upper limit.

[0030] (5) Architectural design risks: ① Coupling degree: The coupling degree is too high, such as multiple core business processes in the same service; ② The call link is too long: The core link is too long, and a problem occurs in one link, causing the entire core business to be unavailable.

[0031] (6) Disaster recovery risk: ① Backup and recovery test: whether important business systems have implemented timely and effective backups and conducted data recovery tests; ② Disaster recovery drill plan: whether core systems and nodes have conducted disaster recovery drills; ③ Disaster recovery plan and emergency plan: whether important business systems have been included in the disaster recovery plan and whether emergency plans have been formulated for important business systems.

[0032] Figure 1 It is a flowchart of a fault handling method based on report development provided in an embodiment of the present disclosure. Figure 1 The report-based fault handling method can be executed by the server. Figure 1 As shown, the fault handling method based on report development may specifically include:

[0033] S101, grouping preset risk types and determining business domains, and determining risk points and risk types corresponding to each business domain of the target enterprise object based on the risk types and business domains;

[0034] S102, obtaining risk prevention and control information corresponding to the business domain of the target enterprise object from the distributed task platform, and counting online faults corresponding to the business domain to obtain online fault statistical information, and counting fault completion status according to the online faults to obtain fault completion status statistical information;

[0035] S103, according to a pre-configured quality score statistics method, the total quality score, R&D quality score, online quality score and fault quality score of the target enterprise object are counted, and quality score statistical information corresponding to the target enterprise object is determined according to the statistical results;

[0036] S104, obtaining test information generated by the tester when testing a failure, performing statistics on the test information to obtain test failure statistics, taking risk prevention and control information, online failure statistics, failure completion statistics, quality score statistics, and test failure statistics as initialization information, and synchronizing the initialization information to the data warehouse;

[0037] S105, using the data warehouse to process the initialization information into table data, and performing data cleaning and aggregation on the table data, and summarizing the cleaned and aggregated tables according to preset business themes to obtain summary table data;

[0038] S106, using a preset report platform to query the summary table data stored in the data warehouse, generating a fault handling report based on the queried target table data and the pre-created report configuration, and monitoring the faults of the business domain of the target enterprise object based on the fault handling report.

[0039] Specifically, the data warehouse (DW) of the disclosed embodiment is obtained by systematically processing, summarizing and organizing the original scattered database data after extraction and cleaning. The purpose of data warehouse construction is to provide functional analysis and decision support as a basis for front-end query and analysis. The disclosed embodiment adopts the Hive data warehouse tool. The Hive data warehouse is mainly used to process structured data. The Hive data warehouse is generally divided into 4 levels, namely the ODS layer, DWD layer, DWS layer and ADS layer, and each level is used to store different types of tables.

[0040] Furthermore, the reporting platform may adopt the ubiquitous reporting platform, and the ubiquitous reporting platform may also be used to replace the reporting platform in the embodiments of the present disclosure in the following embodiments. In the ubiquitous reporting platform, the portal is the entire content of the report, and the portal includes multiple dashboards. In the ubiquitous reporting platform, the dashboard is the dashboard content of the report, including multiple widgets. In the ubiquitous reporting platform, the widget is the chart content of the report. In the embodiments of the present disclosure, the query operation in the ubiquitous reporting platform uses the Presto query engine, and Presto is used to query data in the Hive data warehouse tool.

[0041] According to the technical solution provided by the embodiment of the present disclosure, by taking risk prevention and control information, online fault statistics, fault completion status statistics, quality score statistics and test fault statistics as initialization information, the initialization information is synchronized to the data warehouse; the data warehouse is used to process the initialization information into table data, and the table data is cleaned and aggregated, and the cleaned and aggregated tables are summarized according to the business theme to obtain the summarized table data; the summarized table data stored in the data warehouse is queried using a preset report platform, and a fault handling report is generated based on the queried target table data and the pre-created report configuration, and the faults of the business domain of the target enterprise object are monitored based on the fault handling report. The present disclosure reduces the time consumption of data processing, improves the efficiency of data processing, and can accurately obtain fault-related information.

[0042] In some embodiments, based on the risk type and business domain, the risk score and risk type corresponding to each business domain of the target enterprise object are determined, including: determining the risk score of each risk type corresponding to each business domain according to the business domain corresponding to the target enterprise object, summing the risk scores of all risk types in the business domain to obtain the risk score of each business domain of the target enterprise object.

[0043] Specifically, in daily work, in order to ensure safety, it is necessary to introduce standards and processes, and to achieve service stability, but at the same time it is also necessary to do everything possible to minimize failures. The disclosed embodiment will collect statistics on information about online failures, such as the severity of the failure, solution, severity level, and the leader of the department where the failure occurred. Based on the statistics of the failure information, a general understanding of the basic situation of the failure can be obtained.

[0044] Furthermore, when a fault occurs, the disclosed embodiment can perform statistical analysis on the completion of the fault, and can also track the actual situation of subsequent fault resolution. This can, on the one hand, increase the enthusiasm of employees to resolve faults, and on the other hand, enhance customers' trust and satisfaction with the company. In addition, in order to ensure the quality of delivery and operation, companies will set safety standards and formulate fault penalty rules, so the level will be assessed based on the quality score of each employee, which affects the performance results and, in turn, the salary level. The disclosed embodiment can statistically obtain the quality score of employees to assess performance. When company testers are testing BUGs, the disclosed embodiment implements statistical analysis of the test details.

[0045] In some embodiments, risk prevention and control information corresponding to the business domain of the target enterprise object is obtained from the distributed task platform, and online faults corresponding to the business domain are counted to obtain online fault statistical information, including: uploading the online fault information generated by the business domain to the distributed task platform, and counting the online fault information of the business domain in the distributed task platform to obtain online fault statistical information; using the data scheduling platform to synchronize the risk prevention and control information and online fault statistical information from the distributed task platform to the data warehouse, and mapping the structured information to the database table in the original data layer in the data warehouse, wherein the data warehouse adopts the Hive data warehouse.

[0046] Specifically, Hive is a data warehouse tool based on Hadoop that can map structured data files to a database table and provide SQL-like query functions. The UDF function used in Hive is a Hive-defined function. The functions that come with Hive cannot fully meet business needs. In this case, you need to use a custom function. Through the custom function, you can use different processing logic to handle different needs.

[0047] Furthermore, the present disclosure embodiment will collect statistics on the following information:

[0048] First, relevant information on risk prevention and control: including risk points and risk types of each business domain of the enterprise, business domain, service name, service level, risk type, included risks, risk points, first-level risks, second-level risks, third-level risks, third-level risk descriptions and other information.

[0049] Second, relevant information of online fault statistics: including BUG number, severity, solution, status, BUG title, BUG description, BUG operation steps, organization, problem source, creation date, assigned to / solver, expected resolution time, assigned resolution date, creation-resolution time, resolution-closure time, creation-closure time, BUG link, requirement link, BUG type, entity leader, severity level 1, severity level 2, severity level 3, severity level, detailed information of requirements raised after the fault, requirement link, requirement process, requirement classification, requirement description and other information.

[0050] Third, relevant information on fault completion statistics: including demand completion information, problem response time statistical report, demand response time statistical report, historical delayed unresolved BUG list, fault number statistics, fault number distribution, fault cause, technical risk type, fault review topic name, detailed list of team members involved in the fault, and other information.

[0051] Fourth, relevant information of quality statistical analysis (assessed by quality score): including the per capita quality score of each department, total quality score, R&D quality score, online quality score, entity leadership, P1, P2, P3, P4, P5, P1 takes more than 30 minutes to stop bleeding, P2 takes more than 30 minutes to stop bleeding, P5 takes more than three days to resolve, quality score, team size, per capita quality score, statistical cycle, detailed list of fault review topics (weekly), technical fault statistics (P5), fault behavior quality score (weekly), R&D quality score_statistical item details (weekly), R&D quality score_BUG statistics details, total quality score (weekly cumulative) and other information.

[0052] Fifth, statistical information of testers when testing bugs: including testers, number of test cases, number of valid bugs, bug number, product, level, bug status, creator, creation date, solver, solution, solution date, bug link and other information when the company's testers are testing the code.

[0053] Furthermore, the disclosed embodiment adopts the data warehouse ETL method, and by obtaining information related to faults, such as the risk points, risk types, primary risks, secondary risks, tertiary risks, and tertiary risk descriptions of various business domains of enterprises in risk prevention and control, the detailed contents of BUGs in online fault statistics and the actual situation of demand resolution, detailed information on fault completion statistics, problem response time statistics, fault number statistics and fault cause analysis, detailed information on statistical analysis related to quality points, statistical information of testers when testing BUGs, etc., this can determine the person responsible for the accident according to the cause and completion of the fault, and quickly locate the fault. For online accidents, it is necessary to do a good job of post-processing to avoid recurrence next time, reflect on the root cause, and find out the root cause of the problem. On the other hand, the evaluation of quality points is also beneficial to the year-end performance evaluation. According to each department and each member in the department, performance can be evaluated according to the occurrence of the fault, which can also improve the enthusiasm of company employees to solve fault problems and improve the company's satisfaction.

[0054] In some embodiments, the initialization information is processed into tabular data using a data warehouse, including: using a data scheduling platform to synchronize the initialization information from a distributed task platform to a data warehouse, partitioning the initialization information according to preset indicator dimensions in the original data layer of the data warehouse, and mapping the partitioned initialization information into tabular data.

[0055] Specifically, the disclosed embodiment synchronizes the acquired initialization information directly from the distributed task platform to the ODS layer in the Hive data warehouse. Hive's ODS (Operation Data Store) refers to the source data layer, which is used to store source data. It can directly load original logs and data from the MySQL database, and the data remains in its original form without any processing. In other words, the ODS layer can directly obtain the initialization information in the data scheduling platform, and can modify the table name of the structured initialization information, or it can do nothing.

[0056] In some embodiments, data cleaning and aggregation are performed on the tabular data, and the tables after data cleaning and aggregation are summarized according to preset business topics to obtain summarized tabular data, including: the original data layer passes the tabular data to the detailed data layer of the data warehouse, and in the detailed data layer, a predetermined data processing algorithm is used to clean the tabular data to remove null values, dirty data and redundant data, and aggregation operations are performed on the cleaned tabular data according to field information of the cleaned tabular data, and the aggregated tabular data are summarized according to the preset business topics to obtain summarized tabular data.

[0057] Specifically, HQL is used to perform ETL data cleaning on table data, such as removing null values, filtering meaningless data in core fields (such as system codes as NULL, etc.), desensitizing sensitive data, removing null values, dirty data and redundant data, etc. In actual applications, the ODS layer table is transferred to the DWD layer (i.e., detailed data layer) of the Hive data warehouse, and the DWD (Data Warehouse Detail) layer in Hive is used to perform data cleaning (such as removing null values ​​and dirty data, etc.) and desensitization on the table data to obtain a detailed data table.

[0058] In some embodiments, a preset reporting platform is used to query the summary table data stored in the data warehouse, including: using a data query engine installed in the reporting platform, using a data query script and pre-configured calling rules to query the summary table data stored in the data warehouse, and obtaining target table data for generating a fault handling report.

[0059] Specifically, the summary table data obtained after ETL processing is the data stored in Hive, and the report development stage is completed in the Ubiquitous Report Platform, that is, Hive is only used to store summary table data, and is not responsible for developing the final report. Therefore, it is necessary to use the Ubiquitous Report Platform to call the data in Hive for report development. The data set of the Ubiquitous Report Platform contains SQL scripts (data query scripts) for data query. The Ubiquitous Report Platform uses the Presto query engine to query the summary table data obtained after processing in the Hive data warehouse tool to obtain the target table data for developing reports, so that the Ubiquitous Report Platform can develop reports based on the target table data.

[0060] In some embodiments, a fault handling report is generated based on the queried target table data and a pre-created report configuration, and faults in the business domain of the target enterprise object are monitored based on the fault handling report, including: in a reporting platform, a report configuration is created based on a predetermined report style, and development operations are performed on the fault handling report using the report configuration and the target table data to generate a fault handling report for representing fault handling statistics, wherein the fault handling report contains relevant information on fault handling in different business domains corresponding to the target enterprise object, and fault monitoring is performed based on the relevant information on fault handling.

[0061] Specifically, before developing a report, you need to create a report configuration in advance based on the report style required by the user. The report configuration can include the report data format, arrangement method, data type, and filling rules. In actual applications, after using the Presto query engine to obtain the target table data, the report platform uses the preset report configuration and the obtained target table data to perform report development operations and generate a fault handling report so that fault monitoring can be performed using the relevant information of fault handling.

[0062] The following is a detailed description of the contents of the fault handling report generated by the embodiment of the present disclosure in conjunction with a specific embodiment. The report is developed on the ubiquitous reporting platform, and the final statistical report has a total of 41 sheets, including:

[0063] (1) Risk prevention and control:

[0064] ① Risk prevention and control test: including risk scores, risk types and other information of each business domain of the enterprise (such as AI energy saving, government platform, data-based operation, energy consumption, integrated energy management, ecology, general products, etc.).

[0065] ②Application risk details: including business domain, service name, service level, risk type, included risks, risk score and other information.

[0066] (2) Risk Knowledge Base:

[0067] Includes information such as first-level risk, second-level risk, third-level risk, and third-level risk description.

[0068] (3) Online fault statistics

[0069] ① Online fault statistics: including BUG number, severity, solution, status, BUG title, BUG description, BUG operation steps, organization, problem source, creation date, assigned to / solver, expected resolution time, assigned resolution date, creation-resolution time, resolution-closure time, creation-closure time, BUG link, requirement link, BUG type and other information.

[0070] ②Requirement list: including creation time, product name, requirement ID, bug proposer, creator, organization, requirement title, priority, assigned to, status, stage, closure reason, latest update time, creation-closure time, requirement description, requirement link, requirement process, requirement classification and other information.

[0071] (4) Operation-Response Time Statistics Report

[0072] ① Problem response time statistics report: including BUG number, severity, status, BUG description, organization, problem source, creation date, assignment / resolver, expected resolution time, solution, assignment / resolution date, unresponsive time (hours), BUG link, requirement link and other information.

[0073] ② Demand response time statistics report: including product name, demand ID, creator, organization, demand title, priority, assigned to, status, stage, closure reason, latest update time, unresponsive time (hours), demand description, demand link and other information.

[0074] (5) Quality statistical analysis

[0075] ①Quality summary (weekly)

[0076] Total quality score (weekly): includes information such as per capita quality score and total quality score of each department (such as power trading, smart IoT and products, data middle office group-algorithm platform, data middle office group-data warehouse, technology middle office group-basic platform, technology middle office group-ecological research and development, technology middle office group-middleware, front-end technology group-front-end technology group, business sharing technology group).

[0077] R&D quality score (weekly): includes information such as per capita quality score and R&D quality score of each department (such as power trading, smart IoT and products, data middle office group-algorithm platform, data middle office group-data warehouse, technology middle office group-basic platform, technology middle office group-ecological R&D, technology middle office group-middleware, front-end technology group-front-end technology group, business sharing technology group).

[0078] Online quality score (weekly): includes information such as per capita quality score and online quality score of each department (such as power trading, smart IoT and products, data middle office group-algorithm platform, data middle office group-data warehouse, technology middle office group-basic platform, technology middle office group-ecological research and development, technology middle office group-middleware, front-end technology group-front-end technology group, business sharing technology group).

[0079] ② Online quality details list (weekly):

[0080] Online quality score_Statistical item details list (weekly): including entity leader, P1, P2, P3, P4, P5, P1 exceeds 30 minutes to stop bleeding, P2 exceeds 30 minutes to stop bleeding, P5 exceeds three days without resolution, quality score, team size, average quality score per person, statistical period and other information.

[0081] Fault quality score_Fault review topic list (weekly) (details): including fault number, fault name, fault handler, emergency follow-up person, bleeding stop time, main responsible team, main responsibility ratio, severity, review time, review report, statistical period and other information.

[0082] Technical fault statistics (P5): including entity leader, product name, fault number, fault description, creator, creation time, priority, resolution / assignment to, solution, fault link and other information.

[0083] Fault action quality score (week) (details) (not included in the quality score for the time being): including task number, priority, status, creation time, completion time, deadline, timeout, responsible person, responsible team, statistical period and other information.

[0084] ③ R&D quality details (weekly):

[0085] R&D Quality Score_Statistical Item Details (Weekly): including entity leader, high-level bugs, medium-level bugs, low-level bugs, resolution time ≥5 days (high level), resolution time ≥5 days (medium level), resolution time ≥5 days (low level), number of activations, R&D quality score, per capita R&D quality score, team size, statistical period and other information.

[0086] R&D quality score_BUG statistics details: including entity leader, product name, BUG number, BUG description, creator, assigned to / solved by, severity, level, status, solution, creation date, solution date, BUG active time, number of activations, number of overdue times, quality score, BUG link, statistical period and other information.

[0087] ④Added BUGList:

[0088] Added new BUG statistics: including entity leader, severity level 1, severity level 2, severity level 3, severity level 4 and other information.

[0089] Added a detailed list of bugs: including entity leader, product name, bug number, bug, description, bug level, creator, creation time, solution / assigned to, solution, bug link and other information.

[0090] ⑤ List of historically delayed unresolved BUGs:

[0091] Includes information such as entity leader, BUG number, BUG description, BUG level, creator, creation date, resolved / assigned to, solution, BUG link, etc.

[0092] ⑥Failure statistics:

[0093] Fault count statistics: including the P1, P2, P3, and P4 fault counts summarized last week and the P1, P2, P3, and P4 fault counts summarized to date.

[0094] Fault number statistics table: includes the number of P1, P2, P3, and P4 faults summarized last week, the number of P1, P2, P3, and P4 faults summarized to date, and other information.

[0095] Distribution of the number of failures (as of now): including information such as the number of P1, P2, P3, and P4 failures summarized so far in various departments (such as power trading, smart IoT and products, data middle office group-algorithm platform, data middle office group-data warehouse, technology middle office group-basic platform, technology middle office group-ecological research and development, technology middle office group-middleware, front-end technology group-front-end technology group, and business sharing technology group).

[0096] Distribution of number of failures (weekly) (bar chart): includes information such as the number of P1, P2, P3, and P4 failures summarized last week for each department (such as power trading, smart IoT and products, data middle office group-algorithm platform, data middle office group-data warehouse, technology middle office group-basic platform, technology middle office group-ecological research and development, technology middle office group-middleware, front-end technology group-front-end technology group, and business sharing technology group).

[0097] Fault_Cause Distribution: includes the percentage of each category of fault causes (including coding issues, operation and maintenance configuration, operation configuration, JOB execution, upstream and downstream dependencies, product design, security issues, performance capacity, architecture design, process communication, and third parties).

[0098] Technical risk types: including the percentage of each type of technical risk (including reliability-availability, reliability-fault tolerance, performance efficiency, ease of use, compatibility, functional characteristics, etc.) and other information.

[0099] Fault review topic list: including serial number, topic name, review meeting date, fault level, responsible team, link and other information.

[0100] Team personnel details: including serial number, department name, team size, time and other information.

[0101] (6) Quality review (test)

[0102] ①Total quality score (weekly cumulative): including the total quality score (weekly cumulative) to date and other information.

[0103] ② R&D quality score test (week) (bar chart): includes information such as the average capabilities and total R&D quality score of each department (such as power trading, smart IoT and products, data middle platform group-algorithm platform, data middle platform group-data warehouse, technology middle platform group-basic platform, technology middle platform group-ecological R&D, technology middle platform group-middleware, front-end technology group-front-end technology group, business sharing technology group).

[0104] (7) Test self-driving

[0105] ① Test BUG_CASE Statistics - Test BUG_CASE Statistics (bar chart): includes information such as the number of test cases and the number of valid bugs when the company's testers test the code.

[0106] ②Test BUG_CASE statistics: including testers, number of valid bugs, number of test cases and other information.

[0107] ③ Invalid BUG confirmation: including BUG number, product, level, BUG status, creator, creation date, solver, solution, solution date, BUG link and other information.

[0108] (8) Online fault statistics:

[0109] It includes BUG number, severity, status, BUG description, organization, problem source, creation date, person assigned to / solved, expected resolution time, resolution method, assignment / resolution date, creation-resolution time, resolution-closure time, creation-closure time, BUG link, requirement link and other information.

[0110] (9) Requirements list: including product name, requirement ID, creator, organization, requirement title, priority, assigned to, status, stage, closing reason, creation time, latest update time, creation-closing time, requirement description, requirement link and other information.

[0111] (10) Requirements: including organization, creator, requirement ID, requirement title, status, stage, assigned to, creation time, etc.

[0112] (11) Data statistics: including organizational structure, number of demands, resolved demands, unresolved demands, etc.

[0113] (12) Unresolved defects

[0114] ① Unresolved demands - data statistics: including information such as organizational structure, number of demands, resolved demands, and unresolved demands.

[0115] ②Unresolved Demands-Unresolved Demand Statistics: Displays detailed information of unresolved demands.

[0116] (13)testDB

[0117] ① Requirement status: including organization, creator, requirement ID, requirement title, status, stage, assigned to, creation time and other information.

[0118] ②Data statistics: including organizational structure, number of demands, resolved demands, unresolved demands and other information.

[0119] (14) Statistics of detailed requirements information: including organization name, total number of requirements, number of resolved requirements, number of unresolved requirements, waiting requirements, planned requirements, approved requirements, requirements under development, requirements completed in R&D, requirements under testing, requirements completed in testing, released requirements, verified requirements, etc.

[0120] 4. After the results are displayed according to the report, they can be used for large-screen display, which is also convenient for data statistical analysis or leadership decision-making.

[0121] The following are embodiments of the device disclosed herein, which can be used to execute the method embodiments disclosed herein. For details not disclosed in the device embodiments disclosed herein, please refer to the method embodiments disclosed herein.

[0122] Figure 2 Schematic diagram of the structure of the fault handling device based on report development provided by the embodiment of the present disclosure. Figure 2 As shown, the fault handling device developed based on the report includes:

[0123] The determination module 201 is configured to group the preset risk types and determine the business domains, and determine the risk points and risk types corresponding to each business domain of the target enterprise object based on the risk types and business domains;

[0124] The acquisition module 202 is configured to acquire risk prevention and control information corresponding to the business domain of the target enterprise object from the distributed task platform, and to count online faults corresponding to the business domain to obtain online fault statistical information, and to count fault completion status according to the online faults to obtain fault completion status statistical information;

[0125] The statistical module 203 is configured to perform statistics on the total quality score, R&D quality score, online quality score and fault quality score of the target enterprise object according to a pre-configured quality score statistical method, and determine the quality score statistical information corresponding to the target enterprise object according to the statistical results;

[0126] The synchronization module 204 is configured to obtain the test information generated by the tester when the test failure occurs, perform statistics on the test information to obtain test failure statistics information, use the risk prevention and control information, online failure statistics information, failure completion statistics information, quality score statistics information and test failure statistics information as initialization information, and synchronize the initialization information to the data warehouse;

[0127] The processing module 205 is configured to process the initialization information into table data by using the data warehouse, clean and aggregate the table data, and summarize the cleaned and aggregated tables according to preset business themes to obtain summarized table data;

[0128] The generation module 206 is configured to use a preset reporting platform to query the summary table data stored in the data warehouse, generate a fault handling report based on the queried target table data and a pre-created report configuration, and monitor the faults of the business domain of the target enterprise object based on the fault handling report.

[0129] In some embodiments, Figure 2 The determination module 201 determines the risk score of each risk type corresponding to each business domain according to the business domain corresponding to the target enterprise object, and sums the risk scores of all risk types in the business domain to obtain the risk score of each business domain of the target enterprise object.

[0130] In some embodiments, Figure 2 The acquisition module 202 uploads the online fault information generated by the business domain to the distributed task platform, and counts the online fault information of the business domain in the distributed task platform to obtain online fault statistical information; uses the data scheduling platform to synchronize the risk prevention and control information and online fault statistical information from the distributed task platform to the data warehouse, and maps the structured information to the database table in the original data layer in the data warehouse, where the data warehouse adopts the Hive data warehouse.

[0131] In some embodiments, Figure 2 The processing module 205 uses the data scheduling platform to synchronize the initialization information from the distributed task platform to the data warehouse, partitions the initialization information according to preset indicator dimensions in the original data layer of the data warehouse, and maps the partitioned initialization information into table data.

[0132] In some embodiments, Figure 2 The processing module 205 passes the table data to the detailed data layer of the data warehouse. In the detailed data layer, a predetermined data processing algorithm is used to clean the table data to remove null values, dirty data and redundant data. According to the field information of the cleaned table data, an aggregation operation is performed on the cleaned table data, and the aggregated table data is summarized according to the preset business theme to obtain summarized table data.

[0133] In some embodiments, Figure 2 The generation module 206 uses the data query engine installed in the report platform, the data query script and the pre-configured calling rules to query the summary table data stored in the data warehouse, and obtains the target table data for generating the fault handling report.

[0134] In some embodiments, Figure 2The generation module 206 creates a report configuration based on a predetermined report style in the report platform, and uses the report configuration and the target table data to perform development operations on the fault handling report to generate a fault handling report for representing fault handling statistics. The fault handling report contains relevant information on fault handling of different business domains corresponding to the target enterprise object, and fault monitoring is performed based on the relevant information on fault handling.

[0135] It should be understood that the size of the serial numbers of the steps in the above embodiments does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present disclosure.

[0136] Figure 3 Schematic diagram of the structure of the electronic device 3 provided in the embodiment of the present disclosure. Figure 3 As shown, the electronic device 3 of this embodiment includes: a processor 301, a memory 302, and a computer program 303 stored in the memory 302 and executable on the processor 301. When the processor 301 executes the computer program 303, the steps in the above-mentioned method embodiments are implemented. Alternatively, when the processor 301 executes the computer program 303, the functions of the modules / units in the above-mentioned device embodiments are implemented.

[0137] Exemplarily, the computer program 303 may be divided into one or more modules / units, which are stored in the memory 302 and executed by the processor 301 to complete the present disclosure. The one or more modules / units may be a series of computer program instruction segments capable of completing specific functions, which are used to describe the execution process of the computer program 303 in the electronic device 3.

[0138] The electronic device 3 may be a desktop computer, a notebook, a PDA, a cloud server, or other electronic device. The electronic device 3 may include, but is not limited to, a processor 301 and a memory 302. Those skilled in the art will appreciate that Figure 3 It is only an example of the electronic device 3 and does not constitute a limitation of the electronic device 3. It may include more or fewer components than shown in the figure, or a combination of certain components, or different components. For example, the electronic device may also include input and output devices, network access devices, buses, etc.

[0139] The processor 301 may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.

[0140] The memory 302 may be an internal storage unit of the electronic device 3, for example, a hard disk or memory of the electronic device 3. The memory 302 may also be an external storage device of the electronic device 3, for example, a plug-in hard disk, a smart media card (SMC), a secure digital (SD) card, a flash card, etc. equipped on the electronic device 3. Further, the memory 302 may also include both an internal storage unit and an external storage device of the electronic device 3. The memory 302 is used to store computer programs and other programs and data required by the electronic device. The memory 302 may also be used to temporarily store data that has been output or is to be output.

[0141] The technicians in the relevant field can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional units and modules is used as an example for illustration. In practical applications, the above-mentioned function allocation can be completed by different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiment can be integrated in a processing unit, or each unit can exist physically separately, or two or more units can be integrated in one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of software functional units. In addition, the specific names of the functional units and modules are only for the convenience of distinguishing each other, and are not used to limit the scope of protection of this application. The specific working process of the units and modules in the above-mentioned system can refer to the corresponding process in the aforementioned method embodiment, which will not be repeated here.

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

[0143] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this disclosure.

[0144] In the embodiments provided in the present disclosure, it should be understood that the disclosed apparatus / computer equipment and methods can be implemented in other ways. For example, the apparatus / computer equipment embodiments described above are merely schematic. For example, the division of modules or units is only a logical function division. There may be other division methods in actual implementation. Multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, indirect coupling or communication connection of the apparatus or unit, which may be electrical, mechanical or other forms.

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

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

[0147] If the integrated module / unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the present disclosure implements all or part of the processes in the above-mentioned embodiment method, and can also be completed by instructing the relevant hardware through a computer program. The computer program can be stored in a computer-readable storage medium, and the computer program can implement the steps of the above-mentioned various method embodiments when executed by the processor. The computer program may include computer program code, and the computer program code may be in source code form, object code form, executable file or some intermediate form. The computer-readable medium may include: any entity or device capable of carrying computer program code, recording medium, U disk, mobile hard disk, magnetic disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electric carrier signal, telecommunication signal and software distribution medium. It should be noted that the content contained in the computer-readable medium can be appropriately increased or decreased according to the requirements of legislation and patent practice in the jurisdiction. For example, in some jurisdictions, according to legislation and patent practice, the computer-readable medium does not include electric carrier signals and telecommunication signals.

[0148] The above embodiments are only used to illustrate the technical solutions of the present disclosure, rather than to limit them. Although the present disclosure has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. These modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present disclosure, and should all be included in the protection scope of the present disclosure.

Claims

1. A fault handling method based on report development, characterized in that: include: The preset risk types are grouped and business domains are determined, and based on the risk types and business domains, the risk points and risk types corresponding to the business domains of the target enterprise object are determined; Obtain risk prevention and control information corresponding to the business domain of the target enterprise object from the distributed task platform, and count online faults corresponding to the business domain to obtain online fault statistical information, and count fault completion status according to the online faults to obtain fault completion status statistical information; According to a pre-configured quality score statistical method, the total quality score, R&D quality score, online quality score and fault quality score of the target enterprise object are counted, and the quality score statistical information corresponding to the target enterprise object is determined according to the statistical results; Acquire the test information generated by the tester when testing a failure, perform statistics on the test information to obtain test failure statistical information, use the risk prevention and control information, the online failure statistical information, the failure completion status statistical information, the quality score statistical information and the test failure statistical information as initialization information, and synchronize the initialization information to the data warehouse; Using the data warehouse to process the initialization information into tabular data, and performing data cleaning and aggregation on the tabular data, and summarizing the tables after data cleaning and aggregation according to preset business topics to obtain summarized tabular data; The summary table data stored in the data warehouse is queried using a preset reporting platform, a fault handling report is generated based on the queried target table data and a pre-created report configuration, and faults in the business domain of the target enterprise object are monitored based on the fault handling report.

2. The method according to claim 1, characterized in that The step of determining the risk score and risk type corresponding to each business domain of the target enterprise object based on the risk type and the business domain includes: According to the business domain corresponding to the target enterprise object, the risk score of each risk type corresponding to each business domain is determined, and the risk scores of all the risk types in the business domain are summed to obtain the risk score of each business domain of the target enterprise object.

3. The method according to claim 1, characterized in that The step of acquiring risk prevention and control information corresponding to the business domain of the target enterprise object from the distributed task platform, and performing statistics on online faults corresponding to the business domain to obtain online fault statistical information includes: Uploading the online fault information generated by the business domain to the distributed task platform, and collecting statistics on the online fault information of the business domain in the distributed task platform to obtain the online fault statistical information; The risk prevention and control information and the online fault statistics information are synchronized from the distributed task platform to the data warehouse using a data scheduling platform, and the structured information is mapped to a database table in the original data layer in the data warehouse, wherein the data warehouse adopts a Hive data warehouse.

4. The method according to claim 3, characterized in that The using the data warehouse to process the initialization information into tabular data includes: The data scheduling platform is used to synchronize the initialization information from the distributed task platform to the data warehouse, the initialization information is partitioned according to preset indicator dimensions in the original data layer of the data warehouse, and the partitioned initialization information is mapped into tabular data.

5. The method according to claim 1, characterized in that The data cleaning and aggregation of the table data, and summarizing the cleaned and aggregated tables according to preset business topics to obtain summarized table data, include: The original data layer passes the table data to the detailed data layer of the data warehouse. In the detailed data layer, a predetermined data processing algorithm is used to clean the table data to remove null values, dirty data and redundant data. An aggregation operation is performed on the cleaned table data based on the field information of the cleaned table data, and the aggregated table data is summarized according to the preset business theme to obtain the summarized table data.

6. The method according to claim 1, characterized in that The querying of the summary table data stored in the data warehouse by using a preset report platform includes: The data query engine installed in the report platform is used to query the summary table data stored in the data warehouse using the data query script and pre-configured calling rules to obtain the target table data used to generate the fault handling report.

7. The method according to claim 1, characterized in that The generating of a fault handling report based on the queried target table data and the pre-created report configuration, and monitoring the faults of the business domain of the target enterprise object based on the fault handling report, includes: In the reporting platform, the report configuration is created based on a predetermined report style, and the report configuration and the target table data are used to perform development operations on the fault handling report to generate the fault handling report for representing fault handling statistics. The fault handling report contains relevant information on fault handling of different business domains corresponding to the target enterprise object, and fault monitoring is performed based on the relevant information on fault handling.

8. A fault handling device based on report development, characterized in that: include: A determination module is configured to group preset risk types and determine business domains, and based on the risk types and business domains, determine the risk points and risk types corresponding to each business domain of the target enterprise object; an acquisition module configured to acquire risk prevention and control information corresponding to the business domain of the target enterprise object from the distributed task platform, and to count online faults corresponding to the business domain to obtain online fault statistical information, and to count fault completion status according to the online faults to obtain fault completion status statistical information; A statistical module is configured to perform statistics on the total quality score, R&D quality score, online quality score and fault quality score of the target enterprise object according to a pre-configured quality score statistical method, and determine the quality score statistical information corresponding to the target enterprise object according to the statistical results; A synchronization module is configured to obtain test information generated by a tester when a test failure occurs, perform statistics on the test information to obtain test failure statistics information, use the risk prevention and control information, the online failure statistics information, the failure completion status statistics information, the quality score statistics information and the test failure statistics information as initialization information, and synchronize the initialization information to a data warehouse; a processing module configured to process the initialization information into tabular data by using the data warehouse, and to perform data cleaning and aggregation on the tabular data, and to summarize the tables after data cleaning and aggregation according to preset business themes to obtain summarized tabular data; The generation module is configured to use a preset reporting platform to query the summary table data stored in the data warehouse, generate a fault handling report based on the queried target table data and a pre-created report configuration, and monitor the faults of the business domain of the target enterprise object based on the fault handling report.

9. An electronic device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, wherein the processor implements the method according to any one of claims 1 to 7 when executing the program.

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