Monitoring management method of network equipment and electronic equipment

Abstract

The invention provides a network equipment monitoring management method and electronic equipment, and is applied to the field of network equipment operation and maintenance. The monitoring management method comprises the following steps: acquiring execution information of a to-be-executed monitoring task, wherein the execution information comprises first equipment information corresponding to at least one acquisition command, second equipment information corresponding to at least one execution account and third equipment information of at least one network equipment; matching a target network device corresponding to each acquisition command from at least one network device according to the first device information, the third device information and a network device matching strategy; matching a target execution account corresponding to the target network equipment from the at least one execution account according to the second equipment information, the third equipment information and an account matching strategy; and sending a target acquisition command to the target network device according to the target execution account, and obtaining an execution result. By implementing the monitoring management method provided by the invention, the execution exception rate of the collection command is reduced, and the manual checking cost is reduced.

Description

Technical Field

[0001] This application relates to the field of network equipment operation and maintenance, and in particular to a method for monitoring and managing network equipment and an electronic device. Background Technology

[0002] With the exponential growth of network scale and the increasing complexity of operation and maintenance, network device data acquisition technology has undergone a leapfrog development from manual operation to intelligent analysis. Early networks were mainly small to medium-sized, relying on technicians to manually execute commands (such as `show interface`) via Telnet or console to obtain device status. This data acquisition was inefficient and prone to errors. Later, the SNMP protocol became mainstream, and tools such as Zabbix and Nagios achieved the timed collection of basic indicators (such as CPU and port traffic) by polling the device MIB library. Still later, scripting tools such as Ansible combined with SSH to automate command execution, and hardware mirroring technologies (such as SPAN and TAP) supported traffic capture. However, the high barrier to script development and hardware costs limited large-scale application.

[0003] Despite continuous technological advancements, the significant differences in the collection commands supported by different network devices have resulted in a very high failure rate in the execution of collection commands, which has become a core bottleneck restricting the efficiency and stability of automated data collection. Summary of the Invention

[0004] In view of this, this application provides a monitoring and management method and electronic device for network devices, which helps to reduce the execution error rate of data collection commands and reduce the cost of manual verification.

[0005] In a first aspect, this application provides a monitoring and management method for network devices, comprising: acquiring execution information of a monitoring task to be performed, wherein the execution information includes at least one first device information corresponding to a collection command, at least one second device information corresponding to an execution account, and at least one third device information of a network device;

[0006] Based on the first device information, the third device information, and the network device matching strategy, the target network device corresponding to each acquisition command is matched from the at least one network device;

[0007] Based on the second device information, the third device information, and the account matching strategy, the target execution account corresponding to the target network device is matched from the at least one execution account;

[0008] The target acquisition command is sent to the target network device according to the target execution account, and the execution result is obtained.

[0009] Secondly, this application provides an electronic device, comprising:

[0010] At least one processor; and

[0011] At least one memory storing instructions that, when executed individually or jointly by the at least one processor, cause the electronic device to perform the method as described in the first aspect. Attached Figure Description

[0012] The accompanying drawings are included to provide a further understanding of this application; they are incorporated into and constitute a part of this application. The drawings illustrate embodiments of this application and, together with this specification, serve to explain the principles of this application. In the drawings:

[0013] Figure 1 This is a flowchart illustrating a network device monitoring and management method provided in an embodiment of this application;

[0014] Figure 2 This is a schematic diagram of the creation page for a new data collection command provided in an embodiment of this application;

[0015] Figure 3 This is a schematic diagram of a target parsing script creation page provided in an embodiment of this application;

[0016] Figure 4 This is a schematic diagram of a task execution result page provided in an embodiment of this application;

[0017] Figure 5 This is a flowchart illustrating another method for monitoring and managing network devices provided in an embodiment of this application;

[0018] Figure 6 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0019] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are merely some examples or embodiments of this application. For those skilled in the art, these drawings can be applied to other similar scenarios without creative effort. Unless obvious from the context or otherwise specified, the same reference numerals in the drawings represent the same structures or operations.

[0020] As indicated in this application, unless the context clearly indicates otherwise, the words "a," "an," "an," and / or "the" do not specifically refer to the singular and may also include the plural. Generally speaking, the terms "comprising" and "including" only indicate the inclusion of explicitly identified steps and elements, which do not constitute an exclusive list, and the method or apparatus may also include other steps or elements.

[0021] Furthermore, this application uses specific terms to describe embodiments of the application. For example, "an embodiment," "one embodiment," and / or "some embodiments" refer to a particular feature, structure, or characteristic related to at least one embodiment of the application. Therefore, it should be emphasized and noted that "an embodiment," "one embodiment," or "an alternative embodiment" mentioned twice or more in different locations in this specification do not necessarily refer to the same embodiment. In addition, certain features, structures, or characteristics in one or more embodiments of the application can be appropriately combined.

[0022] Unless otherwise specifically stated, the relative arrangement, numerical expressions, and values ​​of the components and steps described in these embodiments do not limit the scope of this application. It should also be understood that, for ease of description, the dimensions of the parts shown in the drawings are not drawn to actual scale. Techniques, methods, and devices known to those skilled in the art may not be discussed in detail, but where appropriate, such techniques, methods, and devices should be considered part of the specification. In all examples shown and discussed herein, any specific values ​​should be interpreted as merely exemplary and not as limitations. Therefore, other examples of exemplary embodiments may have different values. It should be noted that similar reference numerals and letters in the following drawings denote similar items; therefore, once an item is defined in one drawing, it need not be further discussed in subsequent drawings.

[0023] Furthermore, although the terminology used in this application is selected from commonly known and used terms, some terms mentioned in this application's specification may have been chosen by the applicant according to his or her judgment, and their detailed meanings are explained in the relevant sections of the description herein. Moreover, this application is to be understood not only by the actual terms used, but also by the meaning implied by each term.

[0024] This application uses flowcharts to illustrate the operations performed by an apparatus or device according to embodiments of this application. It should be understood that the preceding or following operations are not necessarily performed precisely in sequence. Instead, various steps can be processed in reverse order or simultaneously. Furthermore, other operations may be added to these processes, or one or more steps may be removed from these processes.

[0025] See Figure 1 This application proposes a monitoring and management method for network devices, which can be executed by electronic devices, and the method includes the following steps:

[0026] S10: Obtain the execution information of the monitoring task to be executed. The execution information includes at least one first device information corresponding to a collection command, at least one second device information corresponding to an execution account, and at least one third device information of a network device.

[0027] In some embodiments, the first device information may include, for example, the device manufacturer, device category, device model, and software version number; the second device information may include, for example, the device category, device manufacturer, deployment region, account category, and account name; the third device information may include, for example, the software version number, device manufacturer, network device name, device category, device model, deployment region, and stacked device information. Network devices may include various types of devices such as routers, switches, firewalls, and load balancers.

[0028] S11: Match the target network device corresponding to each acquisition command from at least one network device based on the first device information, the third device information, and the network device matching strategy.

[0029] In some embodiments, the network device matching strategy can be that the device manufacturer, device category, and device model are the same, or it can be that the device manufacturer, device category, device model, and software version number are the same. The specific strategy can be set according to actual needs, mainly to ensure that the matched target network device supports the execution of the corresponding collection command. This application does not make specific limitations on this.

[0030] For example, assuming the network device matching policy is that the device manufacturer, device category, and device model are the same, taking any acquisition command as an example, the device manufacturer, device category, and device model of this acquisition command are: Manufacturer A, Switch, Manufacturer ACE5855. The third device information of at least one network device is shown in Table 1. Then, network device 1, which has the same device manufacturer, device category, and device model as this acquisition command, can be identified as its corresponding target network device. Similarly, for each acquisition command, the corresponding target network device can be determined based on the same network device matching policy.

[0031] Table 1

[0032]

[0033] S12: Match the target execution account corresponding to the target network device from at least one execution account based on the second device information, the third device information, and the account matching policy. The account matching policy can be divided into a first priority policy and a second priority policy, ranked from highest to lowest priority. If the first priority policy fails to match the corresponding target execution account, the second priority policy will then be used to match the corresponding target execution account. The first priority policy can be: the device category and device manufacturer are the same; the second priority policy can be: a general account with the same deployment area. Specific policies can be set according to actual needs, mainly to ensure that the matched target execution account can access the corresponding target network device. This application does not impose specific limitations on this.

[0034] For example, assuming the target network device is network device 1 in Table 1, and the second device information corresponding to at least one execution account is shown in Table 2, according to the first priority policy, if the device category and device manufacturer of account 1 are the same as those of network device 1, then account 1 can be identified as the target execution account corresponding to network device 1.

[0035] Alternatively, assuming the target network device is network device 2 in Table 1, and the second device information corresponding to at least one execution account is shown in Table 2, priority is given to determining that no target execution account with the same device category and manufacturer as network device 2 was matched according to the first priority policy. Furthermore, since account 2's device category is general and its deployment region is region B, indicating that account 2 is a general account deployed in region B, account 2 can be identified as the target execution account corresponding to network device 2 according to the second priority policy.

[0036] Table 2

[0037]

[0038] S13: Send a target acquisition command to the target network device based on the target execution account and obtain the execution result. In some embodiments, step S13 includes: establishing a remote connection with the target network device through the target execution account and sending a target acquisition command to the target network device. Further, the target network device executes the target acquisition command, collects and returns the relevant data indicated by the target acquisition command (i.e., the execution result). The relevant data may include operating status data such as port traffic, routing table, and CPU utilization, as well as configuration data such as device parameters and interface configuration. After relevant personnel view this data, it can provide full-process data support for real-time fault location, performance trend analysis, and compliance auditing of network devices.

[0039] In some embodiments, step S13 includes: first, executing a Ping command to determine the network connectivity of the target network device, supporting multiple connectivity checks (up to 3 times, with an interval of 5 minutes); after the connectivity check is passed, logging in via SSH using the target execution account and executing the target collection command to reduce invalid login attempts. Ping (PacketInternet Groper) is a network diagnostic tool based on the ICMP protocol, which verifies the reachability and network link quality of the target network device by sending echo request and receiving echo reply messages. SSH (Secure Shell) is a TCP-based encryption protocol that achieves secure remote login and command execution through key exchange and symmetric encryption.

[0040] In some embodiments, to prevent excessive load caused by repeated logins to the target network device within a short period, time control can be incorporated into task execution. Specifically, when executing step S13, the process may include: obtaining the latest remote login time of the target network device; when the time exceeds a time threshold (e.g., 30 minutes), sending the corresponding target collection command to the target network device based on the target execution account. Conversely, when the time is less than or equal to the time threshold, to prevent excessive load caused by repeated logins to the target network device within a short period, the monitoring task to be executed can be placed in a task queuing sequence; when the time exceeds the time threshold, step S13 can then be executed.

[0041] By executing steps S10 to S13, this embodiment of the application can adaptively match the target network device corresponding to each acquisition command and the target execution account corresponding to each target network device, and send the target acquisition command to the target network device based on the target execution account, thereby obtaining the execution result, which helps to reduce the execution error rate of acquisition commands.

[0042] In some embodiments, before performing step S10 above, the method further includes the following steps: outputting a creation page for a new acquisition command, the creation page including multiple first configuration items for obtaining the first device information and multiple second configuration items for obtaining information about the new acquisition command; when creation is detected to be complete, the new acquisition command is associated with and stored with the first device information. For example, the creation page for the new acquisition command can be as follows: Figure 2 As shown, the configuration items in areas 20 and 21 of the creation page are both second-level configuration items, mainly used to configure data collection command information, such as status, risk level, cancel pagination command, data collection command details, and command comments. The configuration items in area 22 of the creation page are all first-level configuration items, mainly used to configure primary device information such as device manufacturer, device category, device model, and software version number. When a target is detected... Figure 2 When the "Save" button is touched, the creation is confirmed to be complete. An approval request for the newly added acquisition command can be initiated. After approval, the newly added acquisition command will be associated with and stored with the first device information, and the newly added acquisition command will be added to the acquisition command repository list.

[0043] In some embodiments, when a target is detected Figure 2 When the "Save" button is touched, the system can analyze the content of the newly added data collection command and identify whether it is a preset high-risk command. If so, an alarm message is output; otherwise, the process continues to the next step. Preset high-risk commands may include, for example, rollback or reboot.

[0044] In some embodiments, before performing step S10 above, the method further includes the following steps: outputting a target parsing script creation page, the creation page including an associated acquisition command selection area and a parsing script configuration area, wherein the associated acquisition command selection area is used to select a target acquisition command, and the parsing script configuration area is used to obtain the target parsing script and the device information corresponding to the target parsing script. Further, when the completion of the operation is detected through the creation page, the association between the target acquisition command and the target parsing script is established and stored.

[0045] For example, the target parsing script creation page can be as follows: Figure 3 As shown, it includes an associated acquisition command selection area 30, through which target acquisition commands associated with the target parsing script can be selected. Figure 3 The remaining areas on the creation page can be considered the parsing script configuration area. This area is used to configure the specific content of the parsing script, including its name, version number, and device information such as the manufacturer and category of the devices on which the script can run. Using the same approach, you can customize the corresponding target parsing script for different target acquisition commands and different device manufacturers. This allows the customized target parsing script to meet the parsing scenarios of different manufacturers and acquisition commands, thereby improving the success rate of parsing and executing results through the target parsing script.

[0046] In some embodiments, after obtaining the execution result by performing step S13, the monitoring and management method may, as an optional approach, include the following steps: Step 1, obtaining the target parsing script pre-associated with the target acquisition command; Step 2, parsing the execution result according to the target parsing script, and storing the parsed data in a preset storage area. For example, a specific implementation of step 1 may include: obtaining the target parsing script corresponding to the target acquisition command based on the pre-established association between the target acquisition command and the target parsing script. The specific method for creating the association between the target acquisition command and the target parsing script can be referred to the above-mentioned... Figure 3 According to the description, Figure 3 The creation page shown completes the configuration of the target parsing script and the creation of its association with the corresponding target acquisition command. This method automates the monitoring task processing chain of acquisition-parsing-database entry, eliminating the need for manual coordination between each step and improving the efficiency of network device monitoring and management.

[0047] In some embodiments, the creation page for the target parsing script also includes an external data source configuration area for obtaining data source information from external data sources. The parsed data can then be transmitted to the external data source based on this information. This data source information can be, for example, configuration information for relational databases and message queues. This application embodiment supports associating the parsing script with multiple types of external data sources, including databases supported (OB-mysql / mysql / PG) and middleware supported (Kafka). The parsed content can be output to different external data sources, broadening the application scenarios for data collection. For example, the external data source configuration area... Figure 3 Region 31 in the middle.

[0048] In some embodiments, the monitoring and management method may further include: outputting a task execution result page based on the execution result and the parsed data. The task execution result page includes information corresponding to one or more of the following fields: collection execution result, parsed file name, parsing execution result, data storage result, execution device, and execution time. Here, the collection execution result can be understood as the execution result of the collection command; the parsed file name is the name of the file used to store the parsed data; and the data storage result represents the result of storing the parsed data in a preset storage area. If storage is completed, execution success is displayed; otherwise, execution failure is displayed, and the specific reason for failure can be displayed in a pop-up window. For example, the task execution result page is as follows: Figure 4 As shown.

[0049] In some embodiments, the monitoring and management method may further include: comparing the currently acquired parsed data with historical data, and distinguishing and displaying the differences, such as highlighting the difference rows. In this application embodiment, the task execution results support file difference highlighting and failure reason pop-up display, eliminating the need for technical personnel to view background logs. Even non-professional operations and maintenance personnel can quickly get started, reducing the reliance on script writing and log analysis capabilities in existing technologies.

[0050] See Figure 5 This application also proposes another method for monitoring and managing network devices, which includes the following steps:

[0051] S50: Outputs the task creation page for the monitoring task to be executed. This task creation page includes a data acquisition command selection area, an execution account selection area, and a network device selection area. The data acquisition command selection area is used to select at least one data acquisition command from the data acquisition command list; the execution account selection area is used to select at least one execution account from the execution account list; and the network device selection area is used to select at least one network device from the network device list.

[0052] In some embodiments, the network devices displayed in the above network device list are all network devices that meet the filtering criteria. These filtering criteria may include the network device's current status being "in use," or they may include the network device's current status being "in use" and not being a stacked backup device. The specific criteria can be set according to actual needs. The main purpose is to automatically exclude network devices that do not meet the filtering criteria from the network device list, reducing invalid data collection during subsequent task execution.

[0053] In some embodiments, the real-time status of each network device can be monitored in real time or periodically, and if any network device is detected as not meeting the filtering criteria, it will be removed from the network device list.

[0054] S51: Create a monitoring task to be executed based on at least one selected acquisition command, at least one execution account, and at least one network device.

[0055] In some embodiments, step S51 may include: checking whether the first device information corresponding to each of the at least one acquisition command matches any of the at least one network device; if not, outputting an alarm message to prompt the user that the currently selected acquisition command cannot be executed on any network device; if yes, creating a monitoring task to be executed based on the at least one selected acquisition command, at least one execution account, and at least one network device. Specifically, taking any acquisition command as an example, when the device category, device model, and device manufacturer of any acquisition command are the same as any network device, it can be determined that the any acquisition command matches the any network device. For example, if a user selects 100 network devices through the network device selection area and selects 10 acquisition commands through the acquisition command selection area, and the device manufacturers of all 100 network devices are manufacturer A, and the first device information corresponding to each of the 10 acquisition commands indicates that the device manufacturers corresponding to the 10 acquisition commands are all manufacturer B, then an alarm message will be output to prompt the user that the currently selected acquisition command cannot be executed on any of the selected network devices.

[0056] S52: Obtain the execution information of the monitoring task to be executed. The execution information includes at least one first device information corresponding to a collection command, at least one second device information corresponding to an execution account, and at least one third device information of a network device.

[0057] S53: Match the target network device corresponding to each acquisition command from at least one network device based on the first device information, the third device information and the network device matching strategy.

[0058] S54: Match the target execution account corresponding to the target network device from at least one execution account based on the second device information, the third device information, and the account matching policy.

[0059] S55: Send the target acquisition command to the target network device according to the target execution account, and obtain the execution result. The specific implementation methods of steps S52 to S55 can be found in the relevant descriptions of steps S10 to S13 in the above embodiments, and will not be repeated here.

[0060] Through the embodiments of this application, when users create a monitoring task to be executed and select at least one network device, at least one data acquisition command, and at least one execution account for the execution command, there is no need to manually match the execution command, network device, and execution account. This reduces the operational threshold for users, allowing them to complete the creation of the monitoring task without professional personnel. During subsequent task execution, steps S52-S55 can be executed to automatically match the target network device corresponding to each data acquisition command and the target execution account corresponding to each target network device, avoiding the risks associated with manually matching devices, commands, and accounts.

[0061] It's important to note that the users who create monitoring tasks and those who add new data collection commands and parsing scripts can be two different types of users. For example, the users adding data collection commands and parsing scripts can be the first type of user, possessing some professional knowledge, capable of configuring parsing scripts, and understanding the relationship between data collection commands and parsing scripts. The users executing monitoring tasks, on the other hand, can be the second type of user, lacking professional knowledge. This approach allows for the introduction of users with different roles at different stages of the entire monitoring management process, avoiding complete reliance on a single type of professional user and reducing labor costs.

[0062] In some embodiments, the monitoring management method proposed in this application further includes: after the monitoring task to be executed is created, adding a cancel pagination command to the monitoring task to be executed, and setting the execution order of the cancel pagination command to be executed first. In this case, sending the corresponding target acquisition command to the target network device according to the target execution account includes: sending the cancel pagination command and the corresponding target acquisition command to the target network device according to the target execution account, and instructing the target network device to execute the cancel pagination command first and then execute the target acquisition command. In this way, a "cancel pagination command" is automatically added to each monitoring task to be executed, and the "cancel pagination command" is automatically placed as the first command to be executed when the task is executed. This is beneficial for the corresponding target network device to present the content continuously and completely when executing the target acquisition command, without the need for manual pagination, thereby improving task execution efficiency and reducing the time for remote connection to the target network device.

[0063] Alternatively, in some embodiments, each acquisition command includes a command end echo symbol. After executing step S55, which sends the target acquisition command to the target network device based on the target execution account, if the aforementioned cancel pagination command is not added to the monitoring task to be executed, or if the aforementioned cancel pagination command has been added to the monitoring task to be executed but the target network device does not support the execution of the cancel pagination command, both scenarios may result in incomplete execution results returned by the target network device. To solve this problem, each time the execution result of the target network device is obtained, an integrity check can be performed on the current execution result. If the check passes, it indicates that the target acquisition command has finished executing and the current execution result is complete; if the check fails, it indicates that the target acquisition command has not finished executing and the current execution result is only partial data. The next batch of execution result acquisition instructions can be sent to the target network device, and so on, until the current execution result passes the integrity check. The integrity check method can be to detect whether the current execution result includes a command end echo symbol. If it does, the check passes; otherwise, it fails. In some embodiments, a concurrency control mechanism can be added when creating a monitoring task to be executed, such as limiting a single task to a maximum of 100 concurrent logins to avoid CPU overload. Specifically, this can be achieved by adding a corresponding prompt for the concurrency control mechanism to the network device selection area on the task creation page, such as displaying the message "A single task can log in to a maximum of 100 concurrent devices," allowing users to control the number of network devices selected. Alternatively, the system can detect whether the number of network devices selected by the user in the network device selection area exceeds 100; if so, an alarm message can be directly output.

[0064] It should be noted that the monitoring and management method proposed in this application involves the creation of monitoring tasks to be executed, the creation of target parsing scripts, the creation of new collection commands, the creation of execution accounts, etc. All of these creations can be subject to an approval mechanism; they can only be officially activated after approval, which helps reduce risk. Furthermore, the monitoring and management method proposed in this application can be executed by the same or different electronic devices, and this application does not specifically limit this. For example, the monitoring and management method can be executed by different electronic devices. This method is applied to a distributed management system, which may include electronic devices: a master control node, execution nodes, OSS (Object Storage Service) nodes, and network devices. The master control node is responsible for task management, the execution nodes are responsible for task execution, the OSS nodes are responsible for data storage, and the network devices are responsible for executing the collection commands sent by the execution nodes. The creation of the aforementioned monitoring tasks, the creation of target parsing scripts, the creation of new collection commands, the creation of execution accounts, etc., can all be executed by the master control node. The execution of tasks (such as steps S10 to S13 above) can be executed by the execution nodes. The OSS nodes can be the aforementioned preset storage areas used to store execution results and parsed data.

[0065] In some embodiments, the type of the monitoring task to be executed may include a temporary task or a scheduled task. In this case, the task creation page may also include a task type configuration (none) for configuring the type of monitoring task to be executed. When executing scheduled tasks and temporary tasks, the other execution processes are the same, except that after obtaining the execution result of a scheduled task, the execution result can be parsed according to the target parsing script, and the parsed data is stored in a preset storage area. When executing a temporary task, obtaining the execution result and storing it in the preset storage area is sufficient; there is no need to parse the execution result according to the target parsing script. This is because temporary tasks are usually executed only once, and users focus more on whether the corresponding target network device is operating normally based on the execution result, without needing to parse the execution result and perform more granular analysis based on the parsed data. In this case, when executing the step of obtaining the target parsing script pre-associated with the target acquisition command, the type of monitoring task to be executed can be identified. When the type is a scheduled task, the acquisition of the target parsing script pre-associated with the target acquisition command is triggered. The monitoring management process can be adaptively adjusted according to the task type, reducing unnecessary parsing work and improving the execution efficiency of temporary tasks.

[0066] In some embodiments, each parsing script is only invoked to parse the execution result when it is in an "enabled" state. Parsing scripts in an "enabled" state cannot be directly modified. If modification is required, the parsing script in an "enabled" state needs to be cloned. Modification is only supported on the cloned version. After the cloned version is modified, it can be officially enabled by going "live". The original parsing script in an "enabled" state will become offline. Multi-version control enables tracking of changes, efficient collaboration, and controllable risks.

[0067] Figure 6 This is a simplified block diagram of an electronic device 600 suitable for implementing embodiments of the present disclosure. For example, the Doppler frequency offset estimation method described above can be implemented by the electronic device 600. As shown, the electronic device 600 includes one or more processors 610, one or more memories 620 coupled to the processors 610, and one or more communication modules 640 coupled to the processors 610.

[0068] Communication module 640 is used for bidirectional communication. Communication module 640 has at least one antenna to facilitate communication. The communication interface can represent any interface necessary for communication with other network elements.

[0069] Processor 610 can be of any type suitable for a local technology network, and as a non-limiting example, can include one or more of the following: general-purpose computer, special-purpose computer, microprocessor, digital signal processor (DSP), and processor based on a multi-core processor architecture. Electronic device 600 can have multiple processors, such as application-specific integrated circuit (ASIC) chips, which are timely driven to a clock that synchronizes with the main processor.

[0070] Memory 620 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memories include, but are not limited to, read-only memory (ROM), electrically programmable read-only memory (EPROM), flash memory, hard disk, optical disc (CD), digital video disc (DVD), and other magnetic and / or optical storage. Examples of volatile memories include, but are not limited to, random access memory (RAM) and other volatile memories that do not persist during power-off periods.

[0071] Computer program 630 includes computer-executable instructions that are executed by a associated processor 610. Program 630 may be stored in ROM 624. Processor 610 may perform any appropriate actions and processes by loading program 630 into RAM 622.

[0072] The embodiments of this disclosure can be implemented via program 630, enabling electronic device 600 to execute reference... Figure 1 or Figure 5Any process disclosed herein. Embodiments of this disclosure may also be implemented in hardware or by a combination of software and hardware.

[0073] In some embodiments, program 630 may be tangibly contained in a computer-readable medium, which may be contained in an electronic device 600 (e.g., memory 620) or other storage device accessible to the electronic device 600. The electronic device 600 may load program 630 from the computer-readable medium into RAM 622 for execution. The computer-readable medium may include any type of tangible non-volatile memory, such as ROM, EPROM, flash memory, hard disk, CD, DVD, etc. Program 630 is stored on the computer-readable medium.

[0074] Generally, the various embodiments of this disclosure can be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. Some aspects may be implemented in hardware, while others may be implemented in firmware or software, which may be executed by a controller, microprocessor, or other computing device. Although various aspects of the embodiments of this disclosure are shown and described as block diagrams, flowcharts, or other graphical representations, it should be understood that, as non-limiting examples, the blocks, devices, systems, techniques, or methods described herein may be implemented in hardware, software, firmware, dedicated circuitry or logic, general-purpose hardware or controllers or other computing devices, or some combination thereof.

[0075] This disclosure also provides at least one computer program product tangibly stored on a non-transitory computer-readable storage medium. The computer program product includes computer-executable instructions, such as instructions included in a program module, which execute in a device on a target real or virtual processor to perform the aforementioned references. Figure 1 or Figure 5 The method described herein. Typically, a program module includes routines, programs, libraries, objects, classes, components, data structures, etc., that perform specific tasks or implement specific abstract data types. In various embodiments, the functionality of a program module can be combined or separated among program modules as needed. The machine-executable instructions used in the program module can execute on a local or distributed device. In a distributed device, the program module can reside on both local and remote storage media.

[0076] Program code used to perform the methods of this disclosure may be written in any combination of one or more programming languages. This program code may be provided to a processor or controller of a general-purpose computer, a special-purpose computer, or other programmable data processing device, such that when executed by the processor or controller, the functions / operations specified in the flowcharts and / or block diagrams are implemented. The program code may be executed entirely on a machine, partially on a machine, partially on a remote machine, partially on a remote machine, or entirely on a remote machine or server as a standalone software package.

[0077] In the context of this disclosure, computer program code or related data may be carried by any suitable carrier to enable a device, apparatus, or processor to perform the various processes and operations described above. Examples of carriers include signals, computer-readable media, etc.

[0078] Computer-readable media can be computer-readable signal media or computer-readable storage media. Computer-readable media can include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or apparatuses, or any suitable combination thereof. More specific examples of computer-readable storage media include electrical connections having one or more wires, portable computer floppy disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable optical disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0079] Furthermore, although the operations are described in a specific order, this should not be construed as requiring that these operations be performed in the specific order or sequence shown, or that all of the operations shown be performed to obtain the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, while several specific implementation details are included in the foregoing discussion, these details should not be construed as limiting the scope of this disclosure, but rather as descriptions of features specific to particular embodiments. Certain features described in the context of individual embodiments may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments.

[0080] Although this disclosure has been described in language specific to structural features and / or methodological behavior, it should be understood that this disclosure as defined in the appended claims is not necessarily limited to the specific features or behaviors described above. Rather, the specific features and actions described above are disclosed as exemplary forms for implementing the claims.

Claims

1. A method for monitoring and managing network devices, characterized in that, The method includes: Obtain the execution information of the monitoring task to be executed, wherein the execution information includes at least one first device information corresponding to a collection command, at least one second device information corresponding to an execution account, and at least one third device information of a network device; Based on the first device information, the third device information, and the network device matching strategy, the target network device corresponding to each acquisition command is matched from the at least one network device; Based on the second device information, the third device information, and the account matching strategy, the target execution account corresponding to the target network device is matched from the at least one execution account; The target acquisition command is sent to the target network device according to the target execution account, and the execution result is obtained.

2. The monitoring and management method as described in claim 1, characterized in that, After obtaining the execution result, the method further includes: Obtain the target parsing script that is pre-associated with the target acquisition command; The execution result is parsed according to the target parsing script, and the parsed data is stored in a preset storage area.

3. The monitoring and management method as described in claim 1, characterized in that, The method further includes: The system outputs a task creation page for the monitoring task to be executed. The task creation page includes a data collection command selection area, an execution account selection area, and a network device selection area. The data collection command selection area is used to select at least one data collection command from the data collection command list. The execution account selection area is used to select at least one execution account from the execution account list. The network device selection area is used to select at least one network device from the network device list. The monitoring task to be executed is created based on the selected at least one acquisition command, at least one execution account, and at least one network device.

4. The monitoring and management method as described in claim 3, characterized in that, The network devices displayed in the network device list are all network devices that meet the filtering criteria, including the network device's current status being "in use".

5. The monitoring and management method as described in claim 3, characterized in that, The method further includes: after the monitoring task to be executed is created, adding a cancel pagination command to the monitoring task to be executed, and setting the execution order of the cancel pagination command to be executed first, wherein: sending the corresponding target acquisition command to the target network device according to the target execution account includes: Based on the target execution account, the cancel pagination command and the corresponding target acquisition command are sent to the target network device, and the target network device is instructed to execute the cancel pagination command first and then execute the target acquisition command.

6. The monitoring and management method as described in claim 2, characterized in that, The method further includes: The creation page for the target parsing script is output. The creation page includes an associated acquisition command selection area and a parsing script configuration area. The associated acquisition command selection area is used to select the target acquisition command. The parsing script configuration area is used to obtain the target parsing script and the device information corresponding to the target parsing script. When the completion of the operation is detected through the creation page, the association between the target acquisition command and the target parsing script is established and stored.

7. The monitoring and management method as described in claim 6, characterized in that, The creation page also includes an external data source configuration area for obtaining data source information from external data sources. The method further includes: The parsed data is transmitted to the external data source based on the data source information.

8. The monitoring and management method as described in claim 2, characterized in that, The method further includes: Based on the execution result and the parsed data, a task execution result page is output. The task execution result page includes information corresponding to any one or more of the following fields: collection execution result, parsed file name, parsed execution result, data entry result, execution device, and execution time.

9. The monitoring and management method as described in claim 1, characterized in that, The step of sending the corresponding target acquisition command to the target network device based on the target execution account includes: Obtain the latest remote login time of the target network device; When the time exceeds the time threshold, the corresponding target acquisition command is sent to the target network device according to the target execution account.

10. An electronic device, characterized in that, include: At least one processor; as well as At least one memory storing instructions that, when executed individually or jointly by the at least one processor, cause the electronic device to perform the method as described in any one of claims 1-9.

Images