CN112015647A - Configuration item monitoring method and device, computer equipment and storage medium - Google Patents

Configuration item monitoring method and device, computer equipment and storage medium Download PDF

Info

Publication number
CN112015647A
CN112015647A CN202010879117.7A CN202010879117A CN112015647A CN 112015647 A CN112015647 A CN 112015647A CN 202010879117 A CN202010879117 A CN 202010879117A CN 112015647 A CN112015647 A CN 112015647A
Authority
CN
China
Prior art keywords
configuration file
item
configuration
target
version
Prior art date
Legal status (The legal status 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 status listed.)
Pending
Application number
CN202010879117.7A
Other languages
Chinese (zh)
Inventor
王自挺
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
OneConnect Smart Technology Co Ltd
OneConnect Financial Technology Co Ltd Shanghai
Original Assignee
OneConnect Financial Technology Co Ltd Shanghai
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 OneConnect Financial Technology Co Ltd Shanghai filed Critical OneConnect Financial Technology Co Ltd Shanghai
Priority to CN202010879117.7A priority Critical patent/CN112015647A/en
Publication of CN112015647A publication Critical patent/CN112015647A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/36Preventing errors by testing or debugging software
    • G06F11/3668Software testing
    • G06F11/3672Test management
    • G06F11/3688Test management for test execution, e.g. scheduling of test suites
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/36Preventing errors by testing or debugging software
    • G06F11/3668Software testing
    • G06F11/3672Test management
    • G06F11/3692Test management for test results analysis
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/60Software deployment
    • G06F8/65Updates
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/70Software maintenance or management
    • G06F8/71Version control; Configuration management

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Software Systems (AREA)
  • Computer Hardware Design (AREA)
  • Quality & Reliability (AREA)
  • Computer Security & Cryptography (AREA)
  • Stored Programmes (AREA)

Abstract

The application relates to the technical field of computers, and provides a configuration item monitoring method, a configuration item monitoring device, computer equipment and a storage medium. The method comprises the following steps: and responding to the starting operation of the configuration item monitoring tool, starting a preset system new version release signal monitoring thread, acquiring a target configuration file of a version to be released of each subsystem when a system new version release signal is monitored, searching a reference configuration file corresponding to the target configuration file, identifying a difference item between the target configuration file and the corresponding reference configuration file, acquiring a difference item identification result, collecting the difference item identification result in each subsystem, and acquiring a configuration item monitoring result of the version to be released of the system. The method is convenient for realizing the adjustment of the configuration data before the release of the new version, thereby reducing the online problem of the new version caused by the misoperation of manual configuration modification, effectively making up the accuracy of the configuration data of the points which cannot be covered in the test regression stage after the system version is updated, and being beneficial to improving the stability of the system in the operation process on the whole.

Description

Configuration item monitoring method and device, computer equipment and storage medium
Technical Field
The present application relates to the field of computer technologies, and in particular, to a method and an apparatus for monitoring configuration items, a computer device, and a storage medium.
Background
For a system with complex functions, processing of each service is generally realized through the cooperation of a plurality of subsystems. Taking the loan system as an example, it includes work-in, workflow, wind control, approval, bank docking, and so on. The configuration items of each subsystem are also quite various. Once configuration items are modified due to human mishandling, it is likely to cause a very serious production problem.
Due to the fact that complex systems relate to subsystems and are configured in a large number, complete test regression cannot be directly conducted in a production environment, and therefore the problem of low stability exists in the operation process of the systems.
Disclosure of Invention
In view of the foregoing, there is a need to provide a configuration item monitoring method, apparatus, computer device and storage medium that can help improve stability during system operation.
A method of configuration item monitoring, the method comprising:
responding to the starting operation of the configuration item monitoring tool, and starting a preset system new version release signal monitoring thread;
when a system new version release signal is monitored, acquiring a target configuration file of a version to be released of each subsystem;
searching a reference configuration file corresponding to the target configuration file;
identifying a difference item in the target configuration file and the corresponding reference configuration file to obtain a difference item identification result;
and collecting the identification results of the difference items in each subsystem to obtain the monitoring result of the configuration item of the version to be released of the system.
In one embodiment, identifying the difference item between the target configuration file and the corresponding reference configuration file, and obtaining the identification result of the difference item includes:
identifying a difference item in the target configuration file and the corresponding reference configuration file, and acquiring data processing logic corresponding to the difference item in the new version data to be released;
when the difference item accords with the data processing logic, judging that the difference item belongs to a normal change difference item;
when the difference item does not accord with the data processing logic, judging that the difference item belongs to the abnormal change difference item;
and obtaining a difference item identification result according to the normal change difference item and the abnormal change difference item.
In one embodiment, after obtaining the difference item identification result according to the normal change difference item and the abnormal change difference item, the method further includes:
updating the abnormal change difference item in the target configuration file by taking the reference configuration file as reference data to obtain an update release configuration file;
and releasing the new version of the system based on the updated release configuration file.
In one embodiment, after obtaining the difference item identification result according to the normal change difference item and the abnormal change difference item, the method further includes:
updating the normal change difference item in the basic configuration file by taking the target configuration file as reference data to obtain an updated basic configuration file;
and detecting the configuration file of the released system new version at regular time based on the updated reference configuration file.
In one embodiment, the step of searching for the reference configuration file corresponding to the target configuration file comprises:
acquiring running data of each historical version of the system;
according to the operation data, obtaining stability evaluation results corresponding to the historical versions, and screening the historical version with the optimal stability evaluation result as a reference version;
and calling a configuration file export component to export a reference configuration file corresponding to the target configuration file from the configuration files of the reference versions of the subsystems.
In one embodiment, invoking the configuration file export component to export a reference configuration file corresponding to the target configuration file from the configuration files of the reference versions of the subsystems comprises:
when the subsystem carries a configuration data exportable identifier, searching a target json configuration file corresponding to a target configuration file from a json (JavaScript Object Notation) configuration file library of a subsystem reference version, calling a configuration file exporting assembly, exporting the target json configuration file and marking the target json configuration file as the reference configuration file of the subsystem;
when the subsystem carries a configuration data exportable identifier, searching an sql (Structured Query Language) script of a configuration table corresponding to a target configuration file from a subsystem reference version database, calling a configuration file exportation component, exporting an sql script mark and marking the sql script mark as a subsystem reference configuration file.
In one embodiment, the method further comprises:
responding to the screening operation of the subsystem configuration items, and determining the configuration items to be monitored of each subsystem;
marking the configuration items to be monitored;
when a system new version release signal is monitored, acquiring a target configuration file of a version to be released of each subsystem and a reference configuration file of each subsystem comprises the following steps:
and when a new version of the system is monitored to release a signal, acquiring a target configuration file matched with the identifier and a target configuration file matched with the identifier according to the identifier of each configuration item to be monitored.
A configuration item monitoring apparatus, the apparatus comprising:
the release signal monitoring module is used for responding to the starting operation of the configuration item monitoring tool and starting a preset system new version release signal monitoring thread;
the target configuration file acquisition module is used for acquiring a target configuration file of a version to be released of each subsystem when a system new version release signal is monitored;
the reference configuration file searching module is used for searching a reference configuration file corresponding to the target configuration file;
the difference item identification module is used for identifying the difference items in the target configuration file and the corresponding reference configuration file to obtain a difference item identification result;
and the result collecting module is used for collecting the identification results of the difference items in the subsystems to obtain the monitoring results of the configuration items of the to-be-released version of the system.
A computer device comprising a memory and a processor, the memory storing a computer program, the processor implementing the following steps when executing the computer program:
responding to the starting operation of the configuration item monitoring tool, and starting a preset system new version release signal monitoring thread;
when a system new version release signal is monitored, acquiring a target configuration file of a version to be released of each subsystem;
searching a reference configuration file corresponding to the target configuration file;
identifying a difference item in the target configuration file and the corresponding reference configuration file to obtain a difference item identification result;
and collecting the identification results of the difference items in each subsystem to obtain the monitoring result of the configuration item of the version to be released of the system.
A computer-readable storage medium, on which a computer program is stored which, when executed by a processor, carries out the steps of:
responding to the starting operation of the configuration item monitoring tool, and starting a preset system new version release signal monitoring thread;
when a system new version release signal is monitored, acquiring a target configuration file of a version to be released of each subsystem;
searching a reference configuration file corresponding to the target configuration file;
identifying a difference item in the target configuration file and the corresponding reference configuration file to obtain a difference item identification result;
and collecting the identification results of the difference items in each subsystem to obtain the monitoring result of the configuration item of the version to be released of the system.
The configuration item monitoring method, the configuration item monitoring device, the computer equipment and the storage medium realize monitoring of the configuration item of the updated version of the system based on the configuration item monitoring tool, respond to the starting operation of the configuration item monitoring tool, start the monitoring thread to monitor the signal released by the new version of the system, when the signal released by the new version of the system is monitored, obtain the target configuration file of the version to be released of each subsystem, search the corresponding reference configuration file according to the target configuration file to obtain the comparison object of the target configuration file, collect the identification results of the difference items in each subsystem by identifying the difference items of the target configuration file and the corresponding reference configuration file to obtain the monitoring results of the configuration item of the version to be released of the system, and can conveniently realize the adjustment of the configuration data before the new version is released based on the monitoring results of the configuration items for the follow-up, therefore, the online problem of the new version caused by the misoperation of manual configuration modification is reduced, the accuracy of configuration data of points which cannot be covered in the test regression stage after the system version is updated is effectively compensated, and the stability of the system in the operation process is improved integrally.
Drawings
FIG. 1 is a diagram of an application environment of a configuration item monitoring method in one embodiment;
FIG. 2 is a flow diagram illustrating a method for configuration item monitoring in one embodiment;
FIG. 3 is a schematic flow chart diagram of a configuration item monitoring method in another embodiment;
FIG. 4 is a schematic flow chart diagram illustrating a configuration item monitoring method according to yet another embodiment;
FIG. 5 is a block diagram showing the configuration of a configuration item monitoring apparatus according to an embodiment;
FIG. 6 is a diagram illustrating an internal structure of a computer device according to an embodiment.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.
The method for monitoring the configuration items is implemented based on a configuration item monitoring tool, as shown in fig. 1, taking an example that the configuration item monitoring tool is applied to a terminal, the configuration item monitoring tool responds to a start operation of the configuration item monitoring tool, starts a preset system new version release signal monitoring thread, when monitoring a system new version release signal, acquires a target configuration file of a version to be released of each subsystem, searches a reference configuration file corresponding to the target configuration file by the configuration item monitoring tool, identifies a difference item in the target configuration file and the corresponding reference configuration file, obtains a difference item identification result, collects the difference item identification result in each subsystem, obtains a configuration item monitoring result of the version to be released of the system, generates a monitoring report, and pushes the monitoring report. The terminal may be, but is not limited to, various personal computers, notebook computers, smart phones, tablet computers, and portable wearable devices.
It is understood that the configuration item monitoring tool can also be applied to a server, and can also be applied to a system comprising a terminal and the server, and the configuration item monitoring method is realized through the interaction of the terminal and the server. The server may be implemented as a stand-alone server or as a server cluster consisting of a plurality of servers.
In one embodiment, as shown in fig. 2, a configuration item monitoring method is provided, which is described by taking the method as an example applied to the configuration item monitoring tool in fig. 1, and includes the following steps 202 to 210.
Step 202, responding to the starting operation of the configuration item monitoring tool, starting a preset system new version release signal monitoring thread.
The configuration item monitoring tool is a tool which is configured in the system in advance and is used for monitoring the monitoring items of the system. Specifically, the configuration item monitoring tool can be configured at a terminal or a server.
The configuration item monitoring tool starting operation means that a user triggers a configuration item monitoring tool starting program to start the operation of the configuration item monitoring tool.
In the embodiment, a signal monitoring thread is issued based on the new version of the system in the configuration item monitoring tool, and the version update state of the system is monitored.
The system can be an integrated system comprising a plurality of subsystems, the subsystems can be distinguished according to different functions, for example, each subsystem in the loan system can respectively realize functions of work entering, workflow, wind control, examination and approval, bank butt joint and the like. When various functions of the system new version release, namely release preparation conditions of the subsystems are met, system new version release information is generated, and the system new version release comprises release of new versions of the subsystems.
And 204, when a system new version release signal is monitored, acquiring a target configuration file of a version to be released of each subsystem.
When monitoring that a new version of the system issues an instruction, identifying a plurality of subsystem identifications contained in the system, and generating a configuration item export instruction carrying the subsystem identifications. And the configuration item export component in the configuration item monitoring tool responds to the configuration item export instruction to export the target configuration file of each subsystem. The acquisition process of the target configuration file to be issued of each subsystem comprises the following steps: and extracting the target configuration files corresponding to the subsystems corresponding to the new version to be released according to the subsystems corresponding to the target configuration files.
In the embodiment, a file export path of a target configuration file is determined by a configuration data recording mode of a subsystem, and the target configuration file corresponding to each subsystem in the new version to be released is exported according to the file export path.
The data recording mode is configured, so that a file export path of a corresponding target configuration file can be rapidly obtained, and the data processing efficiency is improved.
Step 206, find the reference configuration file corresponding to the target configuration file.
The export process of the reference configuration file of each subsystem comprises the following steps: and deriving a reference configuration file of each subsystem from reference historical version data of the system, wherein the reference historical version is determined by analyzing the stability of the historical version.
In one embodiment, as shown in fig. 3, finding the reference profile corresponding to the target profile includes steps 302 to 306.
Step 302, obtaining the operation data of each historical version of the system.
And 304, obtaining stability evaluation results corresponding to the historical versions according to the operation data, and screening the historical version with the optimal stability evaluation result as a reference version.
Step 306, calling a configuration file export component, and exporting a reference configuration file corresponding to the target configuration file from the configuration files of the reference versions of the subsystems.
During multiple version updates of the system, there may be multiple historical versions. Specifically, a reference version may be determined from the plurality of historical versions, and then the configuration file corresponding to the configuration item may be acquired from the configuration file in the reference version as the reference configuration file. The reference configuration file is used for calibrating the configuration data in the newly released version and performing timing detection on the configuration data of the system after the new version is released.
It can be understood that in other application scenarios, the last version of the system may be directly used as the reference version, or the reference version may be selected based on the stability of the historical version, which may be specifically set according to actual needs. By selecting the reference version based on the stability, a more reasonable and effective reference profile can be obtained.
In one embodiment, as shown in fig. 4, invoking the profile export component to export a base profile corresponding to the target profile from the profiles of the base versions of the subsystems comprises steps 402 and 404.
Step 402, when the subsystem carries the configuration data exportable identifier, searching a target json configuration file corresponding to the target configuration file from a json configuration file library of the subsystem reference version, calling a configuration file exporting component, exporting the target json configuration file and marking the target json configuration file as the subsystem reference configuration file.
And 404, when the subsystem carries a configuration data exportable identifier, searching the sql script of the configuration table corresponding to the target configuration file from the subsystem reference version database, calling a configuration file exporting component, exporting the sql script mark and marking the sql script mark as the subsystem reference configuration file.
In the embodiment, the system configuration type of each subsystem in the reference version is obtained; when the system configuration type is a system with configuration data exportable, namely the system carries configuration data exportable identification, exporting a json configuration file of the subsystem, and marking the json configuration file as a reference configuration file of the subsystem;
when the system configuration type is a system with configuration data stored in a database, namely the system carries configuration data exportable identifiers, exporting the sql script of the configuration table of the subsystem from the database, and marking the sql script as a reference configuration file of the subsystem.
Specifically, for a system where configuration data is derivable: the json profile of the existing version is exported and compared to the json profile of the previous reference version. If the difference exists, the difference file is screened, if the difference belongs to normal change, the reference version configuration file is updated, and if the difference belongs to abnormal change, the configuration is repaired. For systems where configuration data is stored in a database: the sql script of the configuration table of the existing version is exported and compared with the sql script of the previous reference version. And if the difference exists, alarming. And screening the difference sql, if the difference sql belongs to normal change, updating the standard version sql script, and if the difference sql belongs to abnormal change, repairing the sql configuration. By separately processing different system configuration types, the monitoring and calibration of configuration items of different types of systems can be met.
And 208, identifying the difference items in the target configuration file and the corresponding reference configuration file to obtain a difference item identification result.
And comparing the target configuration file with the corresponding reference configuration file based on a configuration item analysis component in the configuration item monitoring tool, and identifying a difference item.
Due to different system architectures of the subsystems corresponding to the new version to be released, formats of configuration files of the subsystems may have differences, and therefore, the target configuration files and the reference configuration files need to be compared for the subsystems individually. Specifically, the comparison between the target configuration file and the reference configuration file is a comparison of full data, and when any data item is different, the data item needs to be marked as a difference item to be reported so as to perform corresponding processing on the difference item.
The difference items comprise normal change difference items which accord with the preset data processing logic and abnormal change difference items which do not accord with the preset data processing logic.
And step 210, collecting the identification results of the difference items in each subsystem to obtain the monitoring result of the configuration item of the version to be released of the system.
After the target configuration files of the subsystems are compared with the corresponding reference configuration files, the identification results of the difference items in the subsystems are collected through data summarization, and configuration item monitoring reports are generated and reported.
The system configuration item monitoring is realized through the configuration item monitoring tool, on one hand, the online problem caused by manual configuration modification misoperation can be greatly reduced, the monitoring of the configuration item is triggered before each edition sending, whether the configuration item is abnormally changed or not is checked, the change possibility caused by manual error is reduced to the minimum, and on the other hand, all configuration changes cannot be covered due to general regression testing. The configuration item monitoring tool can effectively make up points which cannot be covered in the test regression stage, and the stability of the system is improved.
In an embodiment, the configuration item monitoring tool includes a system version update detection component, a configuration item export component, a configuration item analysis component, and a configuration item monitoring reporting component.
And the configuration item monitoring tool is called by the component to realize system configuration item monitoring. Specifically, when the configuration item monitoring tool is started, the system version updating detection component is called, a signal monitoring thread is issued based on a system new version in the system version updating detection component, a system new version issuing signal is monitored, when the system new version issuing signal is monitored, the configuration item export component is called to export a target configuration file of a version to be issued of each subsystem, a reference configuration file corresponding to the target configuration file is searched, the exported target configuration file and the corresponding reference configuration file are transmitted to the configuration item analysis component, a difference item identification result is obtained by identifying a difference item in the target configuration file and the corresponding reference configuration file through the configuration item analysis component, and when the difference item identification analysis of each target configuration file and the corresponding reference configuration file is finished, the configuration item monitoring report component is called to collect the difference item identification result in each subsystem, and obtaining a configuration item monitoring result of the version to be released of the system, and generating and pushing a configuration item monitoring report based on the configuration item monitoring result.
The configuration item monitoring method monitors the configuration item of the updated version of the system based on the configuration item monitoring tool, responds to the start operation of the configuration item monitoring tool, starts a monitoring thread to monitor the signal released by the new version of the system, acquires the target configuration file of the version to be released of each subsystem when the signal released by the new version of the system is monitored, searches the corresponding reference configuration file according to the target configuration file to obtain the comparison object of the target configuration file, collects the identification result of the difference item in each subsystem by identifying the difference item of the target configuration file and the corresponding reference configuration file to obtain the monitoring result of the configuration item of the version to be released of the system, and can conveniently realize the adjustment of the configuration data before the new version is released based on the monitoring result of the configuration item by monitoring the difference item, therefore, the online problem of the new version caused by the misoperation of manual configuration modification is reduced, the accuracy of configuration data of points which cannot be covered in the test regression stage after the system version is updated is effectively compensated, and the stability of the system in the operation process is improved integrally.
In one embodiment, identifying the difference item between the target configuration file and the corresponding reference configuration file, and obtaining the identification result of the difference item includes:
and identifying the difference items in the target configuration file and the corresponding reference configuration file, and acquiring the data processing logic corresponding to the difference items in the new version data to be released.
And when the difference item accords with the data processing logic, judging that the difference item belongs to the normal change difference item.
And when the difference item does not accord with the data processing logic, judging that the difference item belongs to the abnormal change difference item.
And obtaining a difference item identification result according to the normal change difference item and the abnormal change difference item.
In one embodiment, the configuration item analysis component called by the configuration item monitoring tool obtains the data processing logic corresponding to the difference item in the new version to be released based on the difference item in the comparison result, determines that the difference item belongs to normal change when the difference item conforms to the data processing logic, and determines that the difference item belongs to abnormal change when the difference item does not conform to the data processing logic. By calling the data processing logic, whether the difference item is changed according with requirements based on actual needs or is changed by mistake due to misoperation of workers can be determined, the type of the change can be conveniently changed, and the difference item in the target configuration file or the reference configuration file can be further processed.
In one embodiment, after obtaining the difference item identification result according to the normal change difference item and the abnormal change difference item, the method further includes: and updating the abnormal change difference item in the target configuration file by taking the reference configuration file as reference data to obtain an update release configuration file. And releasing the new version of the system based on the updated release configuration file.
Specifically, the abnormal change difference item is generally an erroneous change due to an erroneous operation by a worker. And updating the target configuration file by referring to the reference configuration file based on the difference item of the abnormal change in the target configuration file, so that the configuration item which does not conform to the data processing logic of the new version to be released can be found and corrected in time.
In one embodiment, after obtaining the difference item identification result according to the normal change difference item and the abnormal change difference item, the method further includes: and updating the normal change difference item in the basic configuration file by taking the target configuration file as reference data to obtain an updated basic configuration file. And detecting the configuration file of the released system new version at regular time based on the updated reference configuration file.
For the normally changed difference items, the benchmark configuration file can be updated by referring to the target configuration file, so that the updated benchmark configuration file can be suitable for the detection of the system configuration items after the new version is released. The system configuration item detection after the new version is released can be a detection task configured to be executed at regular time according to needs.
The detection of the configuration file of the released system new version at regular time can be realized by the monitoring component, and the monitoring component can be responsible for calling the export tool regularly, exporting the configuration item and synchronizing the result to the configuration item monitoring report component.
In one embodiment, the system configuration item monitoring tool processes the difference items of the abnormal change and the difference items of the normal change by calling an abnormal item processing component preset in the tool. The specific treatment process comprises the following steps: calling an abnormal item processing component to update the target configuration file for the abnormal changed difference item to obtain an update release configuration file; based on the updated configuration file, releasing a new version of the system; calling an abnormal item processing component to update the reference configuration file for the normally changed difference item to obtain an updated reference configuration file; and detecting the configuration file of the released system new version at regular time based on the updated reference configuration file. Based on the processing of two different types of abnormal items, an accurate release configuration file for the release of the new version and an accurate reference configuration file for system detection can be obtained.
In one embodiment, the method further comprises: and responding to the screening operation of the subsystem configuration items, and determining the configuration items to be monitored of each subsystem. And marking the configuration items to be monitored.
When a system new version release signal is monitored, acquiring a target configuration file of a version to be released of each subsystem and a reference configuration file of each subsystem comprises the following steps: and when a new version of the system is monitored to release a signal, acquiring a target configuration file matched with the identifier and a target configuration file matched with the identifier according to the identifier of each configuration item to be monitored.
In the embodiment, the monitoring items comprise field setting, interface parameter configuration, flow setting and the like, the screening of the configuration items can be realized by configuring a filter in a configuration item monitoring tool, the configuration items needing monitoring can be flexibly configured, the configuration items which do not need monitoring or change frequently are filtered, and the occurrence of false alarm is reduced.
In an embodiment, the configuration item monitoring tool further includes an information feedback component, configured to feed back monitoring information to the terminal when the configuration item is not abnormal. For example, when the target configuration file of each subsystem is the same as the reference configuration file, the information that the new version configuration information is not abnormal is fed back.
It can be understood that for a subsystem whose target configuration file is not different from the reference configuration file, there is no problem in characterizing the configuration items in the target configuration file, and the corresponding reference configuration file can be used to perform timing detection on the system. When all subsystems have no problem, the detection of the new version to be released can be prompted to be finished by feeding back information that the configuration information of the new version has no abnormality, and specifically, the information can be fed back in a form of a configuration item monitoring report or can be simply fed back in a form of a popup window and the like.
It should be understood that, although the steps in the flowcharts are shown in sequence as indicated by the arrows, the steps are not necessarily performed in sequence as indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least a part of the steps in each of the flowcharts described above may include multiple steps or multiple stages, which are not necessarily performed at the same time, but may be performed at different times, and the order of performing the steps or stages is not necessarily sequential, but may be performed alternately or alternately with other steps or at least a part of the steps or stages in other steps.
In one embodiment, as shown in fig. 5, there is provided a configuration item monitoring apparatus including: a signal-issuing monitoring module 502, a target configuration file obtaining module 504, a reference configuration file searching module 506, a difference item identifying module 508 and a result aggregating module 510, wherein:
and the issued signal monitoring module 502 is configured to respond to a configuration item monitoring tool start operation and start a preset system new version issued signal monitoring thread.
And a target configuration file obtaining module 504, configured to obtain a target configuration file of a version to be released of each subsystem when a system new version release signal is monitored.
A reference configuration file searching module 506, configured to search a reference configuration file corresponding to the target configuration file.
A difference item identification module 508, configured to identify a difference item in the target configuration file and the corresponding reference configuration file, to obtain a difference item identification result;
and the result collecting module 510 is configured to collect the difference item identification results in the subsystems to obtain the configuration item monitoring result of the to-be-released version of the system.
In one embodiment, the difference item identification module is further configured to identify a difference item in the target configuration file and the corresponding reference configuration file, and acquire a data processing logic corresponding to the difference item in the new version data to be released; when the difference item accords with the data processing logic, judging that the difference item belongs to a normal change difference item; when the difference item does not accord with the data processing logic, judging that the difference item belongs to the abnormal change difference item; and obtaining a difference item identification result according to the normal change difference item and the abnormal change difference item.
In one embodiment, the configuration item monitoring device further includes an abnormal change difference item processing module, configured to update the abnormal change difference item in the target configuration file with the reference configuration file as reference data, so as to obtain an update release configuration file; and releasing the new version of the system based on the updated release configuration file.
In one embodiment, the configuration item monitoring device further includes a normal change difference item processing module, configured to update a normal change difference item in the benchmark configuration file with the target configuration file as reference data, so as to obtain an updated benchmark configuration file; and detecting the configuration file of the released system new version at regular time based on the updated reference configuration file.
In one embodiment, the reference configuration file searching module is further configured to obtain operation data of each historical version of the system; according to the operation data, obtaining stability evaluation results corresponding to the historical versions, and screening the historical version with the optimal stability evaluation result as a reference version; and calling a configuration file export component to export a reference configuration file corresponding to the target configuration file from the configuration files of the reference versions of the subsystems.
In one embodiment, the reference configuration file searching module is further configured to search a target json configuration file corresponding to the target configuration file from a json configuration file library of the subsystem reference version when the subsystem carries the configuration data exportable identifier; calling a configuration file export component, exporting a target json configuration file and marking the target json configuration file as a reference configuration file of the subsystem; when the subsystem carries the configuration data exportable identifier, searching the sql script of the configuration table corresponding to the target configuration file from the subsystem reference version database, calling the configuration file exporting component, exporting the sql script mark and marking the sql script mark as the subsystem reference configuration file.
In one embodiment, the configuration item monitoring apparatus further includes a configuration item screening module, configured to determine a configuration item to be monitored of each subsystem in response to a subsystem configuration item screening operation; marking the configuration items to be monitored; and the target configuration file acquisition module is also used for acquiring a target configuration file matched with the identifier and a target configuration file matched with the identifier according to the identifier of each configuration item to be monitored when a system new version release signal is monitored.
The configuration item monitoring device monitors the configuration item of the updated version of the system based on the configuration item monitoring tool, responds to the start operation of the configuration item monitoring tool, starts the monitoring thread to monitor the signal released by the new version of the system, acquires the target configuration file of the version to be released of each subsystem when the signal released by the new version of the system is monitored, searches the corresponding reference configuration file according to the target configuration file to obtain the comparison object of the target configuration file, collects the identification result of the difference item in each subsystem by identifying the difference item of the target configuration file and the corresponding reference configuration file to obtain the monitoring result of the configuration item of the version to be released of the system, and can conveniently realize the adjustment of the configuration data before the new version is released based on the monitoring result of the configuration item by monitoring the difference item, therefore, the online problem of the new version caused by the misoperation of manual configuration modification is reduced, the accuracy of configuration data of points which cannot be covered in the test regression stage after the system version is updated is effectively compensated, and the stability of the system in the operation process is improved integrally.
For specific limitations of the configuration item monitoring device, reference may be made to the above limitations of the configuration item monitoring method, which are not described herein again. The modules in the configuration item monitoring device can be wholly or partially realized by software, hardware and a combination thereof. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.
In one embodiment, a computer device is provided, which may be a terminal configured with a configuration item monitoring tool, and the internal structure thereof may be as shown in fig. 6. The computer device includes a processor, a memory, a communication interface, a display screen, and an input device connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of an operating system and computer programs in the non-volatile storage medium. The communication interface of the computer device is used for carrying out wired or wireless communication with an external terminal, and the wireless communication can be realized through WIFI, an operator network, NFC (near field communication) or other technologies. The computer program is executed by a processor to implement a configuration item monitoring method. The display screen of the computer equipment can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer equipment can be a touch layer covered on the display screen, a key, a track ball or a touch pad arranged on the shell of the computer equipment, an external keyboard, a touch pad or a mouse and the like.
Those skilled in the art will appreciate that the architecture shown in fig. 6 is merely a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the computing devices to which the disclosed aspects apply, as particular computing devices may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.
In one embodiment, a computer device is provided, comprising a memory and a processor, the memory having a computer program stored therein, the processor implementing the following steps when executing the computer program:
responding to the starting operation of the configuration item monitoring tool, and starting a preset system new version release signal monitoring thread; when a system new version release signal is monitored, acquiring a target configuration file of a version to be released of each subsystem; searching a reference configuration file corresponding to the target configuration file; identifying a difference item in the target configuration file and the corresponding reference configuration file to obtain a difference item identification result; and collecting the identification results of the difference items in each subsystem to obtain the monitoring result of the configuration item of the version to be released of the system.
In one embodiment, the processor, when executing the computer program, further performs the steps of:
identifying a difference item in the target configuration file and the corresponding reference configuration file, and acquiring data processing logic corresponding to the difference item in the new version data to be released; when the difference item accords with the data processing logic, judging that the difference item belongs to a normal change difference item; when the difference item does not accord with the data processing logic, judging that the difference item belongs to the abnormal change difference item; and obtaining a difference item identification result according to the normal change difference item and the abnormal change difference item.
In one embodiment, the processor, when executing the computer program, further performs the steps of:
updating the abnormal change difference item in the target configuration file by taking the reference configuration file as reference data to obtain an update release configuration file; and releasing the new version of the system based on the updated release configuration file.
In one embodiment, the processor, when executing the computer program, further performs the steps of:
updating the normal change difference item in the basic configuration file by taking the target configuration file as reference data to obtain an updated basic configuration file; and detecting the configuration file of the released system new version at regular time based on the updated reference configuration file.
In one embodiment, the processor, when executing the computer program, further performs the steps of:
acquiring running data of each historical version of the system; according to the operation data, obtaining stability evaluation results corresponding to the historical versions, and screening the historical version with the optimal stability evaluation result as a reference version; and calling a configuration file export component to export a reference configuration file corresponding to the target configuration file from the configuration files of the reference versions of the subsystems.
In one embodiment, the processor, when executing the computer program, further performs the steps of:
when the subsystem carries a configuration data exportable identifier, searching a target json configuration file corresponding to the target configuration file from a json configuration file library of a subsystem reference version, calling a configuration file exporting component, exporting the target json configuration file and marking the target json configuration file as the reference configuration file of the subsystem; when the subsystem carries the configuration data exportable identifier, searching the sql script of the configuration table corresponding to the target configuration file from the subsystem reference version database, calling the configuration file exporting component, exporting the sql script mark and marking the sql script mark as the subsystem reference configuration file.
In one embodiment, the processor, when executing the computer program, further performs the steps of:
responding to the screening operation of the subsystem configuration items, and determining the configuration items to be monitored of each subsystem; marking the configuration items to be monitored; and when a new version of the system is monitored to release a signal, acquiring a target configuration file matched with the identifier and a target configuration file matched with the identifier according to the identifier of each configuration item to be monitored.
In one embodiment, a computer-readable storage medium is provided, having a computer program stored thereon, which when executed by a processor, performs the steps of:
responding to the starting operation of the configuration item monitoring tool, and starting a preset system new version release signal monitoring thread; when a system new version release signal is monitored, acquiring a target configuration file of a version to be released of each subsystem; searching a reference configuration file corresponding to the target configuration file; identifying a difference item in the target configuration file and the corresponding reference configuration file to obtain a difference item identification result; and collecting the identification results of the difference items in each subsystem to obtain the monitoring result of the configuration item of the version to be released of the system.
In one embodiment, the computer program when executed by the processor further performs the steps of:
identifying a difference item in the target configuration file and the corresponding reference configuration file, and acquiring data processing logic corresponding to the difference item in the new version data to be released; when the difference item accords with the data processing logic, judging that the difference item belongs to a normal change difference item; when the difference item does not accord with the data processing logic, judging that the difference item belongs to the abnormal change difference item; and obtaining a difference item identification result according to the normal change difference item and the abnormal change difference item.
In one embodiment, the computer program when executed by the processor further performs the steps of:
updating the abnormal change difference item in the target configuration file by taking the reference configuration file as reference data to obtain an update release configuration file; and releasing the new version of the system based on the updated release configuration file.
In one embodiment, the computer program when executed by the processor further performs the steps of:
updating the normal change difference item in the basic configuration file by taking the target configuration file as reference data to obtain an updated basic configuration file; and detecting the configuration file of the released system new version at regular time based on the updated reference configuration file.
In one embodiment, the computer program when executed by the processor further performs the steps of:
acquiring running data of each historical version of the system; according to the operation data, obtaining stability evaluation results corresponding to the historical versions, and screening the historical version with the optimal stability evaluation result as a reference version; and calling a configuration file export component to export a reference configuration file corresponding to the target configuration file from the configuration files of the reference versions of the subsystems.
In one embodiment, the computer program when executed by the processor further performs the steps of:
when the subsystem carries a configuration data exportable identifier, searching a target json configuration file corresponding to the target configuration file from a json configuration file library of a subsystem reference version, calling a configuration file exporting component, exporting the target json configuration file and marking the target json configuration file as the reference configuration file of the subsystem; when the subsystem carries the configuration data exportable identifier, searching the sql script of the configuration table corresponding to the target configuration file from the subsystem reference version database, calling the configuration file exporting component, exporting the sql script mark and marking the sql script mark as the subsystem reference configuration file.
In one embodiment, the computer program when executed by the processor further performs the steps of:
responding to the screening operation of the subsystem configuration items, and determining the configuration items to be monitored of each subsystem; marking the configuration items to be monitored; and when a new version of the system is monitored to release a signal, acquiring a target configuration file matched with the identifier and a target configuration file matched with the identifier according to the identifier of each configuration item to be monitored.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware instructions of a computer program, which can be stored in a non-volatile computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. Any reference to memory, storage, database or other medium used in the embodiments provided herein can include at least one of non-volatile and volatile memory. Non-volatile Memory may include Read-Only Memory (ROM), magnetic tape, floppy disk, flash Memory, optical storage, or the like. Volatile Memory can include Random Access Memory (RAM) or external cache Memory. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM), among others.
The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
The above examples only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present patent shall be subject to the appended claims.

Claims (10)

1. A method for configuration item monitoring, the method comprising:
responding to the starting operation of the configuration item monitoring tool, and starting a preset system new version release signal monitoring thread;
when a system new version release signal is monitored, acquiring a target configuration file of a version to be released of each subsystem;
searching a reference configuration file corresponding to the target configuration file;
identifying a difference item in the target configuration file and the corresponding reference configuration file to obtain a difference item identification result;
and collecting the identification results of the difference items in each subsystem to obtain the monitoring result of the configuration items of the to-be-released version of the system.
2. The method according to claim 1, wherein the identifying the difference item in the target profile and the corresponding reference profile, and obtaining a difference item identification result comprises:
identifying a difference item in the target configuration file and the corresponding reference configuration file, and acquiring a data processing logic corresponding to the difference item in the new version data to be released;
when the difference item conforms to the data processing logic, determining that the difference item belongs to a normal change difference item;
when the difference item does not conform to the data processing logic, determining that the difference item belongs to an abnormal change difference item;
and obtaining a difference item identification result according to the normal change difference item and the abnormal change difference item.
3. The method according to claim 2, further comprising, after obtaining a difference item identification result according to the normal change difference item and the abnormal change difference item:
updating the abnormal change difference item in the target configuration file by taking the reference configuration file as reference data to obtain an update release configuration file;
and releasing the new version of the system based on the updated release configuration file.
4. The method according to claim 2, further comprising, after obtaining a difference item identification result according to the normal change difference item and the abnormal change difference item:
updating the normal change difference item in the basic configuration file by taking the target configuration file as reference data to obtain an updated basic configuration file;
and detecting the configuration file of the released system new version at regular time based on the updated reference configuration file.
5. The method of claim 1, wherein the finding a reference profile corresponding to the target profile comprises:
acquiring running data of each historical version of the system;
obtaining stability evaluation results corresponding to the historical versions according to the operation data, and screening the historical version with the optimal stability evaluation result as a reference version;
and calling a configuration file export component, and exporting a reference configuration file corresponding to the target configuration file from the configuration file of the reference version of each subsystem.
6. The method of claim 5, wherein the invoking a profile export component that exports a baseline profile corresponding to the target profile from the profiles of the baseline versions of the subsystems comprises:
when the subsystem carries a configuration data exportable identifier, searching a target json configuration file corresponding to the target configuration file from a json configuration file library of a subsystem reference version; calling a configuration file export component, exporting the target json configuration file and marking the target json configuration file as a reference configuration file of the subsystem;
and when the subsystem carries a configuration data exportable identifier, searching an sql script of a configuration table corresponding to the target configuration file from a subsystem reference version database, calling a configuration file exportation component, exporting the sql script mark and marking the sql script mark as a reference configuration file of the subsystem.
7. The method of claim 1, further comprising:
responding to the screening operation of the subsystem configuration items, and determining the configuration items to be monitored of each subsystem;
marking each configuration item to be monitored;
when a system new version release signal is monitored, acquiring a target configuration file of a version to be released of each subsystem and a reference configuration file of each subsystem comprises the following steps:
and when a system new version release signal is monitored, acquiring a target configuration file matched with the identifier and a target configuration file matched with the identifier according to the identifier of each configuration item to be monitored.
8. A configuration item monitoring apparatus, the apparatus comprising:
the release signal monitoring module is used for responding to the starting operation of the configuration item monitoring tool and starting a preset system new version release signal monitoring thread;
the target configuration file acquisition module is used for acquiring a target configuration file of a version to be released of each subsystem when a system new version release signal is monitored;
the reference configuration file searching module is used for searching a reference configuration file corresponding to the target configuration file;
the difference item identification module is used for identifying the difference items in the target configuration file and the corresponding reference configuration file to obtain a difference item identification result;
and the result collecting module is used for collecting the identification results of the difference items in the subsystems to obtain the monitoring results of the configuration items of the to-be-released version of the system.
9. A computer device comprising a memory and a processor, the memory storing a computer program, characterized in that the processor, when executing the computer program, implements the steps of the method of any of claims 1 to 7.
10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method of any one of claims 1 to 7.
CN202010879117.7A 2020-08-27 2020-08-27 Configuration item monitoring method and device, computer equipment and storage medium Pending CN112015647A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202010879117.7A CN112015647A (en) 2020-08-27 2020-08-27 Configuration item monitoring method and device, computer equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010879117.7A CN112015647A (en) 2020-08-27 2020-08-27 Configuration item monitoring method and device, computer equipment and storage medium

Publications (1)

Publication Number Publication Date
CN112015647A true CN112015647A (en) 2020-12-01

Family

ID=73503365

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202010879117.7A Pending CN112015647A (en) 2020-08-27 2020-08-27 Configuration item monitoring method and device, computer equipment and storage medium

Country Status (1)

Country Link
CN (1) CN112015647A (en)

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112560028A (en) * 2020-12-24 2021-03-26 深圳昂楷科技有限公司 Method and device for protecting key file and server
CN112988280A (en) * 2021-04-22 2021-06-18 马上消费金融股份有限公司 Configuration data processing method and device
CN113127003A (en) * 2021-04-26 2021-07-16 平安普惠企业管理有限公司 Code abnormity warning method, device, equipment and storage medium
CN113515322A (en) * 2021-06-29 2021-10-19 平安养老保险股份有限公司 Application program loading method and device, computer equipment and readable storage medium
CN113703870A (en) * 2021-08-31 2021-11-26 平安普惠企业管理有限公司 Configuration file checking method, device, equipment and storage medium
CN113849370A (en) * 2021-09-24 2021-12-28 武汉联影医疗科技有限公司 Monitoring parameter adjusting method and device, computer equipment and storage medium
CN114915643A (en) * 2022-05-09 2022-08-16 北京交大微联科技有限公司 Configuration method, device, equipment and medium of railway signal centralized monitoring system
CN116520882A (en) * 2023-04-28 2023-08-01 北京交通大学 Unmanned aerial vehicle system-oriented configuration defect analysis method and system
WO2024093971A1 (en) * 2022-11-04 2024-05-10 中车长春轨道客车股份有限公司 Method and system for determining vehicle-mounted superconducting magnet monitoring system, and storage medium

Cited By (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112560028A (en) * 2020-12-24 2021-03-26 深圳昂楷科技有限公司 Method and device for protecting key file and server
CN112988280A (en) * 2021-04-22 2021-06-18 马上消费金融股份有限公司 Configuration data processing method and device
CN113127003A (en) * 2021-04-26 2021-07-16 平安普惠企业管理有限公司 Code abnormity warning method, device, equipment and storage medium
CN113515322A (en) * 2021-06-29 2021-10-19 平安养老保险股份有限公司 Application program loading method and device, computer equipment and readable storage medium
CN113515322B (en) * 2021-06-29 2022-11-01 平安养老保险股份有限公司 Application program loading method and device, computer equipment and readable storage medium
CN113703870A (en) * 2021-08-31 2021-11-26 平安普惠企业管理有限公司 Configuration file checking method, device, equipment and storage medium
CN113849370A (en) * 2021-09-24 2021-12-28 武汉联影医疗科技有限公司 Monitoring parameter adjusting method and device, computer equipment and storage medium
CN114915643A (en) * 2022-05-09 2022-08-16 北京交大微联科技有限公司 Configuration method, device, equipment and medium of railway signal centralized monitoring system
CN114915643B (en) * 2022-05-09 2024-01-26 北京交大微联科技有限公司 Configuration method, device, equipment and medium of railway signal centralized monitoring system
WO2024093971A1 (en) * 2022-11-04 2024-05-10 中车长春轨道客车股份有限公司 Method and system for determining vehicle-mounted superconducting magnet monitoring system, and storage medium
CN116520882A (en) * 2023-04-28 2023-08-01 北京交通大学 Unmanned aerial vehicle system-oriented configuration defect analysis method and system
CN116520882B (en) * 2023-04-28 2024-02-06 北京交通大学 Unmanned aerial vehicle system-oriented configuration defect analysis method and system

Similar Documents

Publication Publication Date Title
CN112015647A (en) Configuration item monitoring method and device, computer equipment and storage medium
US9459942B2 (en) Correlation of metrics monitored from a virtual environment
US10871753B2 (en) Feedback loop driven end-to-end state control of complex data-analytic systems
US10444121B2 (en) Fault detection using event-based predictive models
CN109934268B (en) Abnormal transaction detection method and system
US10223185B2 (en) Automated defect diagnosis from machine diagnostic data
US20180349251A1 (en) Automated Root Cause Detection Using Data Flow Analysis
JP2019500680A5 (en)
US20220035356A1 (en) Equipment failure diagnosis support system and equipment failure diagnosis support method
US11169896B2 (en) Information processing system
CN113342685A (en) Precise test method and device, computer equipment and storage medium
EP2113874A1 (en) Method and system for monitoring computer-implemented processes
CN114924990A (en) Abnormal scene testing method and electronic equipment
US11106650B2 (en) Data selection system and data selection method
US20130031086A1 (en) Process automation system problem analysis tool
JP2019032671A (en) Cause estimation method and program
CN115437961A (en) Data processing method and device, electronic equipment and storage medium
CN115098378A (en) Method and device for classifying and aggregating log fragments based on abnormal breakpoints
JP7359601B2 (en) Data extraction device, data extraction method, and data extraction program
CN114677779A (en) Vehicle configuration state monitoring method and device, storage medium and computer equipment
CN111141981A (en) Line loss point inspection method and device, computer equipment and storage medium
CN108764607B (en) User monthly data review method, device, equipment and storage medium
CN112948188A (en) Log file screening method, system and medium
CN112632174A (en) Data inspection method, device and system
CN114860549B (en) Buried data verification method, buried data verification device, buried data verification equipment and storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination