Disclosure of Invention
An object of the embodiments of the present application is to provide a system event review method, a network management system, a network management device, and a storage medium, so as to solve the problems of poor readability and high professional requirements in the prior art.
The embodiment of the application provides a system event review method, which comprises the following steps: when the triggering of a preset record starting condition is monitored, generating and storing an operation record according to each operation request initiated by the front end of the system and the response corresponding to each operation request returned by the back end of the system until the triggering of the preset record ending condition; and when a playback request is received, performing page playing according to a target operation record corresponding to the playback request.
In the implementation process, by setting the recording start condition and the recording end condition in the system, the associated record of all operation requests generated at the front end of the system and response data of each operation request returned by the back end can be realized from the time when the recording start condition is triggered to the time when the recording end condition is triggered, and further, when the review is needed (such as in the scenes of shift handover, review summary, investigation problem, operation audit and the like), the recorded operation record can be used for playing back the information in the record, so that the operation needed to be reviewed can be presented in a more visual mode. Compared with the mode of consulting the operation log, the scheme of the embodiment of the application carries out operation review in the page playing mode, has high readability, has low professional capability limitation on consulting staff and has better interactive experience, thereby improving the practical use value of the system.
Further, the recording start condition includes: receiving preset equipment alarm information; the equipment alarm information is information reported when the network equipment fails.
In the implementation process, the device alarm information reported when the network device fails is configured as the record start condition, so that the system can automatically record related operation requests and response data whenever the device fails, the follow-up review is convenient to know which operations are performed on the device failure, the record of useless information can be reduced, and the follow-up review of effective information is convenient.
Further, the recording end condition includes: receiving equipment recovery information and/or recording time reaching a preset recording duration; the equipment recovery information is information reported when the network equipment is recovered from faults.
In the implementation process, the received device recovery information is set as the recording ending condition, so that the recording can be ended after the device recovers from the fault, thereby reducing the recording of useless information and facilitating the subsequent review of effective information. By setting the recording time to reach the preset recording duration as the recording ending condition, the long-time and constant recording of the information can be avoided, so that the size of the recording can be effectively controlled, and the recording effectiveness is improved.
Further, each operation request generated by the system front end includes: request address and request parameters.
In the actual application process, in the request generated by the system, the most core content is the request address and the request parameter. In the implementation process, the request address and the request parameter are recorded, so that the recording size can be effectively reduced, and the storage space is saved.
Further, while generating and storing an operation record according to each operation request initiated by the front end and the response corresponding to each operation request returned by the back end, the method further comprises: and carrying out association record on the generation time of each operation request, each operation request initiated by the front end and the response returned by the back end.
In the implementation process, the generation time of each operation request is also recorded in a correlated way, so that when the operation requests are reviewed, the operation requests can be reviewed in sequence strictly according to the generation time of each operation request, and meanwhile, the review of the designated time and the fast forward and backward during playing are facilitated, and more flexible playing control can be realized.
Further, performing page playing according to the target operation record corresponding to the playback request, including: simulating a request operation for a first operation request in the target operation record, and rendering a page according to a response corresponding to the first operation request; and simulating a request operation for a second operation request in the target operation record, and rendering the page according to a response corresponding to the second operation request until the page is rendered according to a response corresponding to the last operation request in the target operation record.
In the implementation process, by simulating the operation requests in the target operation records in sequence and rendering the response data corresponding to the operation requests, the operation performed at the time is reproduced while the actual outgoing requests are not needed, and the interference to the system and the external equipment in the reviewing process can be avoided.
The embodiment of the application also provides a network management system, which comprises: an operation record trigger configured with a record start condition and a record end condition, and configured to generate and store an operation record according to each operation request initiated by the front end of the system and a response corresponding to each operation request returned by the back end of the system when the record start condition is triggered, until a preset record end condition is triggered; and the player is used for playing the page on the front-end interface according to the target operation record corresponding to the playback request when the playback request is received.
According to the network management system, the operation record trigger is configured, and the record starting condition and the record ending condition are configured in the operation record trigger, so that the associated record of response data of all operation requests generated at the front end of the system and all operation requests returned at the rear end of the system can be realized from the time when the record starting condition is triggered to the time when the record ending condition is triggered through the operation record trigger, and further, when the operation requests are required to be reviewed, information in the operation record can be played back through the player, and therefore operations required to be reviewed can be presented in a more visual mode. Compared with the mode of consulting the operation log, the scheme of the embodiment of the application carries out operation review in the page playing mode, has high readability, has low professional capability limitation on consulting staff and has better interactive experience, thereby improving the practical use value of the system.
Further, the front-end interface is configured with a first program for rendering the response data after receiving the response data, and a second program for performing page jumping; the player multiplexes the first program and the second program to perform rendering of response data and page jumping in the page playing process.
In the implementation scheme, the player can realize lower-cost page playing by multiplexing the first program and the second program of the front-end interface, and is beneficial to popularization in industrial practice.
The embodiment of the application also provides a network management device, which comprises: a processor, a display, a memory; the memory stores the realization program of the operation record trigger and the player in the network management system; the processor is configured to load and execute the implementation program stored in the memory, so as to implement any one of the system event review methods described above.
There is also provided in an embodiment of the present application a computer-readable storage medium having stored therein a computer program which, when run on a computer, causes the computer to perform the system event review method of any one of the above.
Detailed Description
The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application.
Embodiment one:
in order to solve the problems of poor readability and high professional requirements in the prior art, the embodiment of the application provides a system event review method and a network management system. Referring to fig. 1, fig. 1 is a schematic flow chart of a system event review method provided in an embodiment of the present application, including:
s101: when the triggering of the preset record starting condition is monitored, generating and storing an operation record according to each operation request initiated by the front end of the system and the response corresponding to each operation request returned by the back end of the system until the triggering of the preset record ending condition.
In the embodiment of the application, an operation record trigger can be configured in the system, and the operation record trigger can be realized through an event handle. In the operation record trigger, the record start condition and the record end condition may be configured by event handles. When the recording start condition is triggered, the response data corresponding to the operation request generated by the front end and the operation request returned by the back end of the automatic recording system are recorded. When the recording end condition is triggered, recording may be ended.
In the embodiment of the present application, the recording start condition may be one or more, and the specific content may be configured by an engineer according to actual needs.
For example, the recording start condition may be set to include receiving preset device alert information. The device alarm information refers to information reported when a network device fails.
Generally, when the network device reports the device alarm information, the network device indicates that the network device has a fault, and at the moment, a network management system is required to perform fault processing, and the information in the fault processing process has higher recall value, so that the recording of the information in the fault processing process with higher recall value can be effectively ensured by setting the recording start condition including receiving the preset device alarm information.
Further, for some situations with a review demand for a specific period, a recording start condition may also be set including the current time reaching the set recording time point. Thus, when the system finds that the current time reaches the set recording time point, the system can automatically record each operation request generated at the front end of the system and response data returned by the rear end.
In the embodiment of the application, the recording end condition may be one or more, and the specific content may be configured by an engineer according to actual needs.
For example, the recording end condition may be set to include receiving device recovery information. The reception of the device recovery information is information reported when the network device is recovered from a failure.
Thus, when the network equipment is found to recover from the fault, the recording can be finished timely, so that the recording of useless information is reduced, and the follow-up review of effective information is facilitated.
In addition, the recording end condition can be set, wherein the recording time reaches the preset recording duration, so that long-time and constant recording of information can be avoided, the size of recording can be effectively controlled, and the recording effectiveness is improved.
It should be understood that the recording end condition may be set including the recording time reaching the preset recording duration while the setting of the recording end condition includes receiving the device resume information. Therefore, when the network management system does not receive the equipment recovery information due to network abnormality and other conditions, the useless information can be prevented from being recorded all the time based on the recording ending condition that the recording time reaches the preset recording duration, so that the system load is effectively reduced.
In this embodiment of the present application, the preset recording duration may be set by an engineer according to actual needs, and it is generally recommended that the preset duration set should be greater than the conventional fault maintenance duration.
In the embodiment of the present application, in order to facilitate the rapid understanding of the event corresponding to the operation by the reviewer during the subsequent review, when each recording start condition and the corresponding recording end condition are set, the corresponding event name may be set, so that during playback, the event name may be correspondingly displayed for the information recorded between each pair of recording start conditions and recording end conditions, so that the reviewer may understand what event the process aims for.
Illustratively, the recording start condition, the recording end condition, the event name may be configured in the manner shown in the following table one, thereby facilitating management:
list one
In the embodiment of the application, when each operation request generated at the front end of the system is recorded, the request address and the request parameter of each operation request generated at the front end of the system can be recorded, so that the recording size is effectively reduced, and the storage space is saved.
In addition, in the embodiment of the present application, the generation time of each operation request may also be recorded and associated with the operation request and response data returned by the back end.
By way of example, the recording may be performed in the manner of table two below:
watch II
Wherein url. Showalarm characterizes the address requesting display of alarm details, alarm ID characterizes the request parameter alarm id, url. Showdevcfg characterizes the address requesting display device configuration, devID characterizing device ID, url.setDevCfg characterizes the address requesting setting device configuration, cfgmfo characterizes the configuration content.
It should be noted that table two above is only one possible example of an embodiment of the present application. In this embodiment of the present application, the recorded information may record other information, such as the operator identifier of each operation, as required, in addition to the information in table two, which is not limited herein.
S102: and when receiving a playback request, performing page playing according to a target operation record corresponding to the playback request.
In the embodiment of the application, a player can be configured in the system. The reviewer can issue a playback request according to the own requirement, and carry a time interval required to be reviewed in the playback request, or designate an operation record range required to be reviewed, so as to obtain a target operation record from all the operation records.
In the embodiment of the application, the player can simulate the request operation for the first operation request in the target operation record, and render the page according to the response data corresponding to the first operation request.
Then, the player can simulate the request operation for the second operation request in the target operation record, and render the page according to the response data corresponding to the second operation request.
And repeating the process until the last operation request in the target operation record simulates the request operation, and rendering the page according to response data corresponding to the last operation request.
It should be understood that in the above procedure, the first operation request refers to the one whose time of the timestamp record is earliest in the target operation record, the second operation request refers to the one whose time of the timestamp record is earliest in the target operation record, and so on.
It should be noted that, for the scheme of not recording the time stamp, the operation record is obtained according to the generation sequence of each operation request, so that simulation and rendering are only required according to the sequence of each item in the operation record.
It should be understood that, in the embodiment of the present application, the request operation simulated for the operation request in the operation record is not actually sent to the request address in the operation record, but is called to the response data corresponding to the operation request in the operation record through the interface of the player, so as to perform rendering of the response data. The process does not re-access the device requesting the address, so that the logic confusion of the external device and the data in the system is avoided, and the simulation reproduction of the past operation is only realized.
For example, in the case of table two above, the player first records at time t1, inputs the address url. At this time, the system request is not sent to url. Showalarm, but the player calls the "alarm content" in the operation record at time t1 to render, and the rendering page is displayed.
Then, the address request interface inputs the address url. Showdevcfg to be requested, and generates a system request containing the request parameter devID. At this time, the system request is not sent to url. Showdevcfg, but the player calls "device configuration" in the operation record at time t2 to render, and the rendered page is displayed.
Next, the address to be requested url.setdevcfg is input at the address request interface, and a system request including the request parameters devID and cfgmnfo is generated. At this time, the system request is not sent to url. Setdevcfg, but the player calls "configure success prompt" in the operation record at time t3 to render, and the rendered page is displayed.
The embodiment of the application also provides a network management system, which is shown in fig. 2 and comprises an operation record trigger and a player.
As described above, the operation record trigger in the present network management system may be implemented by an event handler, and the record start condition and the record end condition may be configured by the event handler.
The operation record trigger may implement the operation related to step S101 in the foregoing system event review method, which is not described herein.
The player may cooperate with the front end interface of the network management system to implement the operation related to step S102 in the foregoing system event review method, which is not described herein again.
It should be appreciated that, for a network management system, its front-end interface is typically configured with a first program for rendering response data after receiving the response data, and a second program for performing a page jump. In the embodiment of the application, when the player is configured, the player can be configured to multiplex the first program and the second program so as to render response data and skip pages in the page playing process. Therefore, the player multiplexes the first program and the second program of the front end interface, so that lower-cost page playing can be realized, and popularization in industrial practice is facilitated.
In the embodiment of the application, a time axis may be provided in the player, a time point of each request may be presented, and an event name corresponding to each time point may be presented.
In addition, in the embodiment of the application, functions of playing, pausing, advancing, backing and the like can be further provided in the player so as to facilitate flexible operation. Such as shown in fig. 3.
In this embodiment of the present application, a specific implementation structure of a network management system may be shown in fig. 4, where a player is multiplexed with a front-end interface, the front-end interface of the front-end interface is connected to an operation record trigger, and the operation record trigger is connected to each network device through an alarm module, so as to implement trigger judgment on a record start condition and a record end condition, and meanwhile, the operation record trigger is further connected to a database to save and invoke a generated operation record.
In the embodiment of the present application, the network management system may be implemented by a single electronic device, but may also be implemented by a cluster formed by a plurality of electronic devices, which is not limited in the embodiment of the present application.
According to the system event review method and the network management system, by configuring one operation record trigger and configuring the record start condition and the record end condition in the operation record trigger, the operation record trigger can be used for realizing the associated record of all operation requests generated at the front end of the system and response data of each operation request returned at the rear end of the system from the time when the record start condition is triggered to the time when the record end condition is triggered, and further, when the operation record needs to be reviewed, information in the operation record can be played back through a player, so that operations needing to be reviewed can be presented in a more visual mode. Compared with the mode of consulting the operation log, the scheme of the embodiment of the application carries out operation review in the page playing mode, has high readability, has low professional capability limitation on consulting staff and has better interactive experience, thereby improving the practical use value of the system.
In addition, according to the scheme of the embodiment of the application, the original interaction logic of the front-end interface can be reused through the player, so that the operation condition after the event occurs can be truly restored at low cost.
Embodiment two:
the present embodiment provides a network management device, which includes a processor 501, a memory 502, and a display 503, as shown in fig. 5. Wherein:
the memory 502 stores therein the implementation program of the operation record trigger and player described in embodiment one.
The processor 501 is configured to load and execute the implementation program stored in the memory 502, and display the rendered page on the display 503, so as to implement the system event review method in the first embodiment.
It will be appreciated that the configuration shown in fig. 5 is merely illustrative and that the network management device may also include more or fewer components than shown in fig. 5 or have a different configuration than shown in fig. 5. Such as a network interface, network card, etc. for interfacing with a network device.
The present embodiment also provides a computer-readable storage medium, such as a floppy disk, an optical disk, a hard disk, a flash memory, a usb disk, an SD (Secure Digital Memory Card, secure digital Card) Card, an MMC (Multimedia Card) Card, or the like, in which a computer program is stored, which when executed on a computer, can cause the computer to execute the system event review method in the above-described embodiment. And will not be described in detail herein.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other manners. The above-described apparatus embodiments are merely illustrative, for example, the division of the units is merely a logical function division, and there may be other manners of division in actual implementation, and for example, multiple units or components may be combined or integrated into another system, or some features may be omitted, or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be through some communication interface, device or unit indirect coupling or communication connection, which may be in electrical, mechanical or other form.
Further, the units described as separate units may or may not be physically separate, and units displayed as units may or may not be physical units, may be located in one place, or may be distributed over a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
Furthermore, functional modules in various embodiments of the present application may be integrated together to form a single portion, or each module may exist alone, or two or more modules may be integrated to form a single portion.
In this document, 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.
Herein, a plurality refers to two or more.
The foregoing is merely exemplary embodiments of the present application and is not intended to limit the scope of the present application, and various modifications and variations may be suggested to one skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principles of the present application should be included in the protection scope of the present application.