WO2019200750A1 - 报表监控方法、装置、计算机设备和存储介质 - Google Patents

报表监控方法、装置、计算机设备和存储介质 Download PDF

Info

Publication number
WO2019200750A1
WO2019200750A1 PCT/CN2018/095500 CN2018095500W WO2019200750A1 WO 2019200750 A1 WO2019200750 A1 WO 2019200750A1 CN 2018095500 W CN2018095500 W CN 2018095500W WO 2019200750 A1 WO2019200750 A1 WO 2019200750A1
Authority
WO
WIPO (PCT)
Prior art keywords
report
monitoring
status
information
feedback information
Prior art date
Application number
PCT/CN2018/095500
Other languages
English (en)
French (fr)
Inventor
钟宇料
宋剑锋
王佛清
Original Assignee
平安科技（深圳）有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 平安科技（深圳）有限公司 filed Critical 平安科技（深圳）有限公司
Publication of WO2019200750A1 publication Critical patent/WO2019200750A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/32—Monitoring with visual or acoustical indication of the functioning of the machine
    • G06F11/324—Display of status information
    • G06F11/327—Alarm or error message display
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0681—Configuration of triggering conditions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/06—Generation of reports

Definitions

  • the present application relates to the field of computer applications, and in particular, to a report monitoring method, apparatus, computer device, and storage medium.
  • Network management includes monitoring the behavior and content of logging in to the Internet, that is, Internet monitoring or external network monitoring; also includes intranet monitoring or local network monitoring; existing monitoring tools do not support asynchronous loading type report monitoring, and the existing monitoring tool database is not It has been widely promoted and applied, and the automation process is low. It still needs manual intervention. For example, personnel need to log in to browse reports, and manually switch the monitoring process, which consumes a lot of manpower, material resources and financial resources. The progress of monitoring process is low, and human error is easy to occur.
  • the main purpose of the present application is to provide a report monitoring method, which aims to solve the technical problem that the existing monitoring tool does not support the asynchronous monitoring type of report monitoring.
  • the present application proposes a report monitoring method, including:
  • the target keyword is not carried, it is determined that the monitoring status is monitoring failure.
  • the application also provides a report monitoring device, comprising:
  • the asynchronous waiting module is used for asynchronously waiting for the feedback information of the report in the monitoring state after the data loading is completed;
  • a first determining module configured to determine that the monitoring status is a monitoring failure if the feedback information is not received
  • An analysis module configured to: if the feedback information is received, analyze whether the feedback information carries a preset target keyword;
  • a second determining module configured to: if the target keyword is carried, determine that the monitoring status is that the monitoring is successful;
  • the third determining module is configured to determine that the monitoring status is monitoring failure if the target keyword is not carried.
  • the application also provides a computer device comprising a memory and a processor, the memory storing computer readable instructions, the processor implementing the steps of the method when the computer readable instructions are executed.
  • the present application also provides a computer non-transitory readable storage medium having stored thereon computer readable instructions that, when executed by a processor, implement the steps of the methods described above.
  • the present invention has the beneficial technical effects: the present invention realizes the automatic monitoring of the asynchronous loading type by asynchronously waiting for the target keyword, improves the monitoring efficiency, the process, the accuracy, and especially the monitoring of the Cognos report type, and makes up for the defects of the prior art. It has practical application value; this application realizes the automation of the whole monitoring process by simulating the way users browse reports, automatically identify the reports to be monitored, and automatically report abnormal reports, without personnel intervention, reducing monitoring costs and improving the effectiveness of monitoring; Through the automatic alarm exception report, and feedback the exception type, provide useful reference information for the reanalysis and reuse of the database, and further promote the application coverage of the automatic monitoring process.
  • FIG. 1 is a schematic flow chart of a report monitoring method according to an embodiment of the present application.
  • FIG. 2 is a schematic structural diagram of a report monitoring apparatus according to an embodiment of the present application.
  • FIG. 3 is a schematic diagram of an optimized structure of a report monitoring apparatus according to an embodiment of the present application.
  • FIG. 4 is a schematic structural diagram of an apparatus for determining a module according to an embodiment of the present application.
  • FIG. 5 is a schematic diagram of a re-optimization structure of a report monitoring apparatus according to an embodiment of the present application.
  • FIG. 6 is a schematic structural diagram of a report monitoring apparatus according to another embodiment of the present application.
  • FIG. 7 is a schematic diagram of an optimized structure of a report monitoring apparatus according to another embodiment of the present application.
  • FIG. 8 is a schematic structural diagram of a report monitoring apparatus according to still another embodiment of the present application.
  • FIG. 9 is a schematic structural diagram of a classification module according to an embodiment of the present application.
  • FIG. 10 is a schematic structural diagram of a classification module according to still another embodiment of the present application.
  • FIG. 11 is a schematic diagram showing the internal structure of a computer device according to an embodiment of the present application.
  • a report monitoring method includes:
  • S1 The feedback information of the report that is asynchronously waiting for the monitoring state after the data loading is completed.
  • Asynchronous in this step refers to the mechanism of the monitored object.
  • the browser loading items have an order. After waiting for the loading item to complete, the returned content is detected.
  • the asynchronous in this embodiment is that the report page is loaded after the data is completed.
  • AJAX Asynchronous Javascript And XML, asynchronous JavaScript and XML, is a mechanism for creating web development techniques for interactive web applications to request other core content, such as detail data.
  • the report in this embodiment is an asynchronous load type report, such as a Cognos report type. For example, the report frame is loaded first, and then the report data content is loaded asynchronously.
  • the Cognos of this embodiment is a service-oriented data model on the core platform.
  • Cognos business intelligence solutions can be easily integrated into existing multi-system and data source architectures.
  • Cognos reports are based on a unified metadata model that provides a unified view of applications. Users can customize reports in browsers and format flexible elements.
  • Rich and Queryable Studio (a powerful database query build control) for timely and open queries, Cognos report production and display can be achieved through a pure web interface, so that deployment costs and management costs are minimized, but the asynchronous load type of report lacks real-time The real-time status monitoring cannot be performed, which is not conducive to controlling whether the loading data status of the report is normal.
  • the report is not in the monitoring state, or the automatic monitoring system does not have a matching connection relationship with the monitored report, and the monitoring fails.
  • the target keyword in this step includes the label keyword of the tree menu formed on the page after the loading data status of the report is loaded.
  • the target keyword of other embodiments of the present application may also be other identifiers or contents preset by the user. .
  • the report loading data state is loaded successfully, and the monitoring may be performed.
  • the monitoring target keyword indirectly monitors whether the asynchronous loading type report loading data state is in a normal state.
  • the asynchronous monitoring type web monitoring is implemented by asynchronously waiting for the target keyword, which makes up for the technical loophole that the asynchronous loading type of the Web cannot be automatically monitored in the existing industry.
  • Asynchronous loading is non-blocking loading. When the browser downloads, it will continue to parse the subsequent pages.
  • asynchronous monitoring type is automatically monitored by asynchronously waiting for the target keyword, thereby improving monitoring efficiency, process, and accuracy, especially the monitoring of the Cognos report type, and making up for the defect that the asynchronous loading type report cannot be monitored. Practical application value.
  • the monitoring status in this embodiment includes two states: monitoring failure and monitoring success.
  • the monitoring fails, so as to promptly remind the manual to participate in the operation, and timely Check whether the report loading data status is abnormal.
  • the other embodiments of the present application automatically start the report repairing and adjusting mechanism after the report monitoring fails, so as to clear the monitoring obstacles in time, and the report monitoring process is smoothly performed.
  • step S1 the method includes:
  • the status information in this step is generated by the model refresh program, that is, the data is reloaded by the model refresh.
  • the report of this embodiment relies on the report loading data, and the report loading data depends on the model refresh.
  • the status information includes six states of the model refresh, waiting for refresh -> refresh -> refresh exception -> complete refresh -> release -> release completion.
  • the model is refreshed and released for the whole process.
  • the completion of the release indicates that the corresponding report has data loading and updating.
  • the report that updates the loading data is the report that needs to be monitored.
  • the update status of the report loading data is automatically released according to the release status.
  • the update status of the loaded data lists the list of reports that need to be monitored in order to automatically enter the monitoring system.
  • step S10 The process of determining the list of reports to be monitored in this embodiment is as follows, that is, step S10, including:
  • S101 Receive status information that is sent by the first report after the model is refreshed.
  • the status information of this step is one of the six states as described above, and the receiving mode may be a textual expression such as a refresh exception, or a preset corresponding specified code information, such as a display code of 'HTTP404 error' when the exception is refreshed. Wait.
  • S102 Determine whether the state information of the model refresh of the first report is the completion of the release.
  • the received status information is identified and analyzed by means of character recognition or character recognition.
  • the character recognition or character recognition in this embodiment is identified by a template comparison method, and the character or character is segmented and the feature parameters are extracted, and then the extracted feature parameters are compared with the pre-stored instructions in the template to release the completed text or character features.
  • the comparison determines a certain character or character that matches the template according to the similarity. If the matching is successful, the status information is the completion of the publication, otherwise the unpublished is completed. For example, by determining whether the similarity reaches a preset threshold, if it is reached, it indicates that the text or character of the received status information is consistent with a certain character or character of the template.
  • This step only determines that the report is in the updated state of the loaded data when the received status information is completed, and then determines that the report needs to be monitored, and triggers the automatic monitoring system to monitor the report. Any of the above six status information except the release completion will not trigger the automatic monitoring system.
  • step S10 of the embodiment the method includes:
  • This embodiment automatically opens the browser by simulating user behavior to increase the automation of the monitoring process.
  • the browser of this embodiment includes a browser of IE6 or higher.
  • S105 Perform login authentication on the login page of the browser.
  • the embodiment After automatically logging in to the browser page, the embodiment automatically enters the user name and password, simulates the manner in which the user browses the report, and automatically accesses the report data of the report in the monitored state, so as to further improve the automation of the monitoring process, without manual participation, and Browse more frequently and browse more comprehensive data.
  • the manual click is limited by the action frequency of the manual operation, and the click access rate is too small.
  • the access mode of the high frequency and big data can be set, the coverage of the access data is improved, and the access is obtained.
  • the data is more comprehensive and reliable, and it can expose the monitoring abnormal data of the report.
  • the process of accessing the report in this embodiment is a process of browsing the report data and browsing the monitoring status data of the report, so as to timely discover the report abnormality.
  • the process of accessing the report in this embodiment by simulating the manner in which the user browses the report, automatically identifies the report to be monitored, and automatically reports the abnormal report, the automatic operation of the entire monitoring process is realized, no personnel intervention is required, the monitoring cost is reduced, and the monitoring effectiveness is improved.
  • step S4 of the embodiment the method includes:
  • This implementation writes the report and monitoring data that are successfully monitored into the database, so that it can be directly included in the automatic monitoring system when the report is used later, eliminating the need for monitoring and testing again, saving costs.
  • step S2 or S5 the method further includes:
  • an alarm mechanism when the monitoring status is monitoring failure, an alarm mechanism is triggered, and an abnormal alarm report is automatically issued to remind the staff to check in time to improve the monitoring efficiency.
  • the alarm mechanism of the embodiment includes that when the feedback information is received or the corresponding preset target keyword is not received in the specified time period, the sound alarm is triggered, or the monitoring failure state is sent while the sound alarm is sounded. Information to the designated staff in order to cause staff to pay attention to and deal with in a timely manner.
  • the other embodiments of the present application may further refine the display manner of the alarm mechanism according to the two conditions of receiving the feedback information or the received feedback information in the specified time period, so that the relevant staff can Different alarm display modes can quickly determine the abnormal cause of report monitoring and improve the efficiency of releasing the abnormal state of report monitoring.
  • the report information displayed in this embodiment includes the name of the abnormal report, the detection time, the corresponding monitoring model, and the access status, so that the staff or the mechanism for automatically repairing and adjusting the report can accurately grasp the monitoring status in time and provide a timely response plan.
  • the display manner of this embodiment includes sending text information or audio information to a designated person in charge to operate the page, or displaying the text information or audio information through a designated display screen.
  • step S22 the method includes:
  • the monitoring status of the monitoring failure is written into the database, so that the mechanism for repairing and adjusting the report by manual or automatic later is formed, and the prioritized database of the fault cancellation is formed by the strategy scheme for releasing the monitoring failure, so as to encounter and aprior in the later stage.
  • the corresponding policy plan is retrieved in time to improve the timeliness and pertinence of the monitoring failure of the monitoring failure state, which is more conducive to promoting the application scope of the automatic monitoring process.
  • step S23 the method includes:
  • S24 classify the report of the database according to the monitoring status.
  • the monitoring status in this embodiment includes two states: monitoring failure and monitoring success.
  • the report monitoring data is effectively managed.
  • the monitoring success status after the monitoring failure report is removed.
  • the report is directly incorporated into the automatic monitoring system to reduce the workload of the staff; on the other hand, it is convenient to analyze the data for the reasons of monitoring failure and obtain effective experience in releasing the monitoring fault.
  • step S24 of the embodiment includes:
  • the first report data suitable for automatic monitoring is formed by integrating the report whose monitoring status is successfully monitored into the same directory.
  • the report successfully recorded in the database is classified into the first report data, so as to further improve the validity and pertinence of the data retrieved from the database in the automatic monitoring process, and also facilitate further automatic monitoring according to the database.
  • the report information of the report enables effective promotion and application automatic monitoring process.
  • the automated monitoring process is applied to the security management area of report data.
  • the access level of the target data and the countermeasures are preset in advance. Permissions for different users can only access low-level report data. If the user with low access rights is over-authorized, the monitoring process is executed according to the preset countermeasures, thereby preventing the current user from accessing the illegal report and information; and automatically writing the unauthorized access exception to the database and issuing the abnormal information message to prevent the user from accessing the report.
  • the automatic monitoring process can upgrade the monitoring level, strengthen the process supervision of the access user, or send the abnormal access to the report data person by SMS to ensure the security of the data in the report system. Sex.
  • the automated monitoring process is applied to the management of audit report data.
  • the automatic monitoring process of this embodiment stores the correct and error states generated in the process database during the process of monitoring the reporting system process, so as to provide a data foundation for the auditors in the process of system auditing and security auditing.
  • step S24 includes:
  • the report information of the failed report is summarized, so as to analyze the cause of the monitoring failure and improve the analysis efficiency.
  • the second report data in this embodiment includes, but is not limited to, the name of the abnormal report, the detection time, the corresponding monitoring model, the access status, the cause of the abnormality, the exception policy, the abnormal duration, and the like.
  • Step S241 may further include:
  • the reason for the monitoring failure in this embodiment includes, but is not limited to, loading failure, loading failure, network failure, loading file interruption, report page configuration and monitoring process mismatch, and the like.
  • the loading failure is caused by the loading file corruption, and the file repair display is not repairable.
  • the possibility of filtering into the automatic monitoring system is excluded. If the file repair shows repairable, the file is repaired again. After the system is automatically monitored and the possibility of being successfully monitored, the report screening the repair file enters the queue for the test to be monitored again.
  • step S243 the method includes:
  • the reason for the failure of the monitoring is that the page configuration of the report does not match the monitoring process, you need to adjust the matching information of the report page to improve the success rate of the report that was successfully monitored after the report that failed the monitoring again enters the automatic monitoring process again.
  • the network status is restored to normal. If the data is restored to normal, the report that has been interrupted due to the network failure and the monitoring failure will enter the automatic monitoring process again. To conduct secondary monitoring and testing to improve the number of monitoring reports in the automatic monitoring process and improve the application coverage of the automatic monitoring process.
  • the present invention realizes the automatic monitoring of the asynchronous loading type by asynchronously waiting for the target keyword, improves the monitoring efficiency, the process, the accuracy, and especially the monitoring of the Cognos report type, and makes up for the defects of the prior art, and has practical application value; Applying to simulate the user to browse the report, automatically identify the report to be monitored, and automatically report the abnormal report, realize the automation of the entire monitoring process, without personnel intervention, reduce the monitoring cost, and improve the effectiveness of monitoring; this application passes the automatic alarm exception report. And feedback the anomaly type, provide useful reference information for the reanalysis and reuse of the database, and further promote the application coverage of the automatic monitoring process.
  • a report monitoring apparatus includes:
  • the asynchronous waiting module 1 is used for asynchronously waiting for the feedback information of the report in the monitoring state after the data loading is completed.
  • Asynchronous in this embodiment refers to the mechanism of the monitored object, for example, the browser loading item has an order, and waits for the loading item to complete to detect the returned content.
  • the asynchronous in this embodiment is after the report page finishes loading the data, and
  • AJAX Asynchronous Javascript And XML, asynchronous JavaScript and XML, is a mechanism for creating web development techniques for interactive web applications to request other core content, such as detail data.
  • the report in this embodiment is an asynchronous load type report, such as a Cognos report type. For example, the report frame is loaded first, and then the report data content is loaded asynchronously.
  • the Cognos of this embodiment is a service-oriented data model on the core platform.
  • Cognos business intelligence solutions can be easily integrated into existing multi-system and data source architectures.
  • Cognos reports are based on a unified metadata model that provides a unified view of applications. Users can customize reports in browsers and format flexible elements.
  • Rich and Queryable Studio (a powerful database query build control) for timely and open queries, Cognos report production and display can be achieved through a pure web interface, so that deployment costs and management costs are minimized, but the asynchronous load type of report lacks real-time The real-time status monitoring cannot be performed, which is not conducive to controlling whether the loading data status of the report is normal.
  • the first determining module 2 is configured to determine that the monitoring status is monitoring failure if the feedback information is not received.
  • the report is not in the monitoring state, or the automatic monitoring system does not have a matching connection relationship with the monitored report, and the monitoring fails.
  • the analyzing module 3 is configured to analyze whether the feedback information carries a preset target keyword if the feedback information is received.
  • the target keyword in this embodiment includes the label keyword of the tree menu formed on the loading page after the loading data status is loaded.
  • the target keyword in other embodiments of the present application may also be other identifiers preset by the user or content.
  • the report loading data state is loaded successfully, and the monitoring may be performed.
  • the monitoring target keyword indirectly monitors whether the asynchronous loading type report loading data state is in a normal state.
  • the asynchronous monitoring type web monitoring is implemented by asynchronously waiting for the target keyword, which makes up for the technical loophole that the asynchronous loading type of the Web cannot be automatically monitored in the existing industry.
  • Asynchronous loading is non-blocking loading. When the browser downloads, it will continue to parse the subsequent pages.
  • asynchronous monitoring type is automatically monitored by asynchronously waiting for the target keyword, thereby improving monitoring efficiency, process, and accuracy, especially the monitoring of the Cognos report type, and making up for the defect that the asynchronous loading type report cannot be monitored. Practical application value.
  • the second determining module 4 is configured to determine that the monitoring status is successful if the target keyword is carried.
  • the third determining module 5 is configured to determine that the monitoring status is monitoring failure if the target keyword is not carried.
  • the monitoring status in this embodiment includes two states: monitoring failure and monitoring success.
  • the monitoring fails, so as to promptly remind the manual to participate in the operation, and timely Check whether the report loading data status is abnormal.
  • the other embodiments of the present application automatically start the report repairing and adjusting mechanism after the report monitoring fails, so as to clear the monitoring obstacles in time, and the report monitoring process is smoothly performed.
  • the report monitoring apparatus of this embodiment includes:
  • the determining module 10 is configured to determine a report that needs to be monitored according to the state information of the model refresh of each report.
  • the state information in this embodiment is generated by the model refresh program, that is, the data is reloaded by the model refresh.
  • the report of this embodiment relies on the report loading data, and the report loading data depends on the model refresh.
  • the status information includes six states of the model refresh, waiting for refresh -> refresh -> refresh exception -> complete refresh -> release -> release completion.
  • the model is refreshed and released for the whole process.
  • the completion of the release indicates that the corresponding report has data loading and updating.
  • the report that updates the loading data is the report that needs to be monitored.
  • the update status of the report loading data is automatically released according to the release status.
  • the update status of the loaded data lists the list of reports that need to be monitored in order to automatically enter the monitoring system.
  • the determining module 10 of this embodiment includes:
  • the receiving unit 101 is configured to receive status information that is sent by the first report after the model is refreshed.
  • the status information of this embodiment is one of the six states as described above, and the receiving manner may be a textual expression such as a refresh exception, or a preset corresponding specified code information, such as a display code of 'HTTP404 error when refreshing an exception. 'Wait.
  • the determining unit 102 is configured to determine whether the state information of the model refresh of the first report is the completion of the release.
  • the received status information is identified and analyzed by means of character recognition or character recognition.
  • the character recognition or character recognition in this embodiment is identified by a template comparison method, and the character or character is segmented and the feature parameters are extracted, and then the extracted feature parameters are compared with the pre-stored instructions in the template to release the completed text or character features.
  • the comparison determines a certain character or character that matches the template according to the similarity. If the matching is successful, the status information is the completion of the publication, otherwise the unpublished is completed. For example, by determining whether the similarity reaches a preset threshold, if it is reached, it indicates that the text or character of the received status information is consistent with a certain character or character of the template.
  • the determining unit 103 is configured to determine that the first report is a report that needs to be monitored if the publishing is completed.
  • the report is determined to be in the updated state of the loaded data, and then it is determined that the report needs to be monitored, and the automatic monitoring system is triggered to monitor the report. Any of the above six status information except the release completion will not trigger the automatic monitoring system.
  • the report monitoring apparatus of this embodiment includes:
  • the startup module 104 is configured to automatically launch the browser.
  • This embodiment automatically opens the browser by simulating user behavior to increase the automation of the monitoring process.
  • the browser of this embodiment includes a browser of IE6 or higher.
  • the login module 105 is configured to perform login authentication on the login page of the browser.
  • the embodiment After automatically logging in to the browser page, the embodiment automatically enters the user name and password, simulates the manner in which the user browses the report, and automatically accesses the report data of the report in the monitored state, so as to further improve the automation of the monitoring process, without manual participation, and Browse more frequently and browse more comprehensive data.
  • the manual click is limited by the action frequency of the manual operation, and the click access rate is too small.
  • the access mode of the high frequency and big data can be set, the coverage of the access data is improved, and the access is obtained.
  • the data is more comprehensive and reliable, and it can expose the monitoring abnormal data of the report.
  • the access module 106 is configured to access the report that needs to be monitored.
  • the process of accessing the report in this embodiment is a process of browsing the report data and browsing the monitoring status data of the report, so as to timely discover the report abnormality.
  • the process of accessing the report in this embodiment by simulating the manner in which the user browses the report, automatically identifies the report to be monitored, and automatically reports the abnormal report, the automatic operation of the entire monitoring process is realized, no personnel intervention is required, the monitoring cost is reduced, and the monitoring effectiveness is improved.
  • the report monitoring device of the embodiment includes:
  • the first writing module 41 is configured to write the monitoring data of the monitoring success report and the monitoring process to the database.
  • This implementation writes the report and monitoring data that are successfully monitored into the database, so that it can be directly included in the automatic monitoring system when the report is used later, eliminating the need for monitoring and testing again, saving costs.
  • a report monitoring apparatus further includes:
  • the triggering module 21 is configured to trigger an alarm mechanism by using the feedback information of the monitoring failure.
  • an alarm mechanism when the monitoring status is monitoring failure, an alarm mechanism is triggered, and an abnormal alarm report is automatically issued to remind the staff to check in time to improve the monitoring efficiency.
  • the alarm mechanism of the embodiment includes that when the feedback information is received or the corresponding preset target keyword is not received in the specified time period, the sound alarm is triggered, or the monitoring failure state is sent while the sound alarm is sounded. Information to the designated staff in order to cause staff to pay attention to and deal with in a timely manner.
  • the other embodiments of the present application may further refine the display manner of the alarm mechanism according to the two conditions of receiving the feedback information or the received feedback information in the specified time period, so that the relevant staff can Different alarm display modes can quickly determine the abnormal cause of report monitoring and improve the efficiency of releasing the abnormal state of report monitoring.
  • the display module 22 is configured to display report information of the report that the monitoring fails.
  • the report information displayed in this embodiment includes the name of the abnormal report, the detection time, the corresponding monitoring model, and the access status, so that the staff or the mechanism for automatically repairing and adjusting the report can accurately grasp the monitoring status in time and provide a timely response plan.
  • the display manner of this embodiment includes sending text information or audio information to a designated person in charge to operate the page, or displaying the text information or audio information through a designated display screen.
  • a report monitoring apparatus includes:
  • the second writing module 23 is configured to write the monitoring failure report and the monitoring status of the corresponding monitoring failure to the database.
  • the monitoring status of the monitoring failure is written into the database, so that the mechanism for repairing and adjusting the report by manual or automatic later is formed, and the prioritized database of the fault cancellation is formed by the strategy scheme for releasing the monitoring failure, so as to encounter and aprior in the later stage.
  • the corresponding policy plan is retrieved in time to improve the timeliness and pertinence of the monitoring failure of the monitoring failure state, which is more conducive to promoting the application scope of the automatic monitoring process.
  • a report monitoring apparatus includes:
  • the classification module 24 is configured to classify the reports of the database according to the monitoring status.
  • the monitoring status in this embodiment includes two states: monitoring failure and monitoring success.
  • the report monitoring data is effectively managed.
  • the monitoring success status after the monitoring failure report is removed.
  • the report is directly incorporated into the automatic monitoring system to reduce the workload of the staff; on the other hand, it is convenient to analyze the data for the reasons of monitoring failure and obtain effective experience in releasing the monitoring fault.
  • the classification module 24 of this embodiment includes:
  • the first forming unit 240 is configured to integrate the report whose monitoring status is successfully monitored into the same directory to form first report data suitable for automatic monitoring.
  • the report successfully recorded in the database is classified into the first report data, so as to further improve the validity and pertinence of the data retrieved from the database in the automatic monitoring process, and also facilitate further automatic monitoring according to the database.
  • the report information of the report enables effective promotion and application automatic monitoring process.
  • the automated monitoring process is applied to the security management area of report data.
  • the access level of the target data and the countermeasures are preset in advance. Permissions for different users can only access low-level report data. If the user with low access rights is over-authorized, the monitoring process is executed according to the preset countermeasures, thereby preventing the current user from accessing the illegal report and information; and automatically writing the unauthorized access exception to the database and issuing the abnormal information message to prevent the user from accessing the report.
  • the automatic monitoring process can upgrade the monitoring level, strengthen the process supervision of the access user, or send the abnormal access to the report data person by SMS to ensure the security of the data in the report system. Sex.
  • the automated monitoring process is applied to the management of audit report data.
  • the automatic monitoring process of this embodiment stores the correct and error states generated in the process database during the process of monitoring the reporting system process, so as to provide a data foundation for the auditors in the process of system auditing and security auditing.
  • a classification module 24 of another embodiment of the present application includes:
  • the second forming unit 241 is configured to integrate the report whose monitoring status is the monitoring failure into the same directory, and form the second report data of the monitoring failure.
  • the failure monitoring report is summarized to analyze the cause of the monitoring failure and improve the analysis efficiency.
  • the second report data in this embodiment includes, but is not limited to, the name of the abnormal report, the detection time, the corresponding monitoring model, the access status, the cause of the abnormality, the exception policy, the abnormal duration, and the like.
  • the above classification module 24 may further include:
  • the analyzing unit 242 is configured to analyze a monitoring failure reason of the second report data.
  • the reason for the monitoring failure in this embodiment includes, but is not limited to, loading failure, loading failure, network failure, loading file interruption, report page configuration and monitoring process mismatch, and the like.
  • the screening unit 243 is configured to filter the report that enters the automatic monitoring system again according to the monitoring failure reason.
  • the loading failure is caused by the loading file corruption, and the file repair display is not repairable.
  • the possibility of filtering into the automatic monitoring system is excluded. If the file repair shows repairable, the file is repaired again. After the system is automatically monitored and the possibility of being successfully monitored, the report screening the repair file enters the queue for the test to be monitored again.
  • classification module 24 of the embodiment includes:
  • the adjusting unit 244 is configured to adjust the matching information of the report according to the monitoring failure reason.
  • the reason for the failure of the monitoring is that the page configuration of the report does not match the monitoring process, you need to adjust the matching information of the report page to improve the success rate of the report that was successfully monitored after the report that failed the monitoring again enters the automatic monitoring process again.
  • the monitoring test unit 245 is configured to perform a secondary monitoring test on the adjusted report.
  • the network status is restored to normal. If the data is restored to normal, the report that has been interrupted due to the network failure and the monitoring failure will enter the automatic monitoring process again. To conduct secondary monitoring and testing to improve the number of monitoring reports in the automatic monitoring process and improve the application coverage of the automatic monitoring process.
  • the computer device may be a server, and its internal structure may be as shown in FIG. 11.
  • the computer device includes a processor, memory, network interface, and database connected by a system bus. Among them, the computer designed processor is used to provide calculation and control capabilities.
  • the memory of the computer device includes a non-volatile storage medium, an internal memory.
  • the non-volatile storage medium stores an operating system, computer readable instructions, and a database.
  • the memory provides an environment for the operation of operating systems and computer readable instructions in a non-volatile storage medium.
  • the database of the computer device is used to store data such as report monitoring.
  • the network interface of the computer device is used to communicate with an external terminal via a network connection.
  • FIG. 11 is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation of the computer device to which the solution of the present application is applied.
  • An embodiment of the present application also provides a computer non-volatile readable storage medium having stored thereon computer readable instructions that, when executed, perform the processes of the embodiments of the methods described above.
  • the above description is only the preferred embodiment of the present application, and is not intended to limit the scope of the patent application, and the equivalent structure or equivalent process transformations made by the specification and the drawings of the present application, or directly or indirectly applied to other related The technical field is equally included in the scope of patent protection of the present application.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Theoretical Computer Science (AREA)
  • Environmental & Geological Engineering (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Debugging And Monitoring (AREA)

Abstract

本申请揭示了报表监控方法、装置、计算机设备和存储介质，方法包括：异步等待处于监控状态的报表在完成数据加载后的回馈信息；若未接收到回馈信息，则判定监控状态为监控失败；若接收到回馈信息，则分析回馈信息中是否携带预设的目标关键字；若携带，则判定监控状态为监控成功；若未携带，则判定监控状态为监控失败。

Description

报表监控方法、装置、计算机设备和存储介质
本申请要求于2018年4月20日提交中国专利局、申请号为2018103621971，发明名称为“报表监控方法、装置、计算机设备和存储介质”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及到计算机应用领域，特别是涉及到报表监控方法、装置、计算机设备和存储介质。
 背景技术
网络管理包括监视登录因特网的行为和内容，即上网监控或外网监控；还包括内网监控或本网监控；现有监控工具不支持异步加载类型的报表监控，且现有监控工具的数据库未得到广泛推广应用，自动化流程低仍需人工频繁介入，比如需要人员登录浏览报表，人为进行监控流程切换，耗费大量的人力、物力和财力，监控流程进展的效率较低，且容易出现人工失误。
 技术问题
本申请的主要目的为提供一种报表监控方法，旨在解决现有监控工具不支持异步加载类型的报表监控的技术问题。
 技术解决方案
本申请提出一种报表监控方法，包括：
异步等待处于监控状态的报表在完成数据加载后的回馈信息；
若未接收到所述回馈信息，则判定监控状态为监控失败；
若接收到所述回馈信息，则分析所述回馈信息中是否携带预设的目标关键字；
若携带所述目标关键字，则判定监控状态为监控成功；
若未携带所述目标关键字，则判定监控状态为监控失败。
本申请还提供了一种报表监控装置，包括：
异步等待模块，用于异步等待处于监控状态的报表在完成数据加载后的回馈信息；
第一判定模块，用于若未接收到所述回馈信息，则判定监控状态为监控失败；
分析模块，用于若接收到所述回馈信息，则分析所述回馈信息中是否携带预设的目标关键字；
第二判定模块，用于若携带所述目标关键字，则判定监控状态为监控成功；
第三判定模块，用于若未携带所述目标关键字，则判定监控状态为监控失败。
本申请还提供了一种计算机设备，包括存储器和处理器，所述存储器存储有计算机可读指令，所述处理器执行所述计算机可读指令时实现上述方法的步骤。
本申请还提供了一种计算机非易失性可读存储介质，其上存储有计算机可读指令，所述计算机可读指令被处理器执行时实现上述的方法的步骤。
 有益效果
本申请有益技术效果：本申请通过异步等待目标关键字的方法实现异步加载类型的自动化监控，提高监控效率、流程化、准确性，尤其是Cognos报表类型的监控，弥补了现有技术的缺陷，具有实际应用价值；本申请通过模拟用户浏览报表、自动识别要监控报表、自动报警异常报表的方式，实现在整个监控流程的自动化，无需人员介入，降低监控成本，提高监控的有效性；本申请通过自动报警异常报表，并回馈异常类型，为数据库的再分析、再利用，提供有用的参考信息，进一步推广自动监控流程的应用覆盖面。
 附图说明
图1 本申请一实施例的报表监控方法流程示意图；
图2 本申请一实施例的报表监控装置结构示意图；
图3 本申请一实施例的报表监控装置的优化结构示意图；
图4 本申请一实施例的确定模块的装置结构示意图；
图5 本申请一实施例的报表监控装置的再优化结构示意图；
图6 本申请另一实施例的报表监控装置结构示意图；
图7 本申请另一实施例的报表监控装置的优化结构示意图；
图8 本申请再一实施例的报表监控装置结构示意图；
图9 本申请一实施例的分类模块的结构示意图；
图10 本申请又一实施例的分类模块的结构示意图；
图11 本申请一实施例的计算机设备内部结构示意图。
 本发明的最佳实施方式
参照图1，本申请一实施例的报表监控方法，包括：
S1：异步等待处于监控状态的报表在完成数据加载后的回馈信息。
本步骤中的异步是指被监控对象的机制，例如浏览器加载事项具有顺序，等待加载事项完成后才去检测返回的内容，本实施例的异步则为报表页面在完成数据加载后，另外通过AJAX（Asynchronous Javascript And XML，异步 JavaScript 和 XML，是指一种创建交互式网页应用的网页开发技术）的机制去请求其他核心内容，比如细节数据等。本实施例的报表为异步加载类型的报表，比如Cognos报表类型，举例地，先加载报表框架，然后通过异步加载报表数据内容。本实施例的Cognos是核心平台上以服务为导向进行架构的数据模型，是唯一可通过单一产品或在单一可靠架构上提供完整业务智能功能的解决方案，可以提供无缝密合的报表、分析、记分卡、仪表盘等解决方案，通过提供所有的系统和资料资源， Cognos业务智能解决方案可以容易地整合到现有的多系统和数据源架构中，Cognos报表基于统一的元数据模型，为应用提供统一的视图，用户可以在浏览器中自定义报表，格式灵活元素丰富，而且可通过Query Studio（功能强大的数据库查询构建控件）进行及时的开放式查询，Cognos报表的制作和展示可通过纯粹的Web界面，使得部署成本和管理成本降到最低，但该异步加载类型的报表缺乏实时性，无法进行实时状态监控，不利于掌控报表的加载数据状态是否正常。
S2：若未接收到所述回馈信息，则判定监控状态为监控失败。
本实施例中若未收到回馈信息，则说明报表未处于监控状态，或自动监控系统与被监控报表不存在匹配衔接关系，监控失败。
S3：若接收到所述回馈信息，则分析所述回馈信息中是否携带预设的目标关键字。
本步骤的目标关键字包括报表加载数据状态为加载完成后，加载页面上形成的树形菜单的标签关键字，本申请其他实施例的目标关键字也可以是用户预设的其他标识符号或内容。本实施例通过接收到目标关键字则说明报表加载数据状态为加载成功，可进行监控，通过监听目标关键字间接监控异步加载类型的报表加载数据状态是否处于正常状态。本实施例通过异步等待目标关键字的方式实现对异步加载类型的Web监控，弥补了现有行业内无法实现异步加载类型的Web进行自动监控的技术漏洞。异步加载即非阻塞加载，浏览器在下载的同时，还会继续进行后续页面的解析处理，通过异步加载提高数据分流加载的速率，提高事务进展效率，且同时通过异步等待目标关键字的方式实现对异步加载类型的Web监控，在提高事务进程效率的同时，保证了安全有效性。本实施例通过异步等待目标关键字的方法实现异步加载类型的自动化监控，提高监控效率、流程化、准确性，尤其是Cognos报表类型的监控，弥补了异步加载类型报表无法实现监控的缺陷，具有实际应用价值。
S4：若携带所述目标关键字，则判定监控状态为监控成功。
本实施例通过接收到目标关键字表示报表与自动监控系统相匹配，可进行正常监控，则反馈监控状态为监控成功。
S5：若未携带所述目标关键字，则判定监控状态为监控失败。
本实施例中的监控状态包括监控失败和监控成功两种状态，当回馈信息中没有携带预设的目标关键字或未收到回馈信息，均为监控失败，以便及时提醒人工参与操作，并及时查看报表加载数据状态是否异常。本申请其他实施例根据接收到的监控失败状态自动启动报表监控失败后的报表修复与调整机制，以便及时疏通监控障碍，使报表监控流程顺畅进行。
进一步地，本实施例中，步骤S1之前，包括：
S10：根据各报表的模型刷新的状态信息确定需要监控的报表。
本步骤中的状态信息由模型刷新程序生成，即通过模型刷新进行重新加载数据。本实施例的报表依赖于报表加载数据，报表加载数据依赖于模型刷新。例如状态信息包括模型刷新的六个状态，等待刷新->刷新中->刷新异常->完成刷新->发布中-〉发布完成。模型刷新并发布完成为整个流程，发布完成表示相应的报表有数据加载更新，本实施例中出现更新加载数据的报表则为需要监控的报表，报表加载数据的更新状态为发布完成后，自动根据加载数据的更新进展状态罗列需要监控的报表清单，以便自动进入监控系统。
本实施例确定需要监控的报表清单的流程如下，即步骤S10，包括：
S101：接收第一报表于模型刷新后发布的状态信息。
本步骤的状态信息即如上所述的六个状态中的一种，接收方式可以是文字表述比如刷新异常，或预设的相对应的指定代码信息，比如刷新异常时显示代码为‘HTTP404错误’等。
S102：判断第一报表的模型刷新的状态信息是否为发布完成。
本步骤通过文字识别或字符识别等方式对接收的状态信息进行识别分析。本实施例的文字识别或字符识别通过模板比对的方法进行识别，通过对文字或字符进行分割并提取特征参数，然后将提取的特征参数与模板中预存的指示发布完成的文字或字符特征相比较，根据相似性确定与模板中匹配的某一文字或字符，如果匹配成功则说明状态信息为发布完成，否则则为未发布完成。比如通过判断相似性是否达到预设阈值，若达到，则表示接收的状态信息的文字或字符与模板的某一文字或字符一致。
S103：若是，则确定上述第一报表为需要监控的报表。
本步骤只以接收到的状态信息为发布完成时，才判定报表处于加载数据的更新状态，进而判定需要监控此报表，触发自动监控系统监控此报表。上述六种状态信息中除发布完成之外的任何一种状态信息，均不会触发自动监控系统。
进一步地，本实施例的步骤S10之后，包括：
S104：自动启动浏览器。
本实施例通过模拟用户行为自动打开浏览器，以增加监控流程的自动化。本实施例的浏览器包括IE6以上版本的浏览器。
S105：于所述浏览器的登录页面进行登录认证。
本实施例在自动登录浏览器页面后，通过自动录入用户名和密码，模拟用户浏览报表的方式，自动访问处于监控状态的报表的报表数据，以进一步提高监控流程的自动化，不需要人工参与，且浏览频率更高，浏览的数据更全面。比如，人工点击时受限于人工操作的动作频率，点击访问率过小，本实施例通过模拟人工登录，可设定高频率、大数据的访问模式，提高访问数据的覆盖面，使访问获得的数据更全面、更可靠，更能暴露报表的监控异常数据。
S106：访问需要监控的所述报表。
本实施例的访问报表的过程即浏览报表数据、浏览报表的监控状态数据的过程，以便及时发现报表异常。本实施例通过模拟用户浏览报表、自动识别要监控报表、自动报警异常报表的方式，实现在整个监控流程的自动化操作，无需人员介入，降低监控成本，且提高监控的有效性。
进一步地，本实施例的步骤S4之后，包括：
S41：将监控成功的报表和监控过程的监控数据写入数据库。
本实施通过将监控成功的报表和监控数据写入数据库，以便后续使用该报表时直接将其纳入自动监控系统，省却再次进行监控测试过程，节约成本。
本申请另一实施例中，步骤S2或S5之后，还包括：
S21:所述监控失败的反馈信息触发报警机制。
本实施例中当监控状态为监控失败时，会触发报警机制，自动报警异常报表，以提醒工作人员及时查看，提高监控效率。本实施例的报警机制包括指定时间段内为接收到回馈信息或接收到的回馈信息中无相应的预设目标关键字，则会触发鸣音报警，或鸣音报警的同时发送监控失败状态的信息到指定工作人员，以便引起工作人员及时关注与处理。本申请其他实施例可根据指定时间段内为接收到回馈信息或接收到的回馈信息中无相应的预设目标关键字两种状况，进一步细化报警机制的展示方式，以便相关工作人员根据两种不同的报警展示方式，快速判断出报表监控的异常原因，提高解除报表监控的异常状态的效率。
S22:展示所述监控失败的报表的报表信息。
本实施例展示的报表信息包括异常报表的名字、检测时间、对应监控模型、访问状态等信息，以便工作人员或自动进行报表修复与调整的机制及时准确地掌握监控状态，及时给出应对的方案策略。本实施例的展示方式包括发送文本信息或音频信息到指定负责人操作页面，或将文本信息或音频信息通过指定显示屏进行展示。
进一步地，本申请另一实施例中，步骤S22之后，包括：
S23：将监控失败的报表的报表信息和对应的监控失败的监控状态写入数据库。
本实施通过将监控失败的监控状态写入数据库，以便将后期通过人工或自动进行报表修复与调整的机制，与解除监控失败的策略方案形成故障解除的先验数据库，以便后期遇到与先验数据库中已存在的监控故障时，及时调取相应的策略方案，提高解除监控失败状态的监控故障的时效性和针对性，更利于推广自动监控流程的应用范围。
本申请再一实施例中，步骤S23之后，包括：
S24：根据监控状态对数据库的报表进行分类。
本实施例中的监控状态包括监控失败和监控成功两种状态，通过将监控失败的报表进行归类，实现对报表监控数据的有效管理，一方面将剔除掉监控失败报表后的监控成功状态的报表直接纳入自动监控体系，减少工作人员的工作量；另一方面方便对监控失败的原因集中进行数据分析，获取解除监控故障的有效经验。
进一步地，本实施例的步骤S24，包括：
S240：通过将监控状态为监控成功的报表整合于同一目录下，形成适于自动监控的第一报表数据。
本实施例通过将数据库的中监控成功的报表归类成第一报表数据，以进一步提高自动监控流程中从数据库调取数据的有效性和针对性，同时也便于进一步根据数据库中适于自动监控的报表的报表信息，实现有效的推广和应用自动监控流程。
举例地，自动监控流程应用于报表数据的安全性管理领域。本实施例在报表访问过程中，提前预设目标数据的访问级别及应对措施。不同用户的权限只能访问低级别报表数据。如果低访问权限用户越权访问，监控流程根据预设应对措施执行，从而阻止当前用户访问非法报表及信息；并将越权访问异常自动写入数据库、同时发出异常信息邮件，防止用户在访问报表过程中，企图越级访问高级别数据报表，同时自动监控流程可以升级监控级别，加强对该访问用户的过程监督，或同时将异常访问通过短信方式发送给报表数据负责人，以保证报表系统中数据的安全性。
再举例地，自动监控流程应用于审计报表数据的管理领域。本实施例的自动监控流程在监督报表系统过程展示过程中，将产生的正确和错误状态存放在过程数据库中，以便在系统审计与安全审计过程中，为审计人员提供数据基础。
本申请又一实施例中，步骤S24，包括：
S241：将监控状态为监控失败的报表整合于同一目录下，形成监控失败的第二报表数据。
本实施例通过汇总监控失败的报表的报表信息，以便集中分析监控失败的原因，提高分析效率。本实施例的第二报表数据包括但不限于异常报表的名字、检测时间、对应监控模型、访问状态、异常原因、解除异常策略、异常持续时间等信息。
步骤S241之后还可以包括：
S242：分析所述第二报表数据的监控失败原因。
本实施例的监控失败原因，包括但不限于加载文件损坏导致加载失败、网络故障导致加载文件中断、报表的页面配置与监控流程不匹配等。
S243：根据所述监控失败原因筛选再次进入自动监控系统的报表。
比如：监控失败时由于加载文件损坏导致加载失败而引起的，文件修复显示不可修复，则排除再次筛选进自动监控系统的可能性；若文件修复显示可修复，则存在通过修复文件后，再次进入自动监控系统后被成功监控的可能性，则筛选修复文件的报表进入再次待监控测试的队列。
进一步地，步骤S243之后，包括：
S244：根据所述监控失败原因调整报表的匹配信息。
比如，监控失败原因为报表的页面配置与监控流程不匹配，则需要调整报表页面的匹配信息，以提高上次监控失败的报表再次进入自动监控流程后被成功监控的成功率。
S245：重新对调整后的报表进行二次监控测试。
举例地，由于网络故障导致加载文件中断，导致监控失败，则通过诊断网络状态是否恢复正常，若恢复正常则将上次由于网络故障导致加载文件中断进而导致监控失败的报表再次进入自动监控流程，以进行二次监控测试，以提高自动监控流程的监控报表的数量，提高自动监控流程的应用覆盖范围。
本申请通过异步等待目标关键字的方法实现异步加载类型的自动化监控，提高监控效率、流程化、准确性，尤其是Cognos报表类型的监控，弥补了现有技术的缺陷，具有实际应用价值；本申请通过模拟用户浏览报表、自动识别要监控报表、自动报警异常报表的方式，实现在整个监控流程的自动化，无需人员介入，降低监控成本，提高监控的有效性；本申请通过自动报警异常报表，并回馈异常类型，为数据库的再分析、再利用，提供有用的参考信息，进一步推广自动监控流程的应用覆盖面。
参照图2，本申请一实施例的报表监控装置，包括：
异步等待模块1，用于异步等待处于监控状态的报表在完成数据加载后的回馈信息。
本实施例中的异步是指被监控对象的机制，例如浏览器加载事项具有顺序，等待加载事项完成后才去检测返回的内容，本实施例的异步则为报表页面在完成数据加载后，另外通过AJAX（Asynchronous Javascript And XML，异步 JavaScript 和 XML，是指一种创建交互式网页应用的网页开发技术）的机制去请求其他核心内容，比如细节数据等。本实施例的报表为异步加载类型的报表，比如Cognos报表类型，举例地，先加载报表框架，然后通过异步加载报表数据内容。本实施例的Cognos是核心平台上以服务为导向进行架构的数据模型，是唯一可通过单一产品或在单一可靠架构上提供完整业务智能功能的解决方案，可以提供无缝密合的报表、分析、记分卡、仪表盘等解决方案，通过提供所有的系统和资料资源， Cognos业务智能解决方案可以容易地整合到现有的多系统和数据源架构中，Cognos报表基于统一的元数据模型，为应用提供统一的视图，用户可以在浏览器中自定义报表，格式灵活元素丰富，而且可通过Query Studio（功能强大的数据库查询构建控件）进行及时的开放式查询，Cognos报表的制作和展示可通过纯粹的Web界面，使得部署成本和管理成本降到最低，但该异步加载类型的报表缺乏实时性，无法进行实时状态监控，不利于掌控报表的加载数据状态是否正常。
第一判定模块2，用于若未接收到所述回馈信息，则判定监控状态为监控失败。
本实施例中若未收到回馈信息，则说明报表未处于监控状态，或自动监控系统与被监控报表不存在匹配衔接关系，监控失败。
分析模块3，用于若接收到所述回馈信息，则分析所述回馈信息中是否携带预设的目标关键字。
本实施例的目标关键字包括报表加载数据状态为加载完成后，加载页面上形成的树形菜单的标签关键字，本申请其他实施例的目标关键字也可以是用户预设的其他标识符号或内容。本实施例通过接收到目标关键字则说明报表加载数据状态为加载成功，可进行监控，通过监听目标关键字间接监控异步加载类型的报表加载数据状态是否处于正常状态。本实施例通过异步等待目标关键字的方式实现对异步加载类型的Web监控，弥补了现有行业内无法实现异步加载类型的Web进行自动监控的技术漏洞。异步加载即非阻塞加载，浏览器在下载的同时，还会继续进行后续页面的解析处理，通过异步加载提高数据分流加载的速率，提高事务进展效率，且同时通过异步等待目标关键字的方式实现对异步加载类型的Web监控，在提高事务进程效率的同时，保证了安全有效性。本实施例通过异步等待目标关键字的方法实现异步加载类型的自动化监控，提高监控效率、流程化、准确性，尤其是Cognos报表类型的监控，弥补了异步加载类型报表无法实现监控的缺陷，具有实际应用价值。
第二判定模块4，用于若携带所述目标关键字，则判定监控状态为监控成功。
本实施例通过接收到目标关键字表示报表与自动监控系统相匹配，可进行正常监控，则反馈监控状态为监控成功。
第三判定模块5，用于若未携带所述目标关键字，则判定监控状态为监控失败。
本实施例中的监控状态包括监控失败和监控成功两种状态，当回馈信息中没有携带预设的目标关键字或未收到回馈信息，均为监控失败，以便及时提醒人工参与操作，并及时查看报表加载数据状态是否异常。本申请其他实施例根据接收到的监控失败状态自动启动报表监控失败后的报表修复与调整机制，以便及时疏通监控障碍，使报表监控流程顺畅进行。
参照图3，本实施例的报表监控装置，包括：
确定模块10，用于根据各报表的模型刷新的状态信息确定需要监控的报表。
本实施例中的状态信息由模型刷新程序生成，即通过模型刷新进行重新加载数据。本实施例的报表依赖于报表加载数据，报表加载数据依赖于模型刷新。例如状态信息包括模型刷新的六个状态，等待刷新->刷新中->刷新异常->完成刷新->发布中-〉发布完成。模型刷新并发布完成为整个流程，发布完成表示相应的报表有数据加载更新，本实施例中出现更新加载数据的报表则为需要监控的报表，报表加载数据的更新状态为发布完成后，自动根据加载数据的更新进展状态罗列需要监控的报表清单，以便自动进入监控系统。
参照图4，本实施例的确定模块10，包括：
接收单元101，用于接收第一报表于模型刷新后发布的状态信息。
本实施例的状态信息即如上所述的六个状态中的一种，接收方式可以是文字表述比如刷新异常，或预设的相对应的指定代码信息，比如刷新异常时显示代码为‘HTTP404错误’等。
判断单元102，用于判断第一报表的模型刷新的状态信息是否为发布完成。
本实施例通过文字识别或字符识别等方式对接收的状态信息进行识别分析。本实施例的文字识别或字符识别通过模板比对的方法进行识别，通过对文字或字符进行分割并提取特征参数，然后将提取的特征参数与模板中预存的指示发布完成的文字或字符特征相比较，根据相似性确定与模板中匹配的某一文字或字符，如果匹配成功则说明状态信息为发布完成，否则则为未发布完成。比如通过判断相似性是否达到预设阈值，若达到，则表示接收的状态信息的文字或字符与模板的某一文字或字符一致。
确定单元103，用于若是发布完成，则确定上述第一报表为需要监控的报表。
本实施例只以接收到的状态信息为发布完成时，才判定报表处于加载数据的更新状态，进而判定需要监控此报表，触发自动监控系统监控此报表。上述六种状态信息中除发布完成之外的任何一种状态信息，均不会触发自动监控系统。
参照图5，本实施例的报表监控装置，包括：
启动模块104，用于自动启动浏览器。
本实施例通过模拟用户行为自动打开浏览器，以增加监控流程的自动化。本实施例的浏览器包括IE6以上版本的浏览器。
登录模块105，用于在所述浏览器的登录页面进行登录认证。
本实施例在自动登录浏览器页面后，通过自动录入用户名和密码，模拟用户浏览报表的方式，自动访问处于监控状态的报表的报表数据，以进一步提高监控流程的自动化，不需要人工参与，且浏览频率更高，浏览的数据更全面。比如，人工点击时受限于人工操作的动作频率，点击访问率过小，本实施例通过模拟人工登录，可设定高频率、大数据的访问模式，提高访问数据的覆盖面，使访问获得的数据更全面、更可靠，更能暴露报表的监控异常数据。
访问模块106，用于访问需要监控的所述报表。
本实施例的访问报表的过程即浏览报表数据、浏览报表的监控状态数据的过程，以便及时发现报表异常。本实施例通过模拟用户浏览报表、自动识别要监控报表、自动报警异常报表的方式，实现在整个监控流程的自动化操作，无需人员介入，降低监控成本，且提高监控的有效性。
进一步地，本实施例的报表监控装置，包括：
第一写入模块41，用于将监控成功的报表和监控过程的监控数据写入数据库。
本实施通过将监控成功的报表和监控数据写入数据库，以便后续使用该报表时直接将其纳入自动监控系统，省却再次进行监控测试过程，节约成本。
参照图6，本申请另一实施例的报表监控装置，还包括：
触发模块21，用于通过所述监控失败的反馈信息触发报警机制。
本实施例中当监控状态为监控失败时，会触发报警机制，自动报警异常报表，以提醒工作人员及时查看，提高监控效率。本实施例的报警机制包括指定时间段内为接收到回馈信息或接收到的回馈信息中无相应的预设目标关键字，则会触发鸣音报警，或鸣音报警的同时发送监控失败状态的信息到指定工作人员，以便引起工作人员及时关注与处理。本申请其他实施例可根据指定时间段内为接收到回馈信息或接收到的回馈信息中无相应的预设目标关键字两种状况，进一步细化报警机制的展示方式，以便相关工作人员根据两种不同的报警展示方式，快速判断出报表监控的异常原因，提高解除报表监控的异常状态的效率。
展示模块22，用于展示所述监控失败的报表的报表信息。
本实施例展示的报表信息包括异常报表的名字、检测时间、对应监控模型、访问状态等信息，以便工作人员或自动进行报表修复与调整的机制及时准确地掌握监控状态，及时给出应对的方案策略。本实施例的展示方式包括发送文本信息或音频信息到指定负责人操作页面，或将文本信息或音频信息通过指定显示屏进行展示。
参照图7，本申请另一实施例的报表监控装置，包括：
第二写入模块23，用于将监控失败的报表和对应的监控失败的监控状态写入数据库。
本实施通过将监控失败的监控状态写入数据库，以便将后期通过人工或自动进行报表修复与调整的机制，与解除监控失败的策略方案形成故障解除的先验数据库，以便后期遇到与先验数据库中已存在的监控故障时，及时调取相应的策略方案，提高解除监控失败状态的监控故障的时效性和针对性，更利于推广自动监控流程的应用范围。
参照图8，本申请再一实施例的报表监控装置，包括：
分类模块24，用于根据监控状态对数据库的报表进行分类。
本实施例中的监控状态包括监控失败和监控成功两种状态，通过将监控失败的报表进行归类，实现对报表监控数据的有效管理，一方面将剔除掉监控失败报表后的监控成功状态的报表直接纳入自动监控体系，减少工作人员的工作量；另一方面方便对监控失败的原因集中进行数据分析，获取解除监控故障的有效经验。
参照图9，本实施例的分类模块24，包括：
第一形成单元240，用于将监控状态为监控成功的报表整合于同一目录下，形成适于自动监控的第一报表数据。
本实施例通过将数据库的中监控成功的报表归类成第一报表数据，以进一步提高自动监控流程中从数据库调取数据的有效性和针对性，同时也便于进一步根据数据库中适于自动监控的报表的报表信息，实现有效的推广和应用自动监控流程。
举例地，自动监控流程应用于报表数据的安全性管理领域。本实施例在报表访问过程中，提前预设目标数据的访问级别及应对措施。不同用户的权限只能访问低级别报表数据。如果低访问权限用户越权访问，监控流程根据预设应对措施执行，从而阻止当前用户访问非法报表及信息；并将越权访问异常自动写入数据库、同时发出异常信息邮件，防止用户在访问报表过程中，企图越级访问高级别数据报表，同时自动监控流程可以升级监控级别，加强对该访问用户的过程监督，或同时将异常访问通过短信方式发送给报表数据负责人，以保证报表系统中数据的安全性。
再举例地，自动监控流程应用于审计报表数据的管理领域。本实施例的自动监控流程在监督报表系统过程展示过程中，将产生的正确和错误状态存放在过程数据库中，以便在系统审计与安全审计过程中，为审计人员提供数据基础。
参照图10，本申请又一实施例的分类模块24，包括：
第二形成单元241，用于将监控状态为监控失败的报表整合于同一目录下，形成监控失败的第二报表数据。
本实施例通过汇总监控失败的报表，以便集中分析监控失败的原因，提高分析效率。本实施例的第二报表数据包括但不限于异常报表的名字、检测时间、对应监控模型、访问状态、异常原因、解除异常策略、异常持续时间等信息。
上述分类模块24还可以包括：
分析单元242，用于分析所述第二报表数据的监控失败原因。
本实施例的监控失败原因，包括但不限于加载文件损坏导致加载失败、网络故障导致加载文件中断、报表的页面配置与监控流程不匹配等。
筛选单元243，用于根据所述监控失败原因筛选再次进入自动监控系统的报表。
比如：监控失败时由于加载文件损坏导致加载失败而引起的，文件修复显示不可修复，则排除再次筛选进自动监控系统的可能性；若文件修复显示可修复，则存在通过修复文件后，再次进入自动监控系统后被成功监控的可能性，则筛选修复文件的报表进入再次待监控测试的队列。
进一步地，本实施例的分类模块24，包括：
调整单元244，用于根据所述监控失败原因调整报表的匹配信息。
比如，监控失败原因为报表的页面配置与监控流程不匹配，则需要调整报表页面的匹配信息，以提高上次监控失败的报表再次进入自动监控流程后被成功监控的成功率。
监控测试单元245，用于重新对调整后的报表进行二次监控测试。
举例地，由于网络故障导致加载文件中断，导致监控失败，则通过诊断网络状态是否恢复正常，若恢复正常则将上次由于网络故障导致加载文件中断进而导致监控失败的报表再次进入自动监控流程，以进行二次监控测试，以提高自动监控流程的监控报表的数量，提高自动监控流程的应用覆盖范围。
参照图11，本申请实施例中还提供一种计算机设备，该计算机设备可以是服务器，其内部结构可以如图11所示。该计算机设备包括通过系统总线连接的处理器、存储器、网络接口和数据库。其中，该计算机设计的处理器用于提供计算和控制能力。该计算机设备的存储器包括非易失性存储介质、内存储器。该非易失性存储介质存储有操作系统、计算机可读指令和数据库。该内存器为非易失性存储介质中的操作系统和计算机可读指令的运行提供环境。该计算机设备的数据库用于存储报表监控等数据。该计算机设备的网络接口用于与外部的终端通过网络连接通信。该计算机可读指令在执行时，执行如上述各方法的实施例的流程。本领域技术人员可以理解，图11中示出的结构，仅仅是与本申请方案相关的部分结构的框图，并不构成对本申请方案所应用于其上的计算机设备的限定。
本申请一实施例还提供一种计算机非易失性可读存储介质，其上存储有计算机可读指令，该计算机可读指令在执行时，执行如上述各方法的实施例的流程。以上所述仅为本申请的优选实施例，并非因此限制本申请的专利范围，凡是利用本申请说明书及附图内容所作的等效结构或等效流程变换，或直接或间接运用在其他相关的技术领域，均同理包括在本申请的专利保护范围内。

Claims (20)

  1. 一种报表监控方法，其特征在于，包括：
    异步等待处于监控状态的报表在完成数据加载后的回馈信息；
    若未接收到所述回馈信息，则判定监控状态为监控失败；
    若接收到所述回馈信息，则分析所述回馈信息中是否携带预设的目标关键字；
    若携带所述目标关键字，则判定监控状态为监控成功；
    若未携带所述目标关键字，则判定监控状态为监控失败。
  2. 根据权利要求1所述的报表监控方法，其特征在于，所述异步等待处于监控状态的报表在完成数据加载后的回馈信息的步骤之前，包括：
    根据各报表的模型刷新的状态信息确定需要监控的报表。
  3. 根据权利要求2所述的报表监控方法，其特征在于，所述根据各报表的模型刷新的状态信息确定需要监控的报表的步骤，包括：
    接收第一报表于模型刷新后发布的状态信息；
    判断所述第一报表的状态信息是否为发布完成；
    若是，则确定所述第一报表为需要监控的报表。
  4. 根据权利要求2所述的报表监控方法，其特征在于，所述根据各报表的模型刷新的状态信息确定需要监控的报表的步骤之后，包括：
    自动启动浏览器；
    于所述浏览器的登录页面进行登录认证；
    访问需要监控的所述报表。
  5. 根据权利要求1所述的报表监控方法，其特征在于，所述若携带所述目标关键字，则判定监控状态为监控成功的步骤之后，包括：
    将监控成功的报表和监控过程中的监控数据写入数据库。
  6. 根据权利要求1所述的报表监控方法，其特征在于，所述则判定监控状态为监控失败的步骤之后，还包括：
    通过所述监控失败的反馈信息触发报警机制；
    展示监控失败的报表的报表信息。
  7. 根据权利要求6所述的报表监控方法，其特征在于，所述展示所述监控失败的报表的报表信息的步骤之后，包括：
    将所述监控失败的报表的报表信息和对应的监控失败的监控状态写入数据库。
  8. 一种报表监控装置，其特征在于，包括：
    异步等待模块，用于异步等待处于监控状态的报表在完成数据加载后的回馈信息；
    第一判定模块，用于若未接收到所述回馈信息，则判定监控状态为监控失败；
    分析模块，用于若接收到所述回馈信息，则分析所述回馈信息中是否携带预设的目标关键字；
    第二判定模块，用于若携带所述目标关键字，则判定监控状态为监控成功；
    第三判定模块，用于若未携带所述目标关键字，则判定监控状态为监控失败。
  9. 根据权利要求8所述的报表监控装置，其特征在于，包括：
    确定模块，用于根据各报表的模型刷新的状态信息确定需要监控的报表。
  10. 根据权利要求9所述的报表监控装置，其特征在于，所述确定模块，包括：
    接收单元，用于接收第一报表于模型刷新后发布的状态信息；
    判断单元，用于判断所述第一报表的状态信息是否为发布完成；
    确定单元，用于若是发布完成，则确定所述第一报表为需要监控的报表。
  11. 根据权利要求9所述的报表监控装置，其特征在于，包括：
    启动模块，用于自动启动浏览器；
    登录模块，用于在所述浏览器的登录页面进行登录认证；
    访问模块，用于访问需要监控的所述报表。
  12. 根据权利要求8所述的报表监控装置，其特征在于，包括：
    第一写入模块，用于将监控成功的报表和监控过程中的监控数据写入数据库。
  13. 根据权利要求8所述的报表监控装置，其特征在于，还包括：
    触发模块，用于通过所述监控失败的反馈信息触发报警机制；
    展示模块，用于展示监控失败的报表的报表信息。
  14. 根据权利要求13所述的报表监控装置，其特征在于，包括：
    第二写入模块，用于将所述监控失败的报表的报表信息和对应的监控失败的监控状态写入数据库。
  15. 一种计算机设备，包括存储器和处理器，所述存储器存储有计算机可读指令，其特征在于，所述处理器执行所述计算机可读指令时实现报表监控方法，方法包括：
    异步等待处于监控状态的报表在完成数据加载后的回馈信息；
    若未接收到所述回馈信息，则判定监控状态为监控失败；
    若接收到所述回馈信息，则分析所述回馈信息中是否携带预设的目标关键字；
    若携带所述目标关键字，则判定监控状态为监控成功；
    若未携带所述目标关键字，则判定监控状态为监控失败。
  16. 根据权利要求15所述的计算机设备，其特征在于，所述异步等待处于监控状态的报表在完成数据加载后的回馈信息的步骤之前，包括：
    根据各报表的模型刷新的状态信息确定需要监控的报表。
  17. 根据权利要求16所述的计算机设备，其特征在于，所述根据各报表的模型刷新的状态信息确定需要监控的报表的步骤，包括：
    接收第一报表于模型刷新后发布的状态信息；
    判断所述第一报表的状态信息是否为发布完成；
    若是，则确定所述第一报表为需要监控的报表。
  18. 一种计算机非易失性可读存储介质，其上存储有计算机可读指令，其特征在于，所述计算机可读指令被处理器执行时实现报表监控方法，方法包括：
    异步等待处于监控状态的报表在完成数据加载后的回馈信息；
    若未接收到所述回馈信息，则判定监控状态为监控失败；
    若接收到所述回馈信息，则分析所述回馈信息中是否携带预设的目标关键字；
    若携带所述目标关键字，则判定监控状态为监控成功；
    若未携带所述目标关键字，则判定监控状态为监控失败。
  19. 根据权利要求18所述的计算机非易失性可读存储介质，其特征在于，所述异步等待处于监控状态的报表在完成数据加载后的回馈信息的步骤之前，包括：
    根据各报表的模型刷新的状态信息确定需要监控的报表。
  20. 根据权利要求19所述的计算机非易失性可读存储介质，其特征在于，所述根据各报表的模型刷新的状态信息确定需要监控的报表的步骤，包括：
    接收第一报表于模型刷新后发布的状态信息；
    判断所述第一报表的状态信息是否为发布完成；
    若是，则确定所述第一报表为需要监控的报表。
PCT/CN2018/095500 2018-04-20 2018-07-12 报表监控方法、装置、计算机设备和存储介质 WO2019200750A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810362197.1A CN108847998B (zh) 2018-04-20 2018-04-20 报表监控方法、装置、计算机设备和存储介质
CN201810362197.1 2018-04-20

Publications (1)

Publication Number Publication Date
WO2019200750A1 true WO2019200750A1 (zh) 2019-10-24

Family

ID=64212180

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/095500 WO2019200750A1 (zh) 2018-04-20 2018-07-12 报表监控方法、装置、计算机设备和存储介质

Country Status (2)

Country Link
CN (1) CN108847998B (zh)
WO (1) WO2019200750A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113220807A (zh) * 2021-04-01 2021-08-06 辽宁工程技术大学 一种遥感数据自动化发布与在线流程监控方法
CN113254994A (zh) * 2021-05-27 2021-08-13 平安普惠企业管理有限公司 数据库访问方法、装置、存储介质和计算机设备
CN113836160A (zh) * 2021-09-28 2021-12-24 上海市大数据股份有限公司 一种基于主从同步的数据流状态监控告警系统

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112598323B (zh) * 2020-12-30 2023-01-20 广东电网有限责任公司广州供电局 跨业务域流程监控方法、装置、计算机设备和存储介质
CN112650649A (zh) * 2020-12-30 2021-04-13 新奥数能科技有限公司 报表监控方法、装置、计算机可读存储介质及电子设备
CN113204416A (zh) * 2021-04-07 2021-08-03 上海多维度网络科技股份有限公司 数据报表任务执行方法、装置、设备和存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5737592A (en) * 1995-06-19 1998-04-07 International Business Machines Corporation Accessing a relational database over the Internet using macro language files
CN103412961A (zh) * 2013-09-04 2013-11-27 广东全通教育股份有限公司 一种实时导出海量数据报表的处理方法和系统
CN103457802A (zh) * 2013-09-09 2013-12-18 中国农业银行股份有限公司 一种信息传输系统及方法
CN206894667U (zh) * 2017-06-01 2018-01-16 湖南商学院 网络系统监控报表系统
CN107659443A (zh) * 2017-09-22 2018-02-02 天翼电子商务有限公司 一种实时业务的监控方法及其系统

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2443861A (en) * 2006-10-25 2008-05-21 Worldwide Electronic Consultan Information Storage and Distribution via Text Message (SMS, MMS etc)
CN103856359B (zh) * 2012-11-28 2018-03-13 腾讯科技（深圳）有限公司 获取信息的方法和系统
CN104243216A (zh) * 2014-09-28 2014-12-24 北京国双科技有限公司 集群服务器的维护方法及装置
CN105955865A (zh) * 2016-04-29 2016-09-21 浪潮(北京)电子信息产业有限公司 一种针对k-db数据库的监控方法及系统
CN107302476B (zh) * 2017-08-04 2021-07-09 上海爱数信息技术股份有限公司 一种测试异步交互系统的自动化测试方法与系统
CN107798556A (zh) * 2017-09-26 2018-03-13 上海连尚网络科技有限公司 用于更新状况记录的方法、设备和存储介质
CN107908488B (zh) * 2017-11-14 2021-12-07 中国银行股份有限公司 消息请求接口交互方法、装置、计算机设备及存储介质

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5737592A (en) * 1995-06-19 1998-04-07 International Business Machines Corporation Accessing a relational database over the Internet using macro language files
CN103412961A (zh) * 2013-09-04 2013-11-27 广东全通教育股份有限公司 一种实时导出海量数据报表的处理方法和系统
CN103457802A (zh) * 2013-09-09 2013-12-18 中国农业银行股份有限公司 一种信息传输系统及方法
CN206894667U (zh) * 2017-06-01 2018-01-16 湖南商学院 网络系统监控报表系统
CN107659443A (zh) * 2017-09-22 2018-02-02 天翼电子商务有限公司 一种实时业务的监控方法及其系统

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113220807A (zh) * 2021-04-01 2021-08-06 辽宁工程技术大学 一种遥感数据自动化发布与在线流程监控方法
CN113254994A (zh) * 2021-05-27 2021-08-13 平安普惠企业管理有限公司 数据库访问方法、装置、存储介质和计算机设备
CN113836160A (zh) * 2021-09-28 2021-12-24 上海市大数据股份有限公司 一种基于主从同步的数据流状态监控告警系统
CN113836160B (zh) * 2021-09-28 2024-01-23 上海市大数据股份有限公司 一种基于主从同步的数据流状态监控告警系统

Also Published As

Publication number Publication date
CN108847998B (zh) 2021-09-14
CN108847998A (zh) 2018-11-20

Similar Documents

Publication Publication Date Title
WO2019200750A1 (zh) 报表监控方法、装置、计算机设备和存储介质
US10901727B2 (en) Monitoring code sensitivity to cause software build breaks during software project development
US20210352099A1 (en) System for automatically discovering, enriching and remediating entities interacting in a computer network
US11620277B2 (en) Transaction processing at non-relational databases
Chyrun et al. Web Resource Changes Monitoring System Development.
US20090217240A1 (en) Script generation for graceful termination of a web enabled client by a web server
US20160004517A1 (en) SOFTWARE DEVELOPMENT IMPROVEMENT TOOL - iREVIEW
US20040205034A1 (en) Communication between intelligent agents and humans in a distributed system environment
US20080269921A1 (en) System and Method for Providing Support Assistance
CA3094542A1 (en) Management of programmatic and compliance workflows using robotic process automation
US11509950B2 (en) Systems and methods for controlling quality of content
US20230140918A1 (en) Intelligent automated computing system incident management
CN111679851B (zh) 需求代码管理方法、装置、系统与计算机可读存储介质
US20220229856A1 (en) Data processing systems and methods for automatically detecting and documenting privacy-related aspects of computer software
CN110210192A (zh) 信息管理方法、装置、设备及可读存储介质
CN115576978A (zh) 一种业务处理请求的响应方法、装置、系统及介质
CN112559638B (zh) 数据同步的方法、装置、设备和存储介质
US11657030B2 (en) Multi-dimensional data tagging and reuse
CN115080433A (zh) 基于流量回放的测试方法及装置
US20180218628A1 (en) Information technology user behavior monitoring rule generation
TWI696080B (zh) 基於檢核資料庫日誌檔的資訊安全管控系統及其實施方法
US20160373402A1 (en) Information Management and Notification System
Rahmel et al. Testing a site with ApacheBench, JMeter, and Selenium
CN113190531A (zh) 一种数据库迁移方法、装置、设备和存储介质
JP5569438B2 (ja) あいまい記述自動検出装置及びその方法

Legal Events

Date Code Title Description
NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 25.02.2021)

122 Ep: pct application non-entry in european phase

Ref document number: 18915006

Country of ref document: EP

Kind code of ref document: A1