System change processing method and device, electronic equipment and readable medium

Abstract

The embodiment of the invention provides a system change processing method and device, electronic equipment and a readable medium. The method comprises the following steps: collecting a change operation log generated by at least one system management platform; wherein the system management platforms are respectively used for managing at least one operation system; determining a target system object associated with the change operation log in the system objects; acquiring a system change approval work order; based on the system change approval work order and a target system object associated with the change operation log, determining whether a system change operation corresponding to the change operation log satisfies a preset change condition; and if the system change operation corresponding to the change operation log does not meet the preset change condition, sending a change prompt for the system change operation. Therefore, whether the system change operation corresponding to the change operation log belongs to the allowed system change operation can be determined, and when the system change operation is not allowed, a prompt is given out in time, so that the stability of an operation system can be better maintained.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a method for processing system changes, a device for processing system changes, an electronic device, and a computer-readable medium. Background Art

[0002] When an enterprise manages its business through an operation system, there may usually be multiple operation systems, such as a billing system, a customer relationship management system, an order management system, etc. In order to meet different business needs, a variety of different system management platforms can usually be designed to manage one or more of the operation systems. In this case, there may be multiple system management platforms that can manage and maintain the operation system at the same time, making it difficult to manage system changes to the operation system, which can easily cause failures in the operation system. Summary of the invention

[0003] The embodiment of the present invention provides a system change processing method, device, electronic device and computer-readable storage medium to solve the problem that system changes of an operating system are difficult to manage.

[0004] The embodiment of the present invention discloses a method for processing system changes, including:

[0005] Collecting change operation logs generated by at least one system management platform; wherein the system management platform is used to manage at least one operation system; the operation system includes at least one system object;

[0006] Determining a target system object associated with the change operation log in the system objects;

[0007] Obtain system change approval work order;

[0008] Based on the system change approval work order and the target system object associated with the change operation log, confirm whether the system change operation corresponding to the change operation log meets the preset change condition;

[0009] If the system change operation corresponding to the change operation log does not meet the preset change condition, a change prompt is issued for the system change operation.

[0010] Optionally, the method further comprises:

[0011] The risk level of the change operation log is determined according to the impact scope of the change operation log on the system object in the operation system.

[0012] Optionally, the step of confirming whether the system change operation corresponding to the change operation log meets a preset change condition based on the system change approval work order, the change operation log, and the association relationship between the change operation log and the system object includes:

[0013] The change operation log whose risk level meets the preset risk condition is used as the target change operation log;

[0014] Based on the system change approval work order and the association relationship between the change operation log and the system object, it is confirmed whether the system change operation corresponding to the target change operation log meets the preset change condition.

[0015] Optionally, the step of determining, in the system object, a target system object associated with the change operation log comprises:

[0016] Extracting the system object recorded in the change operation log as the operation object;

[0017] Determining, among the system objects of the operation system, an associated object associated with the operation object;

[0018] The operation object and the associated object are used as target system objects corresponding to the change operation log.

[0019] Optionally, the step of confirming whether the system change operation corresponding to the change operation log meets a preset change condition based on the system change approval work order and the target system object associated with the change operation log includes:

[0020] Extracting the system object recorded in the system change approval work order;

[0021] Determine whether the system object recorded in the system change approval work order matches the target system object associated with the change operation log;

[0022] In a case where the system object recorded in the system change approval work order matches the target system object associated with the change operation log, it is determined that the system change operation corresponding to the change operation log meets the preset change condition.

[0023] Optionally, when the system object recorded in the system change approval work order matches the target system object associated with the change operation log, the step of determining whether the system change operation corresponding to the change operation log satisfies a preset change condition includes:

[0024] Extracting the change behavior recorded in the change operation log and the change behavior recorded in the system change approval work order;

[0025] Determine whether the change behavior recorded in the change operation log matches the change behavior recorded in the system change approval work order;

[0026] When the system object recorded in the system change approval work order matches the target system object associated with the change operation log, and the change behavior recorded in the change operation log matches the change behavior recorded in the system change approval work order, it is determined that the system change operation corresponding to the change operation log meets the preset change conditions.

[0027] Optionally, when the system object recorded in the system change approval work order matches the target system object associated with the change operation log, the step of determining whether the system change operation corresponding to the change operation log satisfies a preset change condition includes:

[0028] Extract the change time recorded in the change operation log and the change time range recorded in the system change approval work order;

[0029] Determine whether the change time recorded in the change operation log matches the change time range recorded in the system change approval work order;

[0030] When the system object recorded in the system change approval work order matches the target system object associated with the change operation log, and the change time recorded in the change operation log matches the change time range recorded in the system change approval work order, it is determined that the system change operation corresponding to the change operation log meets the preset change conditions.

[0031] Optionally, the method further comprises:

[0032] If a fault indication is received, determining a system object corresponding to the fault indication;

[0033] Based on the target system object associated with the change operation log, searching for the change operation log corresponding to the fault prompt;

[0034] A fault-related prompt is issued for the change operation log corresponding to the fault prompt.

[0035] The embodiment of the present invention further provides a system change processing device, including:

[0036] A collection module, used to collect change operation logs generated by at least one system management platform; wherein the system management platform is used to manage at least one operation system; the operation system includes at least one system object;

[0037] A target system object determination module, used to determine a target system object associated with the change operation log in the system objects;

[0038] Condition identification module, used to obtain system change approval work orders;

[0039] A matching module, used to confirm whether the system change operation corresponding to the change operation log meets the preset change condition based on the system change approval work order and the target system object associated with the change operation log;

[0040] The change prompt module is used to issue a change prompt for the system change operation if the system change operation corresponding to the change operation log does not meet the preset change condition.

[0041] Optionally, the device further comprises:

[0042] The risk identification module is used to determine the risk level of the change operation log according to the impact scope of the change operation log on the system object in the operation system.

[0043] Optionally, the matching module includes:

[0044] A first matching submodule, configured to use the change operation log whose risk level meets a preset risk condition as a target change operation log;

[0045] Based on the system change approval work order and the association relationship between the change operation log and the system object, it is confirmed whether the system change operation corresponding to the target change operation log meets the preset change condition.

[0046] Optionally, the target system object determination module includes:

[0047] An operation object extraction submodule, used to extract the system object recorded in the change operation log as the operation object;

[0048] An associated object determination submodule, used to determine an associated object associated with the operation object in the system object of the operation system;

[0049] The target system object determination submodule is used to use the operation object and the associated object as the target system object corresponding to the change operation log.

[0050] Optionally, the matching module includes:

[0051] An object extraction submodule, used to extract the system objects recorded in the system change approval work order;

[0052] An object matching submodule, used to determine whether the system object recorded in the system change approval work order matches the target system object associated with the change operation log;

[0053] The second matching submodule is used to determine whether the system change operation corresponding to the change operation log meets the preset change condition when the system object recorded in the system change approval work order matches the target system object associated with the change operation log.

[0054] Optionally, the matching module includes:

[0055] A behavior extraction submodule, used to extract the change behavior recorded in the change operation log and the change behavior recorded in the system change approval work order;

[0056] A behavior matching submodule, used to determine whether the change behavior recorded in the change operation log matches the change behavior recorded in the system change approval work order;

[0057] The third matching submodule is used to determine that the system change operation corresponding to the change operation log meets the preset change condition when the system object recorded in the system change approval work order matches the target system object associated with the change operation log, and the change behavior recorded in the change operation log matches the change behavior recorded in the system change approval work order.

[0058] Optionally, the matching module includes:

[0059] A time extraction submodule, used to extract the change time recorded in the change operation log and the change time range recorded in the system change approval work order;

[0060] A time matching submodule, used to determine whether the change time recorded in the change operation log matches the change time range recorded in the system change approval work order;

[0061] The fourth matching submodule is used to determine that the system change operation corresponding to the change operation log meets the preset change conditions when the system object recorded in the system change approval work order matches the target system object associated with the change operation log, and the change time recorded in the change operation log matches the change time range recorded in the system change approval work order.

[0062] Optionally, the device further comprises:

[0063] A fault object determination module, for determining the system object corresponding to the fault indication if a fault indication is received;

[0064] A log search module, used to search the change operation log corresponding to the fault prompt based on the target system object associated with the change operation log;

[0065] The fault association prompt module is used to issue a fault association prompt for the change operation log corresponding to the fault prompt.

[0066] The embodiment of the present invention further discloses an electronic device, comprising a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other via the communication bus;

[0067] The memory is used to store computer programs;

[0068] The processor is used to implement the method described in the embodiment of the present invention when executing the program stored in the memory.

[0069] The embodiment of the present invention further discloses one or more computer-readable media on which instructions are stored. When executed by one or more processors, the processors are enabled to execute the method described in the embodiment of the present invention.

[0070] The embodiments of the present invention include the following advantages:

[0071] Through the system change processing method provided by the embodiment of the present invention, the change operation log generated by at least one system management platform is collected; wherein the system management platform is used to manage at least one operating system respectively; the operating system includes at least one system object; the target system object associated with the change operation log is determined in the system object; a system change approval work order is obtained; based on the system change approval work order and the target system object associated with the change operation log, whether the system change operation corresponding to the change operation log meets the preset change conditions; if the system change operation corresponding to the change operation log does not meet the preset change conditions, a change prompt is issued for the system change operation. In this way, the change operation logs generated by the system management platform can be centralized, and the system objects that may be affected by the change operation logs can be determined, and compared with the system objects in the system change approval work order to determine whether the system change operation corresponding to the change operation log belongs to the allowed system change operation, and a prompt is issued in time when the system change operation is not allowed, so as to better maintain the stability of the operating system. BRIEF DESCRIPTION OF THE DRAWINGS

[0072] Figure 1 is a flowchart of a method for processing system changes provided in an embodiment of the present invention;

[0073] Figure 2 is a structural block diagram of a system change processing device provided in an embodiment of the present invention;

[0074] Figure 3 is a block diagram of an electronic device provided in an embodiment of the present invention;

[0075] Figure 4 is a schematic diagram of a computer-readable medium provided in an embodiment of the present invention. DETAILED DESCRIPTION

[0076] In order to make the above-mentioned objects, features and advantages of the present invention more obvious and easy to understand, the present invention is further described in detail below with reference to the accompanying drawings and specific embodiments.

[0077] Reference Figure 1 , shows a flowchart of a method for processing system changes provided in an embodiment of the present invention, which may specifically include the following steps:

[0078] Step 101, collecting a change operation log generated by at least one system management platform; wherein the system management platform is used to manage at least one operation system; the operation system includes at least one system object;

[0079] In an embodiment of the present invention, an enterprise may have at least one operating system. The operating system may refer to a system for managing business operations. The operating system may include at least one system object. The system object may refer to basic hardware, service architecture, application services, etc. required for the normal operation of the operating system.

[0080] As a specific example of the present invention, the operation system may adopt a distributed cluster, microservice, containerization, and other architectures, and the system objects may include:

[0081] Network as a Service (NaaS), such as firewalls, switches and other equipment.

[0082] Infrastructure as a Service (IaaS), such as physical machines and virtual machines.

[0083] Platform as a Service (PaaS), such as Kubernetes containers, caching, message queues, distributed collaboration, load balancing, etc.

[0084] Software as a Service (SaaS), such as application services.

[0085] In the embodiment of the present invention, in order to realize different forms of operation system management, at least one system management platform can be provided, and any system management platform can be used to manage at least one operation system. If it is necessary to adjust the system object of the operation system, the user can perform a system change operation on the operation system, and the operation system can record the user's system change operation, thereby generating a change operation log.

[0086] In a specific implementation, users can perform system change operations on the operating system through white screen operations or black screen operations. White screen operations may refer to system change operations performed through a graphical user interface or web interface provided by a system management platform such as a container publishing platform, a middleware management platform, an application configuration platform, etc. Black screen operations may refer to system change operations performed by users through a command line interface (CLI) or by directly logging into a host or network device when the system management platform does not provide a graphical user interface or web interface. This method usually relies on protocols such as SSH and Telnet, and users usually need to manually enter commands to perform system change operations.

[0087] In the embodiment of the present invention, since different system management platforms involve many ways to implement system change operations and different system management platforms are built by different parties, it is difficult to centrally transform the system management platforms. However, if the system change operations generated by the system management platform cannot be well managed, it may cause failures in the operating system and it is difficult to find the cause of the failure. Therefore, the change operation logs generated by at least one system management platform can be centrally collected to centrally manage the system management platform.

[0088] As a specific example of the present invention, if the black screen operation is implemented by a bastion host that maintains the core data of the network system from being disturbed by external users, a message engine system such as kafka can be used to obtain the change operation log directly from the bastion host. If the black screen operation is operated by a directly connected host (such as a physical machine, a virtual machine, etc.) and a network device (such as a firewall, a switch, etc.), the logs in the specified directory can be collected by a transmission tool such as filebeat for forwarding and centralizing log data, and the change operation log is obtained after parsing and sent to the message engine system.

[0089] For the system management platform involved in the white screen operation, the change operation log can be collected regularly in the database of the system management platform itself. Specifically, the timestamp of the latest change operation log collected last time can be obtained regularly, and the timestamp of the latest change operation log can be determined in the database of the system management platform itself. If the timestamp of the latest change operation log collected last time is earlier than the timestamp of the latest change operation log in the database of the system management platform itself, then it can be determined that there is a new change operation log, and the new change operation log is collected, and after adding a tag that records the source of the change operation log from the system management platform, it is sent to the message engine system.

[0090] Step 102, determining a target system object associated with the change operation log in the system objects;

[0091] In a specific implementation, a user's system change operation may result in a configuration change of at least one system object. Thus, a system object that may be affected by the system change operation corresponding to the change operation log may be searched in the system objects as the target system object associated with the change operation log.

[0092] Step 103, obtaining a system change approval work order;

[0093] Subsequently, in order to avoid failures in the operating system and adjust the system objects, it is usually necessary to initiate a system change approval work order in advance to determine whether the adjustment of the system objects in the operating system is allowed. Therefore, in order to determine whether the system change operation corresponding to the change operation log is allowed, the system change approval work order can be obtained.

[0094] Step 104: based on the system change approval work order and the target system object associated with the change operation log, confirm whether the system change operation corresponding to the change operation log meets the preset change condition;

[0095] In a specific implementation, based on the system change approval work order and the target system object associated with the change operation log, the target system object affected by the system change operation can be determined according to the change operation log, and further confirmed whether the change of the target system object is allowed according to the system change approval work order, so as to confirm whether the system change operation corresponding to the change operation log meets the preset change conditions.

[0096] Among them, the preset change condition may include the target system object being recorded in the system change approval work order.

[0097] Step 105: If the system change operation corresponding to the change operation log does not meet the preset change condition, a change prompt is issued for the system change operation.

[0098] In an embodiment of the present invention, if the system change operation corresponding to the change operation log does not meet the preset change conditions, then it can be considered that the system change operation corresponding to the change operation log has modified the system object that has not been approved and confirmed, and the system change operation corresponding to the change operation log is not allowed. At this time, in order to ensure the security of the operating system, a change prompt can be issued for the system change operation. The change prompt can be used to remind the management personnel of the operating system that the operating system currently has system objects that have been modified without permission, and there may be security risks. The change prompt can also be used to remind the initiator of the system change operation corresponding to the change operation log that he needs to explain the reason for modifying the system object.

[0099] Through the system change processing method provided by the embodiment of the present invention, the change operation log generated by at least one system management platform is collected; wherein the system management platform is used to manage at least one operating system respectively; the operating system includes at least one system object; the target system object associated with the change operation log is determined in the system object; a system change approval work order is obtained; based on the system change approval work order and the target system object associated with the change operation log, whether the system change operation corresponding to the change operation log meets the preset change conditions; if the system change operation corresponding to the change operation log does not meet the preset change conditions, a change prompt is issued for the system change operation. In this way, the change operation logs generated by the system management platform can be centralized, and the system objects that may be affected by the change operation logs can be determined, and compared with the system objects in the system change approval work order to determine whether the system change operation corresponding to the change operation log belongs to the allowed system change operation, and a prompt is issued in time when the system change operation is not allowed, so as to better maintain the stability of the operating system.

[0100] In one embodiment of the present invention, the method further comprises:

[0101] S11, determining a risk level of the change operation log according to the impact scope of the change operation log on the system object in the operation system.

[0102] In a specific implementation, different system change operations may have an impact on different types and numbers of system objects. Different system objects themselves may also have different importance levels. If a system change operation affects more types of system objects, or a larger number of system objects, or system objects with a higher importance level, then it can be considered that the system change operation recorded in the current change operation log has a larger impact on the system objects in the operating system. If a system change operation affects fewer types of system objects, or a smaller number of system objects, or system objects with a lower importance level, then it can be considered that the system change operation recorded in the current change operation log has a smaller impact on the system objects in the operating system.

[0103] Thus, the risk level of the change operation log can be determined according to the scope of influence of the change operation log on the system object in the operation system. The risk level classification method can be determined according to actual needs. For example, level 0, level 1, level 2, or ordinary, important, very important, etc., the present invention does not limit this.

[0104] In a specific implementation, different risk levels can be preset, and corresponding field information can be set for different risk levels, such as operation behavior information, operation system information, system management platform information, etc. The impact range of the change operation log on the system object in the operation system can be determined by keyword matching, and the risk level of the change operation log can be obtained.

[0105] In one embodiment of the present invention, the step of confirming whether the system change operation corresponding to the change operation log meets the preset change condition based on the system change approval work order, the change operation log, and the association relationship between the change operation log and the system object includes:

[0106] S21, taking the change operation log whose risk level meets the preset risk condition as the target change operation log;

[0107] In the specific implementation, if the risk level of the change operation log is low, it can be considered that the system change operation corresponding to the change operation log has no significant impact on the operating system. If the risk level of the change operation log is high, it can be considered that the system change operation corresponding to the change operation log may have a significant impact on the operating system.

[0108] For change operation logs with higher risk levels, it is necessary to further confirm whether the system change operation is allowed. For change operation logs with lower risk levels, since they do not have a significant impact on the operating system, it is not necessary to further confirm whether the system change operation is allowed.

[0109] Therefore, a risk condition can also be set, and the risk condition can be to use the change operation logs with a risk level greater than a preset risk threshold as the target change operation logs that need to be further processed. In this way, only the change operation logs that may have a significant impact on the operating system can be extracted, further improving the processing efficiency.

[0110] S22: based on the system change approval work order and the association relationship between the change operation log and the system object, confirm whether the system change operation corresponding to the target change operation log meets a preset change condition.

[0111] Afterwards, based on the system change approval work order and the association between the change operation log and the system object, it can be confirmed whether the system change operation corresponding to the target change operation log meets the preset change conditions to determine whether the system change operation corresponding to the change operation log is allowed.

[0112] In an embodiment of the present invention, the step of determining, in the system object, a target system object associated with the change operation log comprises:

[0113] S31, extracting the system object recorded in the change operation log as the operation object;

[0114] In the embodiment of the present invention, the change operation log may record the system object modified by the system change operation, and the system object recorded in the change operation log may be extracted as the operation object.

[0115] S32, determining, among the system objects of the operation system, an associated object associated with the operation object;

[0116] Specifically, there can be a hierarchical relationship between system objects, and the upper-level system objects can affect the lower-level system objects. For example, the firewall is associated with the switch, the switch is associated with the corresponding host, the host is associated with the virtual machine, and the host and virtual machine are associated with the corresponding PaaS components. If the application service is deployed based on containers, the host corresponding to the container platform and the lower-level switch can be associated with the application service.

[0117] Thus, the associated objects associated with the operation object can be determined in the system objects of the operation system, so that the associated objects that will be affected by the system change operation can be obtained.

[0118] In a specific implementation, a configuration management database component (CMDB) can be set up, and the association relationship between system objects at different levels can be recorded in the CMDB component. After obtaining the change operation log, the associated object associated with the operation object can be determined through the CMDB component.

[0119] S33: Use the operation object and the associated object as target system objects corresponding to the change operation log.

[0120] Thereafter, both the operation object and the associated object may be used as the target system object corresponding to the change operation log, so that it is possible to fully analyze which system objects are affected by different change operation logs, thereby better maintaining the operation system.

[0121] In one embodiment of the present invention, the step of confirming whether the system change operation corresponding to the change operation log meets the preset change condition based on the system change approval work order and the target system object associated with the change operation log includes:

[0122] S41, extracting the system object recorded in the system change approval work order;

[0123] In a specific implementation, the system change approval work order may record the system objects that need to be changed and the reasons for the changes. The reasons for the changes may be the purpose that the administrator wants to achieve by changing the system objects, such as version release, bug fixes, fault handling, etc.

[0124] In order to determine whether the system change operation corresponding to the change operation log has been approved, the system object recorded in the system change approval work order can be extracted.

[0125] S42, determining whether the system object recorded in the system change approval work order matches the target system object associated with the change operation log;

[0126] Thereafter, it may be determined whether the system object recorded in the system change approval work order matches the target system object associated with the change operation log to determine whether the system object has been changed according to the system change approval work order without changing other system objects.

[0127] S43, when the system object recorded in the system change approval work order matches the target system object associated with the change operation log, determining that the system change operation corresponding to the change operation log meets the preset change condition.

[0128] When the system object recorded in the system change approval work order matches the target system object associated with the change operation log, it can be considered that the system object has been changed in accordance with the system change approval work order, and other system objects have not been changed. At this time, it can be considered that the system change operation corresponding to the change operation log meets the preset change conditions.

[0129] In a specific implementation, after confirming whether the system change operation corresponding to the change operation log meets the preset change conditions based on the system change approval work order and the target system object associated with the change operation log, the change operation log can be marked and stored in a database according to whether the system change operation corresponding to the change operation log meets the preset change conditions, so as to further analyze the cause of the failure of the operation system.

[0130] In an embodiment of the present invention, when the system object recorded in the system change approval work order matches the target system object associated with the change operation log, the step of determining whether the system change operation corresponding to the change operation log satisfies the preset change condition includes:

[0131] S51, extracting the change behavior recorded in the change operation log and the change behavior recorded in the system change approval work order;

[0132] In a specific implementation, the change operation log may further record the change behavior, that is, how the administrator adjusts the system object. The change behavior may include restarting, shutting down, updating, switching, etc. of the changed object.

[0133] At the same time, the system change approval work order may also record the change behavior. In order to ensure that the system object is changed as expected, the change behavior recorded in the change operation log and the change behavior recorded in the system change approval work order may be extracted.

[0134] S52, determining whether the change behavior recorded in the change operation log matches the change behavior recorded in the system change approval work order;

[0135] Thereafter, it may be determined whether the system object has been changed as expected by determining whether the change behavior recorded in the change operation log matches the change behavior recorded in the system change approval work order.

[0136] S53, when the system object recorded in the system change approval work order matches the target system object associated with the change operation log, and the change behavior recorded in the change operation log matches the change behavior recorded in the system change approval work order, it is determined that the system change operation corresponding to the change operation log meets the preset change condition.

[0137] When the system object recorded in the system change approval work order matches the target system object associated with the change operation log, and the change behavior recorded in the change operation log matches the change behavior recorded in the system change approval work order, it can be considered that the system object has been changed in accordance with the system change approval work order, and other system objects have not been changed, and the change method is consistent with the approval work order. At this time, it can be considered that the system change operation corresponding to the change operation log meets the preset change conditions.

[0138] In an embodiment of the present invention, when the system object recorded in the system change approval work order matches the target system object associated with the change operation log, the step of determining whether the system change operation corresponding to the change operation log satisfies the preset change condition includes:

[0139] S61, extracting the change time recorded in the change operation log and the change time range recorded in the system change approval work order;

[0140] In a specific implementation, since daytime is usually the time period when the operation system normally provides services to users, managers are usually not allowed to make changes to the operation system during this time period, and changes must be made within other specified time ranges. Therefore, the change time range can also be recorded in the system change approval worksheet. By extracting the change time recorded in the change operation log and the change time range recorded in the system change approval worksheet, it can be determined whether the system change operation of the manager has an adverse impact on the normal operation of the operation system.

[0141] S62, determining whether the change time recorded in the change operation log matches the change time range recorded in the system change approval work order;

[0142] Thus, it can be determined whether the change time recorded in the change operation log matches the change time range recorded in the system change approval work order, so as to determine whether the management personnel change the operation system according to the time range required in the system change approval work order.

[0143] S63, when the system object recorded in the system change approval work order matches the target system object associated with the change operation log, and the change time recorded in the change operation log matches the change time range recorded in the system change approval work order, it is determined that the system change operation corresponding to the change operation log meets the preset change condition.

[0144] When the system object recorded in the system change approval work order matches the target system object associated with the change operation log, and the change time recorded in the change operation log matches the change time range recorded in the system change approval work order, it can be considered that the system object has been changed in accordance with the system change approval work order, and other system objects have not been changed, and the change time is consistent with the approval work order. At this time, it can be considered that the system change operation corresponding to the change operation log meets the preset change conditions.

[0145] In one embodiment of the present invention, the method further comprises:

[0146] S71, if a fault indication is received, determining a system object corresponding to the fault indication;

[0147] In the specific implementation, system objects at different levels of the operation system can be monitored. If a system object in the operation system fails, a fault indication can be generated to warn of abnormal conditions in the operation system. Fault indications can also be generated by front-line sales staff reporting faults.

[0148] When a fault indication is received, the fault indication may be parsed to determine the system object corresponding to the fault prompt.

[0149] S72, searching for the change operation log corresponding to the fault prompt based on the target system object associated with the change operation log;

[0150] Afterwards, you can search for the target system object associated with the change operation log, find the change operation log that is consistent with the system object corresponding to the fault prompt, and find the change operation log corresponding to the fault prompt to check whether the fault prompt may be related to the system change operation.

[0151] In a specific implementation, in the process of searching for the change operation log corresponding to the fault prompt, the change operation log within a preset time period before the fault prompt is generated can be searched to better locate the cause of the possible fault.

[0152] Afterwards, the fault prompt can be further compared with the change operation log to determine whether the system object, the operating system described by the system object, and the level to which the system object belongs are completely consistent. If they are completely consistent, it can be considered that the change operation log is the change operation log corresponding to the fault prompt. If they are not completely consistent, for example, the operating system is the same, but the change operation logs of the system objects are different, it is possible that the change operation log affects other system objects associated with the changed system object, causing a system failure. At this time, it is possible to further analyze whether other system objects associated with the changed system object and the level to which other system objects belong match the fault prompt. If they match, it can also be considered that the fault prompt corresponds to the change operation log.

[0153] S73: issuing a fault-related prompt for the change operation log corresponding to the fault prompt.

[0154] After determining the change operation log corresponding to the fault prompt, a fault-related prompt may be issued to the management personnel so that the management personnel can quickly locate the cause of the fault.

[0155] It should be noted that, for the sake of simplicity, the method embodiments are described as a series of action combinations, but those skilled in the art should be aware that the embodiments of the present invention are not limited by the order of the actions described, because according to the embodiments of the present invention, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all preferred embodiments, and the actions involved are not necessarily required by the embodiments of the present invention.

[0156] Reference Figure 2 , shows a structural block diagram of a system change processing device provided in an embodiment of the present invention, which may specifically include the following modules:

[0157] A collection module, used to collect change operation logs generated by at least one system management platform; wherein the system management platform is used to manage at least one operation system; the operation system includes at least one system object;

[0158] A target system object determination module, used to determine a target system object associated with the change operation log in the system objects;

[0159] Condition identification module, used to obtain system change approval work orders;

[0160] A matching module, used to confirm whether the system change operation corresponding to the change operation log meets the preset change condition based on the system change approval work order and the target system object associated with the change operation log;

[0161] The change prompt module is used to issue a change prompt for the system change operation if the system change operation corresponding to the change operation log does not meet the preset change condition.

[0162] Optionally, the device further comprises:

[0163] The risk identification module is used to determine the risk level of the change operation log according to the impact scope of the change operation log on the system object in the operation system.

[0164] Optionally, the matching module includes:

[0165] A first matching submodule, configured to use the change operation log whose risk level meets a preset risk condition as a target change operation log;

[0166] Based on the system change approval work order and the association relationship between the change operation log and the system object, it is confirmed whether the system change operation corresponding to the target change operation log meets the preset change condition.

[0167] Optionally, the target system object determination module includes:

[0168] An operation object extraction submodule, used to extract the system object recorded in the change operation log as the operation object;

[0169] An associated object determination submodule, used to determine an associated object associated with the operation object in the system object of the operation system;

[0170] The target system object determination submodule is used to use the operation object and the associated object as the target system object corresponding to the change operation log.

[0171] Optionally, the matching module includes:

[0172] An object extraction submodule, used to extract the system objects recorded in the system change approval work order;

[0173] An object matching submodule, used to determine whether the system object recorded in the system change approval work order matches the target system object associated with the change operation log;

[0174] The second matching submodule is used to determine whether the system change operation corresponding to the change operation log meets the preset change condition when the system object recorded in the system change approval work order matches the target system object associated with the change operation log.

[0175] Optionally, the matching module includes:

[0176] A behavior extraction submodule, used to extract the change behavior recorded in the change operation log and the change behavior recorded in the system change approval work order;

[0177] A behavior matching submodule, used to determine whether the change behavior recorded in the change operation log matches the change behavior recorded in the system change approval work order;

[0178] The third matching submodule is used to determine that the system change operation corresponding to the change operation log meets the preset change condition when the system object recorded in the system change approval work order matches the target system object associated with the change operation log, and the change behavior recorded in the change operation log matches the change behavior recorded in the system change approval work order.

[0179] Optionally, the matching module includes:

[0180] A time extraction submodule, used to extract the change time recorded in the change operation log and the change time range recorded in the system change approval work order;

[0181] A time matching submodule, used to determine whether the change time recorded in the change operation log matches the change time range recorded in the system change approval work order;

[0182] The fourth matching submodule is used to determine that the system change operation corresponding to the change operation log meets the preset change conditions when the system object recorded in the system change approval work order matches the target system object associated with the change operation log, and the change time recorded in the change operation log matches the change time range recorded in the system change approval work order.

[0183] Optionally, the device further comprises:

[0184] A fault object determination module, for determining the system object corresponding to the fault indication if a fault indication is received;

[0185] A log search module, used to search the change operation log corresponding to the fault prompt based on the target system object associated with the change operation log;

[0186] The fault association prompt module is used to issue a fault association prompt for the change operation log corresponding to the fault prompt.

[0187] As for the device embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0188] In addition, an embodiment of the present invention further provides an electronic device, such as Figure 3 As shown, it includes a processor 301, a communication interface 302, a memory 303 and a communication bus 304, wherein the processor 301, the communication interface 302, and the memory 303 communicate with each other through the communication bus 304.

[0189] Memory 303, used for storing computer programs;

[0190] The processor 301 is used to execute the program stored in the memory 303 to implement the following steps:

[0191] Collecting change operation logs generated by at least one system management platform; wherein the system management platform is used to manage at least one operation system; the operation system includes at least one system object;

[0192] Determining a target system object associated with the change operation log in the system objects;

[0193] Obtain system change approval work order;

[0194] Based on the system change approval work order and the target system object associated with the change operation log, confirm whether the system change operation corresponding to the change operation log meets the preset change condition;

[0195] If the system change operation corresponding to the change operation log does not meet the preset change condition, a change prompt is issued for the system change operation.

[0196] Optionally, the method further comprises:

[0197] The risk level of the change operation log is determined according to the impact scope of the change operation log on the system object in the operation system.

[0198] Optionally, the step of confirming whether the system change operation corresponding to the change operation log meets a preset change condition based on the system change approval work order, the change operation log, and the association relationship between the change operation log and the system object includes:

[0199] The change operation log whose risk level meets the preset risk condition is used as the target change operation log;

[0200] Based on the system change approval work order and the association relationship between the change operation log and the system object, it is confirmed whether the system change operation corresponding to the target change operation log meets the preset change condition.

[0201] Optionally, the step of determining, in the system object, a target system object associated with the change operation log comprises:

[0202] Extracting the system object recorded in the change operation log as the operation object;

[0203] Determining, among the system objects of the operation system, an associated object associated with the operation object;

[0204] The operation object and the associated object are used as target system objects corresponding to the change operation log.

[0205] Optionally, the step of confirming whether the system change operation corresponding to the change operation log meets a preset change condition based on the system change approval work order and the target system object associated with the change operation log includes:

[0206] Extracting the system object recorded in the system change approval work order;

[0207] Determine whether the system object recorded in the system change approval work order matches the target system object associated with the change operation log;

[0208] In a case where the system object recorded in the system change approval work order matches the target system object associated with the change operation log, it is determined that the system change operation corresponding to the change operation log meets the preset change condition.

[0209] Optionally, when the system object recorded in the system change approval work order matches the target system object associated with the change operation log, the step of determining whether the system change operation corresponding to the change operation log satisfies a preset change condition includes:

[0210] Extracting the change behavior recorded in the change operation log and the change behavior recorded in the system change approval work order;

[0211] Determine whether the change behavior recorded in the change operation log matches the change behavior recorded in the system change approval work order;

[0212] When the system object recorded in the system change approval work order matches the target system object associated with the change operation log, and the change behavior recorded in the change operation log matches the change behavior recorded in the system change approval work order, it is determined that the system change operation corresponding to the change operation log meets the preset change conditions.

[0213] Optionally, when the system object recorded in the system change approval work order matches the target system object associated with the change operation log, the step of determining whether the system change operation corresponding to the change operation log satisfies a preset change condition includes:

[0214] Extract the change time recorded in the change operation log and the change time range recorded in the system change approval work order;

[0215] Determine whether the change time recorded in the change operation log matches the change time range recorded in the system change approval work order;

[0216] When the system object recorded in the system change approval work order matches the target system object associated with the change operation log, and the change time recorded in the change operation log matches the change time range recorded in the system change approval work order, it is determined that the system change operation corresponding to the change operation log meets the preset change conditions.

[0217] Optionally, the method further comprises:

[0218] If a fault indication is received, determining a system object corresponding to the fault indication;

[0219] Based on the target system object associated with the change operation log, searching for the change operation log corresponding to the fault prompt;

[0220] A fault-related prompt is issued for the change operation log corresponding to the fault prompt.

[0221] The communication bus mentioned in the above terminal can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. The communication bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, only one thick line is used in the figure, but it does not mean that there is only one bus or one type of bus.

[0222] The communication interface is used for communication between the above terminal and other devices.

[0223] The memory may include a random access memory (RAM) or a non-volatile memory, such as at least one disk memory. Optionally, the memory may also be at least one storage device located away from the aforementioned processor.

[0224] The above-mentioned processor can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.

[0225] like Figure 4 As shown, in another embodiment provided by the present invention, a computer-readable storage medium 401 is also provided, in which instructions are stored. When the computer-readable storage medium is run on a computer, the computer executes the system change processing method described in the above embodiment.

[0226] In another embodiment of the present invention, a computer program product including instructions is provided. When the computer program product is run on a computer, the computer executes the method for processing system changes described in the above embodiment.

[0227] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented by software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present invention is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from a website site, computer, server or data center to another website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrated. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state hard disk Solid State Disk (SSD)), etc.

[0228] It should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or device including the elements.

[0229] Each embodiment in this specification is described in a related manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0230] The above description is only a preferred embodiment of the present invention and is not intended to limit the protection scope of the present invention. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention are included in the protection scope of the present invention.

Claims

1. A method for processing system changes, characterized in that: include: Collecting a change operation log generated by at least one system management platform; wherein the system management platform is used to manage at least one operation system; the operation system includes at least one system object; Determining a target system object associated with the change operation log in the system objects; Obtain system change approval work order; Based on the system change approval work order and the target system object associated with the change operation log, confirm whether the system change operation corresponding to the change operation log meets the preset change condition; If the system change operation corresponding to the change operation log does not meet the preset change condition, a change prompt is issued for the system change operation.

2. The method according to claim 1, characterized in that The method further comprises: The risk level of the change operation log is determined according to the impact scope of the change operation log on the system object in the operation system.

3. The method according to claim 2, characterized in that The step of confirming whether the system change operation corresponding to the change operation log meets the preset change condition based on the system change approval work order, the change operation log, and the association relationship between the change operation log and the system object includes: The change operation log whose risk level meets the preset risk condition is used as the target change operation log; Based on the system change approval work order and the association relationship between the change operation log and the system object, it is confirmed whether the system change operation corresponding to the target change operation log meets the preset change condition.

4. The method according to claim 1, characterized in that: The step of determining the target system object associated with the change operation log in the system object comprises: Extracting the system object recorded in the change operation log as the operation object; Determining, among the system objects of the operation system, an associated object associated with the operation object; The operation object and the associated object are used as target system objects corresponding to the change operation log.

5. The method according to claim 1, characterized in that The step of confirming whether the system change operation corresponding to the change operation log meets the preset change condition based on the system change approval work order and the target system object associated with the change operation log includes: Extracting the system object recorded in the system change approval work order; Determine whether the system object recorded in the system change approval work order matches the target system object associated with the change operation log; In a case where the system object recorded in the system change approval work order matches the target system object associated with the change operation log, it is determined that the system change operation corresponding to the change operation log meets the preset change condition.

6. The method according to claim 5, characterized in that When the system object recorded in the system change approval work order matches the target system object associated with the change operation log, the step of determining whether the system change operation corresponding to the change operation log meets the preset change condition includes: Extracting the change behavior recorded in the change operation log and the change behavior recorded in the system change approval work order; Determine whether the change behavior recorded in the change operation log matches the change behavior recorded in the system change approval work order; When the system object recorded in the system change approval work order matches the target system object associated with the change operation log, and the change behavior recorded in the change operation log matches the change behavior recorded in the system change approval work order, it is determined that the system change operation corresponding to the change operation log meets the preset change conditions.

7. The method according to claim 5, characterized in that When the system object recorded in the system change approval work order matches the target system object associated with the change operation log, the step of determining whether the system change operation corresponding to the change operation log meets the preset change condition includes: Extract the change time recorded in the change operation log and the change time range recorded in the system change approval work order; Determine whether the change time recorded in the change operation log matches the change time range recorded in the system change approval work order; When the system object recorded in the system change approval work order matches the target system object associated with the change operation log, and the change time recorded in the change operation log matches the change time range recorded in the system change approval work order, it is determined that the system change operation corresponding to the change operation log meets the preset change conditions.

8. The method according to claim 1, characterized in that The method further comprises: If a fault indication is received, determining a system object corresponding to the fault indication; Based on the target system object associated with the change operation log, searching for the change operation log corresponding to the fault prompt; A fault-related prompt is issued for the change operation log corresponding to the fault prompt.

9. A system change processing device, characterized in that: include: A collection module, used to collect change operation logs generated by at least one system management platform; wherein the system management platform is used to manage at least one operation system; the operation system includes at least one system object; A target system object determination module, used to determine a target system object associated with the change operation log in the system objects; Condition identification module, used to obtain system change approval work orders; A matching module, used to confirm whether the system change operation corresponding to the change operation log meets the preset change condition based on the system change approval work order and the target system object associated with the change operation log; The change prompt module is used to issue a change prompt for the system change operation if the system change operation corresponding to the change operation log does not meet the preset change condition.

10. An electronic device, characterized in that: It includes a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other through the communication bus; The memory is used to store computer programs; The processor is used to implement the method according to any one of claims 1 to 8 when executing the program stored in the memory.

11. A computer-readable medium having instructions stored thereon, which, when executed by one or more processors, cause the processors to perform the method according to any one of claims 1 to 8.

Images