CN111831628A - System operation and maintenance monitoring method and device, electronic equipment and storage medium - Google Patents
System operation and maintenance monitoring method and device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN111831628A CN111831628A CN202010740475.XA CN202010740475A CN111831628A CN 111831628 A CN111831628 A CN 111831628A CN 202010740475 A CN202010740475 A CN 202010740475A CN 111831628 A CN111831628 A CN 111831628A
- Authority
- CN
- China
- Prior art keywords
- function switch
- release
- version
- monitoring
- change
- 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
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/21—Design, administration or maintenance of databases
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
- G06F11/302—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system component is a software system
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3051—Monitoring arrangements for monitoring the configuration of the computing system or of the computing system component, e.g. monitoring the presence of processing resources, peripherals, I/O links, software programs
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/21—Design, administration or maintenance of databases
- G06F16/219—Managing data history or versioning
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Databases & Information Systems (AREA)
- Computing Systems (AREA)
- Data Mining & Analysis (AREA)
- Quality & Reliability (AREA)
- Software Systems (AREA)
- Mathematical Physics (AREA)
- Computer Security & Cryptography (AREA)
- Debugging And Monitoring (AREA)
Abstract
The application belongs to the technical field of pedestal operation and maintenance, and provides a system operation and maintenance monitoring method, which comprises the following steps: acquiring version release change related information, and acquiring an old value of a function switch in a configuration file and/or a database of a system; version release is carried out according to the version release change related information and a preset rule, and a new value of a function switch after the version release is collected; and comparing the new value of the function switch after the version release with the old value of the function switch before the version release, and monitoring the system operation condition corresponding to the function switch according to the comparison result. By monitoring the function switch values before and after the release of the system version in real time and monitoring the system operation condition according to the change of the function switch values, the influence of the application function switch can be repaired in advance under the condition of no business influence, and the great influence on the business is avoided.
Description
Technical Field
The present disclosure relates to the field of pedestal operation and maintenance technologies, and in particular, to a method and an apparatus for monitoring system operation and maintenance, an electronic device, and a storage medium.
Background
The monitoring system plays an important role in the whole operation and maintenance link and even the most important link in the whole product life cycle, can comprehensively monitor and alarm a server, an operating system, middleware and application, can early warn in advance to find faults in time, and provides detailed data for tracing and positioning problems afterwards.
At present, in the operation and maintenance of the existing system, the monitoring and alarming are mainly concentrated on the aspects of logs, networks, hosts and the like, and the monitoring is lacked for the function switch applied to a configuration file or a database; and the wrong configuration of the application function often causes a great abnormity of the system and even causes the service to be unavailable.
Disclosure of Invention
In view of the foregoing, a method, an apparatus, an electronic device, and a storage medium for system operation and maintenance monitoring are provided. So as to realize the monitoring and early warning of the change state of the function switch.
In order to solve the above problem, an embodiment of the present application discloses a system operation and maintenance monitoring method, including:
acquiring version release change related information, and acquiring an old value of a function switch in a configuration file and/or a database of a system;
version release is carried out according to the version release change related information and a preset rule, and a new value of a function switch after the version release is collected;
and comparing the new value of the function switch after the version release with the old value of the function switch before the version release, and monitoring the system operation condition corresponding to the function switch according to the comparison result.
Further, the comparing the new value of the function switch with the old value of the function switch, and monitoring the system operation status according to the comparison result includes:
if the new value of the function switch is consistent with the old value of the function switch, outputting a consistent identifier, and not monitoring the system running condition corresponding to the function switch;
if the new value of the function switch is inconsistent with the old value of the function switch, outputting a change identifier, storing the old value of the function switch into a preset database, and monitoring the system running condition corresponding to the changed function switch;
if the old value of the function switch exists and the new value of the function switch does not exist, outputting a deletion identifier and monitoring the system running state corresponding to the function switch;
and if the old value of the function switch does not exist and the new value of the function switch exists, outputting a newly added identifier and monitoring the system running state corresponding to the function switch.
Further, the monitoring the system operation status corresponding to the function switch according to the comparison result includes:
and if the output identifier is a change identifier, a deletion identifier or a new identifier when the new value of the function switch is compared with the old value of the function switch, inquiring a corresponding alarm mail according to a preset system importance level, and sending the alarm mail to an operation and maintenance end and/or a development end.
Further, the monitoring the system operation status corresponding to the function switch according to the comparison result includes:
if the output identifier is a deleted identifier or a newly added identifier, comparing the new value of the function switch with the old value of the function switch, sending function change confirmation information to an operation and maintenance end and/or a development end, wherein the function change confirmation information is function change information and influence corresponding to the newly added or deleted function switch;
receiving a confirmation result corresponding to the function change confirmation information sent by the operation and maintenance end and/or the development end;
and storing the confirmation result into a preset database.
Further, the version release is performed according to the version release change related information and a preset rule, and the collecting of the new value of the function switch after the version release includes:
acquiring a system release plan according to the version release change related information;
forming a monitoring version release change queue according to the system release plan;
and issuing the version according to the monitoring version issuing change queue, collecting the new value of the function switch after the version is issued, and sending a version issuing completion result to the operation and maintenance end and/or the development end.
Further, the system release plan includes a planned release start time, and the forming of the monitored version release change queue according to the system release plan includes:
collecting the planned release starting time according to a preset time interval;
comparing the current plan release starting time with the historical plan release starting time, and judging whether the current plan release starting time is consistent with the historical plan release starting time;
and if the current planned release starting time is different from the historical planned release starting time, updating the monitoring version release change queue according to the current planned release starting time.
Further, the system release plan further includes a system name, a version number, and a plan release end time, and the acquiring version release change related information includes, after acquiring the system release plan according to the version release change related information:
recording the system name, the version number, the planned release starting time and the planned release ending time to a preset database;
wherein the predetermined database is deployed in a blockchain.
The embodiment of the application discloses system operation and maintenance monitoring device includes:
the information acquisition module is used for acquiring version release change related information and acquiring old values of the function switches in a configuration file and/or a database of the system;
the version release module is used for releasing the version according to the version release change related information and a preset rule and collecting a new value of the function switch after the version is released;
and the monitoring module is used for comparing the new value of the function switch after the version release with the old value of the function switch before the version release and monitoring the system running state corresponding to the function switch according to the comparison result.
The embodiment of the application discloses an electronic device, which comprises a processor, a memory and a computer program stored on the memory and capable of running on the processor, wherein when the computer program is executed by the processor, the steps of the system operation and maintenance monitoring method are realized.
The embodiment of the application discloses a computer readable storage medium, which comprises a storage data area and a storage program area, wherein the storage data area stores data created according to the use of a block chain node, and the storage program area stores a computer program, and when the computer program is executed by a processor, the steps of the system operation and maintenance monitoring method are realized.
The embodiment of the application has the following beneficial effects: the function switch in the configuration file or the database is monitored in real time, and the change of the function switch is judged according to the comparison between the new value of the function switch and the old value of the function switch, so that the change state of the function switch is monitored and early warned, the reliability and the usability of the operation and maintenance system are improved, the serious abnormal condition of the system is avoided in advance, and the monitoring defect is filled.
Drawings
FIG. 1 is a flowchart illustrating steps of an embodiment of a system operation and maintenance monitoring method according to the present application;
FIG. 2 is a flowchart illustrating steps of another embodiment of a system operation and maintenance monitoring method according to the present application;
FIG. 3 is a flowchart illustrating steps of another embodiment of a system operation and maintenance monitoring method according to the present application;
FIG. 4 is a flowchart illustrating steps of another embodiment of a system operation and maintenance monitoring method according to the present application;
FIG. 5 is a flowchart illustrating steps of another embodiment of a system operation and maintenance monitoring method according to the present application;
fig. 6 is a block diagram of an embodiment of a system operation and maintenance monitoring apparatus according to the present application;
FIG. 7 is a block diagram of another embodiment of a system operation and maintenance monitoring device according to the present application;
FIG. 8 is a block diagram of another embodiment of a system operation and maintenance monitoring device according to the present application;
FIG. 9 is a block diagram of another embodiment of a system operation and maintenance monitoring device according to the present application;
fig. 10 is a computer device of a system operation and maintenance monitoring method according to the present application.
Detailed Description
In order to make the aforementioned objects, features and advantages of the present application more comprehensible, the present application is described in further detail with reference to the accompanying drawings and the detailed description.
One of the core concepts of the embodiment of the present application is to provide a system operation and maintenance monitoring method, including: acquiring version release change related information, and acquiring an old value of a function switch in a configuration file and/or a database of a system; version release is carried out according to the version release change related information and a preset rule, and a new value of a function switch after the version release is collected; and comparing the new value of the function switch after the version release with the old value of the function switch before the version release, and monitoring the system operation condition corresponding to the function switch according to the comparison result. By monitoring the function switch values before and after the release of the system version in real time and monitoring the system operation condition according to the change of the function switch values, the influence of the application function switch can be repaired in advance under the condition of no business influence, and the great influence on the business is avoided.
Referring to fig. 1, a flowchart illustrating steps of an embodiment of a system operation and maintenance monitoring method according to the present application is shown, and specifically, the method may include the following steps:
s110, acquiring version release change related information, and collecting old values of function switches in a configuration file and/or a database of a system;
s120, version release is carried out according to the version release change related information and a preset rule, and a new value of a function switch after the version release is collected;
s130, comparing the new value of the function switch after the version release with the old value of the function switch before the version release, and monitoring the system running state corresponding to the function switch according to the comparison result.
It is emphasized that, in order to further ensure the privacy and security of the version release change related information, the version release change related information may also be stored in a node of a block chain.
Referring to step S110, the information related to version release change is obtained, and the old values of the function switches in the configuration file and/or the database of the system are collected. Specifically, through this application realization to quoting the release change of system, the new value of function switch on the system passes through proxy server (agent) automatic collection configuration file, function switch includes the function switch in the configuration file and the database switch in the database, function switch in the configuration file obtains through proxy server automatic collection configuration file, database switch can be through formulating standard protocol with database switch fixed record on the function switch table of definition, is convenient for collect the new value of corresponding function switch. The version release change related information is specifically obtained through an external interface, the version release change related information includes, but is not limited to, version creation information, version deployment initiation information, version release change information, version deployment completion information, and/or version change information, and the external interface in the present application includes, but is not limited to, an open-api interface and a WebHook interface. The method and the device are based on the http protocol and transmit the parameters from the outside to a third-party interface of the development end in a post mode, so that the related information of version release change can be obtained.
The function switch in the application is a service switch defined in a uniform mode, and the function switch can be used for centrally managing the services of each application when the management services run. In order to ensure the dynamic performance of each service, a back-end program usually controls the logic of the program by using the change of a value of a function switch, so as to achieve the purpose of switching the operation logic when the system runs.
Referring to the step S120, the version is released according to the preset rule according to the version release change related information, and a new value of the function switch after the version is released is collected. And after a system release plan is acquired through the version creation interface, recording the system name, the version number, the planned release starting time and the planned release ending time, forming a monitoring version release change queue according to the planned release starting time, and sequentially releasing the system according to the sequence of the version release change queue.
Referring to the step S130, the new value of the function switch after the version release is compared with the old value of the function switch before the version release, and the system operation status corresponding to the function switch is monitored according to the comparison result. The monitoring of the application function switch can judge whether the system is abnormal or not in the release process, and can repair the influence of the application switch function in advance under the condition of no business influence, thereby avoiding great influence on the business.
Referring to fig. 2, in this embodiment, the step S130 of comparing the new value of the function switch with the old value of the function switch and monitoring the function switch according to the comparison result may further include the following steps:
s131, if the new value of the function switch is consistent with the old value of the function switch, outputting a consistent identifier, and not monitoring the system running state corresponding to the function switch;
s132, if the new value of the function switch is inconsistent with the old value of the function switch, outputting a change identifier, storing the old value of the function switch into a preset database, and monitoring the system running state corresponding to the changed function switch;
s133, if the old value of the function switch exists and the new value of the function switch does not exist, outputting a deletion identifier and monitoring the system running state corresponding to the function switch;
and S134, if the old value of the function switch does not exist and the new value of the function switch exists, outputting a newly added identifier and monitoring the system running state corresponding to the function switch.
Referring to the above steps, the new value of the function switch may be compared with the old value of the function switch, and whether the function switch needs to be monitored may be further determined according to the output identifier, and when the function switch is changed, the old value of the function switch may be stored in the database so as to be called for the change determination. Specifically, when the new value of the function switch is consistent with the old value of the function switch, it indicates that the value of the function switch has not changed, that is, the system operation logic corresponding to the function switch has not sent a change, and then a consistent identifier is output, in a specific embodiment, the value of the consistent identifier is defined to be 0, the value of the newly added identifier is 1, the value of the deleted identifier is 2, and the value of the changed identifier is 3, and then the consistent identifier with the value of 0 is output; when the new value of the function switch is inconsistent with the old value of the function switch, the value of the function switch is modified, a change identifier with a numerical value of 3 is output, when the old value of the function switch in the original system is deleted, a deletion identifier with a numerical value of 2 is output, and when the new value of the function switch is added in the new system, a new identifier with a numerical value of 1 is output. By monitoring the values of the function switches before and after the release of the system version in real time and analyzing the running state of the system according to the change condition of the function switches, the influence of the application function switches can be repaired in advance, great influence on the service is avoided, the time efficiency of solving the abnormity is further improved, the stable running of the application system is improved, and the reliable running of the service is ensured.
Further, in this embodiment, if the output identifier obtained by comparing the new value of the function switch with the old value of the function switch is a change identifier, or a delete identifier, or a new identifier, it indicates that the function switch has a corresponding change, that is, the system operation logic corresponding to the function switch sends a corresponding change, and at this time, in addition to outputting a corresponding changeable identifier, or a delete identifier, or a new identifier, a corresponding alarm mail may be queried according to a preset system importance level, and the alarm mail is sent to the operation and maintenance end and/or the development end to remind the operation and maintenance personnel and/or the development personnel, so that the operation and maintenance personnel and/or the development personnel can know the change in time to perform processing such as maintenance on the system in time.
Referring to the steps, when the function switch of the system is not changed, an alarm mail is not required to be sent; and when the system function switch has the actions of deletion, addition, change and the like, sending a corresponding alarm mail to the operation and maintenance end and/or the development end according to the importance level of the currently changed function switch. The operation and maintenance personnel or the development personnel can conveniently carry out corresponding early warning operation according to the corresponding warning mails, the condition that the system is seriously abnormal is avoided, and the monitoring deficiency is filled.
Referring to fig. 3, in this embodiment, the step S130 of monitoring the system operating condition corresponding to the function switch according to the comparison result may further include the following steps:
s135, if the output identifier obtained by comparing the new value of the function switch with the old value of the function switch is a deleted identifier or a newly added identifier, sending function change confirmation information to an operation and maintenance end and/or a development end, wherein the function change confirmation information is function change information and influence corresponding to the newly added or deleted function switch;
s136, receiving a confirmation result corresponding to the function change confirmation information sent by the operation and maintenance end and/or the development end;
and S137, storing the confirmation result into a preset database.
Referring to the above steps, when the function switch is updated, the corresponding function is changed, the system sends the corresponding function before the change and the corresponding function and function change influence after the version release to the operation and maintenance terminal and/or the development terminal, specifically, the function and change influence of the function switch can be stored in the database in advance, and when the function switch is changed, the corresponding change influence result in the database is directly called and sent to the operation and maintenance terminal and/or the development terminal.
Referring to fig. 4, in this embodiment, the step S120 of performing version release according to the version release change related information and the preset rule, and collecting a new value of the function switch after the version release may include the following steps:
s121, acquiring a system release plan according to the version release change related information;
s122, forming a monitoring version release change queue according to the system release plan;
and S123, carrying out version release according to the monitored version release change queue, collecting new values of the function switches after the version release, and sending a version release completion result to the operation and maintenance end and/or the development end.
Specifically, in this embodiment, the system release plan includes a planned release start time, where forming a monitoring version release change queue according to the system release plan specifically includes collecting the planned release start time according to a preset time interval; comparing the current plan release starting time with the historical plan release starting time, and judging whether the current plan release starting time is consistent with the historical plan release starting time; and if the current planned release starting time is different from the historical planned release starting time, updating the monitoring version release change queue according to the current planned release starting time.
Referring to the above steps, in order to avoid the change of the scheduled distribution time, whether the scheduled distribution start time of the system changes or not can be obtained through the version information change interface every 1 hour, and if so, the scheduled distribution start time is updated and sorted again in the queue.
In this embodiment, the system release plan further includes a system name, a version number, and a scheduled release end time, and after the version release change related information is acquired, the system name, the version number, the scheduled release start time, and the scheduled release end time may be further recorded in a preset database after the system release plan is acquired according to the version release change related information; wherein the predetermined database is deployed in a blockchain.
The block chain referred by the application is a novel application mode of computer technologies such as distributed data storage, point-to-point transmission, a consensus mechanism, an encryption algorithm and the like. A block chain (Blockchain), which is essentially a decentralized database, is a series of data blocks associated by using a cryptographic method, and each data block contains information of a batch of network transactions, so as to verify the validity (anti-counterfeiting) of the information and generate a next block. The blockchain may include a blockchain underlying platform, a platform product service layer, an application service layer, and the like. The preset database is deployed in the block chain, so that the safety of data storage can be improved.
And referring to the steps, version release is carried out according to the version release change related information and the preset rule, and new values of the corresponding function switches are collected. And after a system release plan is acquired through the version creation interface, recording the system name, the version number, the planned release starting time and the planned release ending time, forming a monitoring version release change queue according to the planned release time, and sequentially performing system release according to the sequence of the version release change queue.
Referring to fig. 5, in an embodiment, a system publishing and monitoring method is disclosed, including:
s211, acquiring version release change related information, and acquiring a system release plan according to the version release change related information;
s212, recording the system name, the version number, the planned release starting time and the planned release ending time to a preset database;
s213, forming a monitoring version release change queue according to the system release plan, and collecting the plan release starting time according to a preset time interval; comparing the current plan release starting time with the historical plan release starting time, and judging whether the current plan release starting time is consistent with the historical plan release starting time; if the current planned release starting time is different from the historical planned release starting time, updating the monitoring version release change queue according to the current planned release starting time;
s214, performing version release according to the monitored version release change queue, collecting a new value of a function switch after the version release, and sending a version release completion result to the operation and maintenance end and/or the development end;
s215, acquiring old values of function switches in configuration files and/or databases of the system according to the version release change related information;
s216, according to the version release change related information, version release is carried out according to a preset rule, and a new value of a function switch after the version release is collected;
s217, comparing the new value of the function switch after the version release with the old value of the function switch before the version release, and monitoring the system operation state corresponding to the function switch according to the comparison result; if the new value of the function switch is consistent with the old value of the function switch, outputting a consistent identifier, and not monitoring the system running condition corresponding to the function switch;
s218, if the new value of the function switch is inconsistent with the old value of the function switch, outputting a change identifier, storing the old value of the function switch into a preset database, and monitoring the system operation condition corresponding to the changed function switch;
s219, if the old value of the function switch exists and the new value of the function switch does not exist, outputting a deletion identifier and monitoring the system running state corresponding to the function switch;
s220, if the old value of the function switch does not exist and the new value of the function switch exists, outputting a newly added identifier and monitoring the system running state corresponding to the function switch;
s221, if the output identifier obtained by comparing the new value of the function switch with the old value of the function switch is a change identifier, or a delete identifier, or a new identifier, inquiring a corresponding alarm mail according to a preset system importance level, and sending the alarm mail to an operation and maintenance end and/or a development end;
s222, if the identification output by comparing the new value of the function switch with the old value of the function switch is a deleted identification or a newly added identification, sending function change confirmation information to an operation and maintenance end and/or a development end, wherein the function change confirmation information is function change information and influence corresponding to the newly added or deleted function switch;
s223, receiving a confirmation result corresponding to the function change confirmation information sent by the operation and maintenance end and/or the development end;
and S224, storing the confirmation result into a preset database.
It should be noted that, for simplicity of description, the method embodiments are described as a series of acts or combination of acts, but those skilled in the art will recognize that the embodiments are not limited by the order of acts described, as some steps may occur in other orders or concurrently depending on the embodiments. Further, those skilled in the art will also appreciate that the embodiments described in the specification are presently preferred and that no particular act is required of the embodiments of the application.
Referring to fig. 6, a block diagram of a system operation and maintenance monitoring apparatus according to an embodiment of the present application is shown, and specifically, the system operation and maintenance monitoring apparatus may include the following modules:
the information acquisition module 110 is configured to acquire version release change related information and acquire old values of function switches in a system configuration file and/or a database;
the version release module 120 is configured to release a version according to the version release change related information and a preset rule, and collect a new value of the function switch after the version release;
and the monitoring module 130 is configured to compare the new value of the function switch after the version release with the old value of the function switch before the version release, and monitor the system operation status corresponding to the function switch according to the comparison result.
Referring to fig. 7, in the present embodiment, the monitoring module 130 includes:
the neglect monitoring unit 131 is configured to output a consistent identifier if the new value of the function switch is consistent with the old value of the function switch, and not monitor the system operating condition corresponding to the function switch;
a changing unit 132, configured to output a change identifier if the new value of the function switch is inconsistent with the old value of the function switch, store the old value of the function switch in a preset database, and monitor a system operating condition corresponding to the updated function switch;
a deleting unit 133, configured to output a deletion identifier if the old value of the function switch exists and the new value of the function switch does not exist, and monitor a system operating condition corresponding to the function switch;
and a new adding unit 134, configured to output a new adding identifier if the old value of the function switch does not exist and the new value of the function switch exists, and monitor a system operation status corresponding to the function switch.
In this embodiment, the method further includes:
and the alarm module is used for inquiring a corresponding alarm mail according to a preset system importance level and sending the alarm mail to the operation and maintenance end and/or the development end if the output identifier is a change identifier, or the identifier is deleted, or the identifier is newly added when the new value of the function switch is compared with the old value of the function switch.
Referring to fig. 8, in this embodiment, the monitoring module 130 further includes:
an information confirming unit 135, configured to send function change confirmation information to the operation and maintenance end and/or the development end if an identifier output by comparing the new value of the function switch with the old value of the function switch is a deleted identifier or a newly added identifier, where the function change confirmation information is function change information and an influence corresponding to the function switch being newly added or deleted;
a confirmation result receiving unit 136, configured to receive a confirmation result corresponding to the function change confirmation information sent by the operation and maintenance end and/or the development end;
a result storage unit 137, configured to store the confirmation result in a preset database.
Referring to fig. 9, in the present embodiment, the version issuing module 120 includes:
a plan obtaining unit 121, configured to obtain a system release plan according to the version release change related information;
a queue update list 122, configured to form a monitored version release change queue according to the system release plan;
and the version release unit 123 is configured to release the version according to the monitored version release change queue, collect a new value of the function switch after the version release, and send a version release completion result to the operation and maintenance terminal and/or the development terminal.
In this embodiment, the system publishing plan includes a planned publishing start time, and the queue updating unit includes:
the time acquisition subunit is used for acquiring the planned release starting time according to a preset time interval;
the plan comparison unit is used for comparing the current plan release starting time with the historical plan release starting time and judging whether the current plan release starting time is consistent with the historical plan release starting time or not;
and the queue updating subunit is configured to update the monitored version release change queue according to the current planned release start time if the current planned release start time is different from the historical planned release start time.
In this embodiment, the system release plan further includes a system name, a version number, and a plan release end time, and the apparatus of the present application further includes:
the information storage module is used for recording the system name, the version number, the planned release starting time and the planned release ending time to a preset database;
wherein the predetermined database is deployed in a blockchain.
The block chain referred by the application is a novel application mode of computer technologies such as distributed data storage, point-to-point transmission, a consensus mechanism, an encryption algorithm and the like. A block chain (Blockchain), which is essentially a decentralized database, is a series of data blocks associated by using a cryptographic method, and each data block contains information of a batch of network transactions, so as to verify the validity (anti-counterfeiting) of the information and generate a next block. The blockchain may include a blockchain underlying platform, a platform product service layer, an application service layer, and the like.
For the device embodiment, since it is basically similar to the method embodiment, the description is simple, and for the relevant points, refer to the partial description of the method embodiment.
Referring to fig. 10, an electronic device of a system operation and maintenance monitoring method according to the present invention is shown, which may specifically include the following:
the electronic device 12 described above is embodied in the form of a general purpose computing device, and the components of the electronic device 12 may include, but are not limited to: one or more processors or processing units 16, a system memory 28, and a bus 18 that couples various system components including the system memory 28 and the processing unit 16.
The system memory 28 may include computer system readable media in the form of volatile memory, such as Random Access Memory (RAM)30 and/or cache memory 32. The electronic device 12 may further include other removable/non-removable, volatile/nonvolatile computer system storage media. By way of example only, storage system 34 may be used to read from and write to non-removable, nonvolatile magnetic media (commonly referred to as "hard drives"). Although not shown in FIG. 5, a magnetic disk drive for reading from and writing to a removable, nonvolatile magnetic disk (e.g., a "floppy disk") and an optical disk drive for reading from or writing to a removable, nonvolatile optical disk (e.g., a CD-ROM, DVD-ROM, or other optical media) may be provided. In these cases, each drive may be connected to bus 18 by one or more data media interfaces. The memory may include at least one program product having a set (e.g., at least one) of program modules 42, with the program modules 42 configured to carry out the functions of embodiments of the invention.
A program/utility 40 having a set (at least one) of program modules 42 may be stored, for example, in memory, such program modules 42 including, but not limited to, an operating system, one or more application programs, other program modules 42, and program data, each of which examples or some combination thereof may comprise an implementation of a network environment. Program modules 42 generally carry out the functions and/or methodologies of the described embodiments of the invention.
The processing unit 16 executes various functional applications and data processing by running programs stored in the system memory 28, for example, to implement the system operation and maintenance monitoring method provided by the embodiment of the present invention.
That is, the processing unit 16 implements, when executing the program,: acquiring version release change related information, and acquiring an old value of a function switch in a configuration file and/or a database of a system; version release is carried out according to the version release change related information and a preset rule, and a new value of a function switch after the version release is collected; and comparing the new value of the function switch after the version release with the old value of the function switch before the version release, and monitoring the system operation condition corresponding to the function switch according to the comparison result.
In an embodiment of the present invention, the present invention further provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the system operation and maintenance monitoring method provided in all embodiments of the present application:
that is, the program when executed by the processor implements: acquiring version release change related information, and acquiring an old value of a function switch in a configuration file and/or a database of a system; version release is carried out according to the version release change related information and a preset rule, and a new value of a function switch after the version release is collected; and comparing the new value of the function switch after the version release with the old value of the function switch before the version release, and monitoring the system operation condition corresponding to the function switch according to the comparison result.
Any combination of one or more computer-readable media may be employed. The computer readable medium may be a computer-readable storage medium or a computer-readable signal medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPOM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
Computer program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider). The embodiments in the present specification are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments are referred to each other.
While preferred embodiments of the present application have been described, additional variations and modifications of these embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including the preferred embodiment and all such alterations and modifications as fall within the true scope of the embodiments of the application.
Finally, it should also be noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or terminal that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or terminal. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or terminal that comprises the element.
The block chain referred by the application is a novel application mode of computer technologies such as distributed data storage, point-to-point transmission, a consensus mechanism, an encryption algorithm and the like. A block chain (Blockchain), which is essentially a decentralized database, is a series of data blocks associated by using a cryptographic method, and each data block contains information of a batch of network transactions, so as to verify the validity (anti-counterfeiting) of the information and generate a next block. The blockchain may include a blockchain underlying platform, a platform product service layer, an application service layer, and the like.
The system operation and maintenance monitoring method, device, electronic device and storage medium provided by the present application are introduced in detail, and a specific example is applied in the present application to explain the principle and the implementation of the present application, and the description of the above embodiment is only used to help understand the method and the core idea of the present application; meanwhile, for a person skilled in the art, according to the idea of the present application, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present application.
Claims (10)
1. A system operation and maintenance monitoring method is characterized by comprising the following steps:
acquiring version release change related information, and acquiring an old value of a function switch in a configuration file and/or a database of a system;
version release is carried out according to the version release change related information and a preset rule, and a new value of a function switch after the version release is collected;
and comparing the new value of the function switch after the version release with the old value of the function switch before the version release, and monitoring the system operation condition corresponding to the function switch according to the comparison result.
2. The method of claim 1, wherein comparing the new value of the function switch with the old value of the function switch and monitoring the system operation according to the comparison result comprises:
if the new value of the function switch is consistent with the old value of the function switch, outputting a consistent identifier, and not monitoring the system running condition corresponding to the function switch;
if the new value of the function switch is inconsistent with the old value of the function switch, outputting a change identifier, storing the old value of the function switch into a preset database, and monitoring the system running condition corresponding to the changed function switch;
if the old value of the function switch exists and the new value of the function switch does not exist, outputting a deletion identifier and monitoring the system running state corresponding to the function switch;
and if the old value of the function switch does not exist and the new value of the function switch exists, outputting a newly added identifier and monitoring the system running state corresponding to the function switch.
3. The method according to claim 1 or 2, wherein the monitoring the system operation status corresponding to the function switch according to the comparison result comprises:
and if the output identifier is a change identifier, a deletion identifier or a new identifier when the new value of the function switch is compared with the old value of the function switch, inquiring a corresponding alarm mail according to a preset system importance level, and sending the alarm mail to an operation and maintenance end and/or a development end.
4. The method according to claim 1 or 2, wherein the monitoring the system operation status corresponding to the function switch according to the comparison result comprises:
if the output identifier is a deleted identifier or a newly added identifier, comparing the new value of the function switch with the old value of the function switch, sending function change confirmation information to an operation and maintenance end and/or a development end, wherein the function change confirmation information is function change information and influence corresponding to the newly added or deleted function switch;
receiving a confirmation result corresponding to the function change confirmation information sent by the operation and maintenance end and/or the development end;
and storing the confirmation result into a preset database.
5. The method according to claim 1, wherein the version release is performed according to a preset rule according to the version release change related information, and a new value of the function switch after the version release is collected, includes:
acquiring a system release plan according to the version release change related information;
forming a monitoring version release change queue according to the system release plan;
and issuing the version according to the monitoring version issuing change queue, collecting the new value of the function switch after the version is issued, and sending a version issuing completion result to the operation and maintenance end and/or the development end.
6. The method of claim 5, wherein the system release plan includes a scheduled release start time, and wherein forming a queue of monitored version release changes according to the system release plan includes:
collecting the planned release starting time according to a preset time interval;
comparing the current plan release starting time with the historical plan release starting time, and judging whether the current plan release starting time is consistent with the historical plan release starting time;
and if the current planned release starting time is different from the historical planned release starting time, updating the monitoring version release change queue according to the current planned release starting time.
7. The method of claim 6, wherein the system release plan further includes a system name, a version number, and a plan release end time;
the acquiring version release change related information, after acquiring a system release plan according to the version release change related information, further includes:
recording the system name, the version number, the planned release starting time and the planned release ending time to a preset database;
wherein the predetermined database is deployed in a blockchain.
8. A system operation and maintenance monitoring device is characterized by comprising:
the information acquisition module is used for acquiring version release change related information and acquiring old values of the function switches in a configuration file and/or a database of the system;
the version release module is used for releasing the version according to the version release change related information and a preset rule and collecting a new value of the function switch after the version is released;
and the monitoring module is used for comparing the new value of the function switch after the version release with the old value of the function switch before the version release and monitoring the system running state corresponding to the function switch according to the comparison result.
9. Electronic device, characterized in that it comprises a processor, a memory and a computer program stored on the memory and capable of running on the processor, the computer program, when executed by the processor, implementing the steps of the system operation and maintenance monitoring method according to any one of claims 1 to 7.
10. Computer-readable storage medium, characterized in that it comprises a data storage area storing data created according to the use of blockchain nodes and a program storage area storing a computer program, wherein the computer program when executed by a processor implements the steps of the system operation and maintenance monitoring method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010740475.XA CN111831628A (en) | 2020-07-28 | 2020-07-28 | System operation and maintenance monitoring method and device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010740475.XA CN111831628A (en) | 2020-07-28 | 2020-07-28 | System operation and maintenance monitoring method and device, electronic equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111831628A true CN111831628A (en) | 2020-10-27 |
Family
ID=72921071
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010740475.XA Pending CN111831628A (en) | 2020-07-28 | 2020-07-28 | System operation and maintenance monitoring method and device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111831628A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112612255A (en) * | 2020-12-24 | 2021-04-06 | 特劢丝软件科技(上海)有限公司 | Data acquisition method and device, electronic equipment and storage medium |
| CN112732518A (en) * | 2020-12-30 | 2021-04-30 | 北京神州泰岳智能数据技术有限公司 | Application program version monitoring method and device, electronic equipment and storage medium |
| CN113360213A (en) * | 2021-06-30 | 2021-09-07 | 中国农业银行股份有限公司 | Application program version switching method, device, equipment and system |
-
2020
- 2020-07-28 CN CN202010740475.XA patent/CN111831628A/en active Pending
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112612255A (en) * | 2020-12-24 | 2021-04-06 | 特劢丝软件科技(上海)有限公司 | Data acquisition method and device, electronic equipment and storage medium |
| CN112612255B (en) * | 2020-12-24 | 2021-10-12 | 上海赛美特软件科技有限公司 | Data acquisition method and device, electronic equipment and storage medium |
| CN112732518A (en) * | 2020-12-30 | 2021-04-30 | 北京神州泰岳智能数据技术有限公司 | Application program version monitoring method and device, electronic equipment and storage medium |
| CN113360213A (en) * | 2021-06-30 | 2021-09-07 | 中国农业银行股份有限公司 | Application program version switching method, device, equipment and system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111831628A (en) | System operation and maintenance monitoring method and device, electronic equipment and storage medium | |
| US20230129123A1 (en) | Monitoring and Management System for Automatically Generating an Issue Prediction for a Trouble Ticket | |
| US8756385B2 (en) | Software configuration item back-up facility | |
| CN112152823B (en) | Website operation error monitoring method and device and computer storage medium | |
| CN113946499A (en) | Micro-service link tracking and performance analysis method, system, equipment and application | |
| EP3470988A1 (en) | Method for replicating production behaviours in a development environment | |
| CN110765090B (en) | Log data management method and device, storage medium and electronic equipment | |
| US9448998B1 (en) | Systems and methods for monitoring multiple heterogeneous software applications | |
| CN115964272A (en) | Transaction data automatic testing method, device, equipment and readable storage medium | |
| CN111198902B (en) | Metadata management method and device, storage medium and electronic equipment | |
| CN114328107A (en) | Monitoring method and system for optomagnetic fusion storage server cluster and electronic equipment | |
| CN113010208A (en) | Version information generation method, version information generation device, version information generation equipment and storage medium | |
| CN112817827A (en) | Operation and maintenance method, device, server, equipment, system and medium | |
| CN117422434A (en) | Wisdom fortune dimension dispatch platform | |
| CN111427959A (en) | Data storage method and device | |
| CN114358799B (en) | Hardware information management method and device, electronic equipment and storage medium | |
| CN110348984B (en) | Automatic credit card data input method and related equipment under different transaction channels | |
| CN114625664A (en) | Automatic testing method, device, equipment and storage medium | |
| JP4850733B2 (en) | Health check device, health check method and program | |
| CN112799957A (en) | User behavior based fault handling method, system, device and medium | |
| CN111930590A (en) | Real-time monitoring system for computer software and hardware resources | |
| CN113760856A (en) | Database management method and device, computer readable storage medium and electronic device | |
| CN111447329A (en) | Method, system, device and medium for monitoring state server in call center | |
| JP2002351702A (en) | Method and device for preparing terminal operation statistical data utilizing online | |
| CN116431872B (en) | Observable system and service observing method based on observable system |
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 |