Data collection configuration file generation

A network monitoring system may receive a configuration request to generate a configuration file associated with collecting feature or debug data associated with a feature, hardware, or software associated with a network device. The network monitoring system may determine a command profile associated with the feature, hardware, or software that identifies a set of commands associated with obtaining the feature or debug data from the network device. The network monitoring system may determine respective parameters of one or more commands of the set of commands. The network monitoring system may determine, based on the respective parameters, respective arguments of the one or more commands. The network monitoring system may generate the configuration file based on the respective arguments and may perform an action associated with the configuration file to permit the configuration file to be used to collect the feature or debug data from the network device.

BACKGROUND

A network may include one or more network devices, such as one or more switches, one or more routers, one or more firewalls, and/or one or more gateways, among other examples. A performance of the network may be impacted by respective performances of the one or more network devices.

SUMMARY

In some implementations, a method includes receiving, by a device, a configuration request to generate a configuration file associated with collecting feature or debug data associated with a feature, hardware, or software associated with a network device; determining, by the device, a command profile associated with the feature, hardware, or software, wherein the command profile identifies a set of commands associated with obtaining the feature or debug data from the network device; determining, by the device and based on the configuration request, a collection scheme associated with collecting feature or debug data associated with the feature, hardware, or software, wherein the collection scheme is associated with an event that causes the feature or debug data to be collected from the network device; determining, by the device, respective parameters of one or more commands of the set of commands; determining, by the device and based on the respective parameters, respective arguments of the one or more commands; generating, by the device, the configuration file based on the respective arguments and the collection scheme; generating, based on the configuration file, one or more executable modules; and causing the feature or debug data to be collected from the network device based on executing the one or more executable modules.

In some implementations, a device includes one or more memories and one or more processors to: obtain a command profile associated with a feature, hardware, or software associated with a network, wherein the command profile identifies a set of commands associated with collecting, from a network device, feature or debug data associated with the feature, hardware, or software; determine, based on one or more characteristics of the feature, hardware, or software, respective parameters of one or more commands of the set of commands; determine, based on the respective parameters, respective arguments of the one or more commands; generate a configuration file based on the respective arguments and a collection scheme, wherein the collection scheme is associated with one or more events that cause the feature or debug data to be collected from the network device; determine, based on the respective arguments and the collection scheme, one or more tags associated with the feature, hardware, or software; and store, in a data structure, a mapping that associates the one or more tags and the configuration file.

In some implementations, a non-transitory computer-readable medium storing a set of instructions includes one or more instructions that, when executed by one or more processors of a device, cause the device to: obtain feature, hardware, or software information associated with a feature, hardware, or software of a network; determine, based on the feature, hardware, or software information, a command profile associated with collecting feature or debug data from a network device of the network, wherein the feature or debug data is associated with the feature, hardware, or software; determine, for a command of the command profile, a parameter of the command that corresponds to a characteristic of the feature, hardware, or software; determine, for the command and based on the parameter, an argument for collecting the feature or debug data from the network device; integrate the argument into a configuration file associated with the feature, hardware, or software to generate an updated configuration file; and deploy the updated configuration file to permit the updated configuration file to be used to collect the feature or debug data from the network device.

DETAILED DESCRIPTION

A network may include one or more network devices, where each network device is associated with one or more features. A feature of a network device may include, for example, a type of the network device, a type of service provided by the network device, a type of network operation performed by the network device, a type of network metric associated with a performance of the network device, and/or a sequence of events following a failure scenario, among other examples. In a typical case, monitoring the respective features of the one or more network devices requires manual development of scripts on each of the network devices. This can be a resource intensive, time-consuming procedure that is susceptible to human error and efforts spent on a script is specific to a particular feature and does not extend to other features. Further, due to changing characteristics of the one or more network devices and/or features of the one or more network devices that are to be monitored, generating and/or updating scripts for individual network devices and/or for every feature is often impracticable.

Some implementations described herein provide a network monitoring system that generates a configuration file associated with collecting feature or debug data associated with a feature, hardware, or software associated with a network device. The network monitoring system may receive a request to generate the configuration file and determine, based on the request, a command profile that identifies a set of commands associated with obtaining the feature or debug data from the network device. The network monitoring system may generate the configuration file based on determining parameters and arguments of the set of commands. Accordingly, the network monitoring system may deploy the configuration file to permit the configuration file to be used to collect the feature or debug data from the network device.

In this way, the network monitoring system may automatically generate a configuration file (e.g., from a set of commands) to facilitate collection of feature or debug data associated with a feature, hardware, or software of a network device. The network monitoring system may generate a configuration file that is specific to the network device; without manual development by a network administrator. Accordingly, the network monitoring system eliminates an amount of time and computing resources (e.g., processing resources, memory resources, and/or power resources, among other examples) that would otherwise be required in order to manually develop individual scripts for monitoring respective features of a network device.

FIGS.1A-1Bare diagrams of an example100associated with generating a data collection configuration file. As shown inFIGS.1A-1B, example100includes a network monitoring system and one or more network devices (shown inFIG.1Bas network devices1through N, N≥1). A network device, of the one or more network devices, may include a switch, a router, and/or a gateway, among other examples. As shown inFIG.1B, the network device may be included in a network (e.g., with one or more other network devices), such as a cellular network, a local area network (LAN), a core network, an access network, a wide area network (WAN) such as the Internet, a cloud network, and/or the like.

Turning toFIG.1Aand reference number110, the network monitoring system may receive (e.g., from another device, such as a user device) a request to generate a configuration file associated with a feature, hardware, or software of a network device and/or a network that is monitored by the network monitoring system. The feature, hardware, or software may be a particular type of the network device, a particular type of service provided by the network device (e.g., an authentication service, a security service, a routing service, and/or a load balancing service, among other examples), a particular type of network operation performed by the network device, a particular type of network metric associated with a performance of the network device, and/or a sequence of events following a failure scenario, among other examples. For example, as shown in the Feature, Hardware, or Software Information table inFIG.1A, the network monitoring system may receive a request to generate a configuration file associated with a particular data type (shown as Type_1) associated with a particular type of network device (shown as Dev_1), a request to generate a configuration file associated with a particular type of network metric (shown as Metric_2), and so on. The configuration file (e.g., after the configuration file is generated by the network monitoring system, as described herein) may be used by the network monitoring system and/or a network device to collect feature or debug data (e.g. shown as Data A and/or Data B in the Feature, Hardware, or Software Information table) associated with the feature, hardware, or software indicated by the request.

In some implementations, a user may interact with a user interface of the network monitoring system and/or another device (e.g., a user device that communicates with the network monitoring system) to generate user input that is received by the network monitoring system. The user input may include a description of the feature, hardware, or software. For example, the description may indicate one or more characteristics of the feature, hardware, or software (e.g., one or more keywords associated with the feature, hardware, or software; guidance on how to interpret and/or use the feature or debug data; and/or the like). In some implementations, the description includes a document that describes the network device, a guide (e.g., a manual, a debugging guide, and/or a troubleshooting guide) associated with the network device, and/or specification information concerning the network device, among other examples. Additionally, or alternatively, the user input may include one or more tags associated with the feature, hardware, or software (e.g., that may be used by the network monitoring system to determine how to process and collect the feature or debug data based on a run time hardware/software state of the network device or feature, hardware, or software; to classify and/or store the configuration file; and/or the like, as described herein). The user input may be included as part of the request that is received by the network monitoring system, or may be received by the network monitoring system in association with the request (e.g., within a particular time window of receiving the request).

As further shown inFIG.1A, and by reference number120, the network monitoring system may determine a command profile associated with the feature, hardware, or software. In some implementations, the network monitoring system may process and/or analyze the request and/or the user input to determine the one or more characteristics of the feature, hardware, or software, and may determine the command profile based on the one or more characteristics. For example, as shown inFIG.1A, the network monitoring system may search, based on the one or more characteristics, a command data structure (e.g., a storage device, such as a hard drive, a database, a network-attached storage (NAS), and/or the like, that is configured to store command profiles) for a command profile that is associated with the feature, hardware, or software. The command profile may identify a set of commands associated with obtaining the feature or debug data associated with the feature, hardware, or software of the network device and/or the state of the network and/or the network device or when isolating a state of events following a major event or failure in the network or on the network device (e.g., from the network device). For example, when the one or more characteristics are associated with a route supported by the network device, the network monitoring system may process the one or more characteristics to identify a command profile that includes a set of commands that are associated with collecting data concerning a route.

In some implementations, the network monitoring system may determine one or more parameters (also referred to as one or more variables) of a command, of the set of commands. In some implementations, the one or more parameters may correspond to the one or more characteristics of the feature, hardware, or software (e.g., a parameter, of the one or more parameters, may respectively correspond to a characteristic of the one or more characteristics). A parameter of the command may indicate a type of the network device, a location (e.g., a physical location and/or a virtual location) of the network device, an interface of the network device, a condition of the network device, a performance characteristic of the network device, run time values associated with other commands, and/or types of packet or network traffic, among other examples. In some implementations, the parameter may indicate a relationship between the parameter and one or more other parameters of the command and/or one or more other parameters of a different command of the set of commands. For example, the parameter may indicate a next hop of a route of the network device that may be related to a parameter associated with the interface of the network device.

In some implementations, the network monitoring system may determine a collection scheme associated with collecting the feature or debug data associated with the feature, hardware, or software (e.g., from the network device). The collection scheme may indicate an event for collecting the feature or debug data. For example, the collection scheme may indicate a schedule to collect the feature or debug data (e.g., the feature or debug data is to be collected every 2 seconds, every 10 seconds, every 30 seconds, or every 5 minutes, among other examples), a particular time to collect the feature or debug data (e.g., the feature or debug data is to be collected at 14:00 on the day the request is received), and/or a triggering condition to collect the feature or debug data (e.g., the feature or debug data is to be collected when the network device operates under a particular condition, such as the network device experiencing a failure, being overloaded, having certain performance characteristics, and/or the like), among other examples.

In some implementations, the user input (e.g., as described above) may include a description of the event. For example, the description may indicate the schedule to collect the feature or debug data, the particular time to collect the feature or debug data, and/or the triggering condition to collect the feature or debug data. In another example, as shown in the Feature, Hardware, or Software Information table inFIG.1A, the user input may indicate that first feature or debug data (shown as Data A) is to be collected according to a schedule (shown as Schedule_1), or that second feature or debug data (shown as Data B) is to be collected according to a triggering condition (shown as T_Event_2). As described above, the user input may be included as part of the request that is received by the network monitoring system, or may be received by the network monitoring system in association with the request (e.g., within a particular time window of receiving the request). Accordingly, the network monitoring system may process and/or analyze the request and/or the user input to determine the collection scheme.

As further shown inFIG.1A, and by reference number130, the network monitoring system may generate, or prompt a user to input, one or more arguments for a command of the set of commands. An argument may define one or more inputs required to facilitate collecting the feature or debug data associated with the feature, hardware, or software. In some implementations, the network monitoring system may generate the one or more arguments for the command based on the one or more parameters of the command. For example, the network monitoring system may generate (e.g., using a configuration module of the network monitoring system, as shown inFIG.1A) an argument for collecting data concerning a performance metric of the network device that includes at least one parameter, of the one or more parameters, associated with the performance metric.

As further shown inFIG.1A, and by reference number140, the network monitoring system may generate (e.g., using a configuration file generator module of the network monitoring system, as shown inFIG.1A) a configuration file (e.g., that may be used by the network monitoring system to collect feature or debug data associated with the feature, hardware, or software, as described herein). The configuration file may include the respective arguments of the one or more commands that comprise the set of commands. For example, the network monitoring system may generate a configuration file (e.g., an initial, “blank” configuration file) and integrate each of the respective arguments of the one or more commands into the configuration file to generate an updated configuration file. As another example, the network monitoring system may identify an existing configuration file (e.g., based on searching, using an identifier associated with the feature, hardware, or software, a data structure that is configured to store configuration files) and generate a copy of the configuration file. Accordingly, the network monitoring system may integrate each of the respective arguments of the one or more commands in the copied configuration file. In some implementations, the network monitoring system may generate the configuration file to include and/or indicate the collection scheme.

In some implementations, the network monitoring system may store the configuration file (e.g., after causing the configuration file to include the respective arguments of the one or more commands that comprise the set of commands and/or the collection scheme) in the data structure configured to store configuration files. For example, the network monitoring system may process and/or analyze the request, the user input, and/or the configuration file (e.g., that includes the respective arguments of the one or more commands that comprise the set of commands and/or the collection scheme), among other examples, to identify the one or more tags (e.g., one or more classification terms) associated with the feature, hardware, or software. The network monitoring system may store the configuration file in association with an identifier of the feature, hardware, or software (e.g., a name or description of the feature, hardware, or software) and/or the one or more tags in the data structure (e.g., as an entry in the data structure that includes the identifier of the feature, hardware, or software, the one or more tags, and the configuration file as different elements of the entry).

Turning toFIG.1Band reference number150, the network monitoring system may receive a collection request associated with the feature, hardware, or software of the network device and/or the network (e.g., after the network monitoring system has generated the configuration file associated with the feature, hardware, or software). In some implementations, the network monitoring system may receive the collection request from another device (e.g., a user device that communicates with the network monitoring system). The collection request may include a request to collect the feature or debug data associated with the feature, hardware, or software. In some implementations, the collection request may include a description of the feature, hardware, or software and/or one or more tags associated with the feature, hardware, or software, among other examples.

As further shown inFIG.1B, and by reference number160, the network monitoring system may obtain the configuration file based on the collection request. For example, the network monitoring system may process and/or analyze the collection request to identify the description of the feature, hardware, or software and/or the one or more tags associated with the feature, hardware, or software. Accordingly, the network monitoring system may search, based on the description of the feature, hardware, or software and/or the one or more tags associated with the feature, hardware, or software, the data structure that stores the configuration files to obtain the configuration file.

Turning toFIG.1Cand reference number170, the network monitoring system may process the configuration file. For example, the network monitoring system may process the configuration file to generate one or more executable modules that may be run to collect the feature or debug data associated with the feature, hardware, or software.

In some implementations, when processing the configuration file, the network monitoring system may identify the set of commands that are included in the configuration file. The network monitoring system may identify for each command, of the set of commands, one or more arguments and may determine whether each of the one or more arguments is a required argument or optional argument. In some implementations, network monitoring system may identify for each command, of the set of commands, one or more parameters and may determine whether any of the one or more parameters is a multi-use parameter used by other commands of the set of commands and/or whether any of the one or more parameters includes a dynamic value (e.g., a regular expression for indicating a matching condition). In some implementations, the network monitoring system may identify the collection scheme included in the configuration file and determine one or more events for collecting the feature or debug data (e.g., a schedule to collect the feature or debug data, a number of times to collect the feature or debug data, and/or the like).

Accordingly, the network monitoring system may generate the one or more executable modules according to the required and/or optional arguments, the multi-use parameters, the parameters with dynamic values, and/or the one or more events, among other examples. In some implementations, the network monitoring system may generate the one or more executable modules based on the collection request, such that only executable modules that are relevant to the collection request are generated. In this way, the network monitoring system may prevent computing resources (e.g., processing resources, memory resources, power resources, and/or the like) of the network monitoring system from being used to generate unnecessary executable modules.

As further shown inFIG.1Cand by reference number180, the network monitoring system may perform one or more actions to collect the feature or debug data associated with the feature, hardware, or software (e.g., based on the configuration file and/or the one or more executable modules). In some implementations, performing the one or more actions includes executing the one or more executable modules to cause the network monitoring system to collect the feature or debug data. For example, the network monitoring system may execute the one or more executable modules to cause the set of commands that are included in the configuration file to be run according to the collection scheme included in the configuration file. In this way, the network monitoring system may collect the feature or debug data associated with the feature, hardware, or software.

In some implementations, the network monitoring system may send the configuration file and/or the one or more executable modules to the network device associated with the feature, hardware, or software, to allow the network device to collect the feature or debug data associated with the feature, hardware, or software (e.g., by executing the one or more executable modules in a similar manner as that described above). Accordingly, the network device may send the feature or debug data to the network monitoring system (e.g., to allow the network monitoring system to collect the feature or debug data associated with the feature, hardware, or software).

In some implementations, the network monitoring system may store the feature or debug data in a data structure of the network monitoring system (e.g., as a file that includes the feature or debug data and additional identifying information, such as a timestamp indicating when the feature or debug data was collected). In some implementations, the network monitoring system, or another device, may access the data structure to obtain and process and/or analyze the feature or debug data.

As indicated above,FIGS.1A-1Care provided as an example. Other examples may differ from what is described with regard toFIGS.1A-1C. The number and arrangement of devices shown inFIGS.1A-1Care provided as an example. In practice, there may be additional devices, fewer devices, different devices, or differently arranged devices than those shown inFIGS.1A-1C. Furthermore, two or more devices shown inFIGS.1A-1Cmay be implemented within a single device, or a single device shown inFIGS.1A-1Cmay be implemented as multiple, distributed devices. Additionally, or alternatively, a set of devices (e.g., one or more devices) shown inFIGS.1A-1Cmay perform one or more functions described as being performed by another set of devices shown inFIGS.1A-1C.

FIG.2is a diagram of an example environment200in which systems and/or methods described herein may be implemented. As shown inFIG.2, environment200may include a network monitoring system201, which may include one or more elements of and/or may execute within a cloud computing system202. The cloud computing system202may include one or more elements203-213, as described in more detail below. As further shown inFIG.2, environment200may include a network220, and/or a network device230. Devices and/or elements of environment200may interconnect via wired connections and/or wireless connections.

The cloud computing system202includes computing hardware203, a resource management component204, a host operating system (OS)205, and/or one or more virtual computing systems206. The resource management component204may perform virtualization (e.g., abstraction) of computing hardware203to create the one or more virtual computing systems206. Using virtualization, the resource management component204enables a single computing device (e.g., a computer, a server, and/or the like) to operate like multiple computing devices, such as by creating multiple isolated virtual computing systems206from computing hardware203of the single computing device. In this way, computing hardware203can operate more efficiently, with lower power consumption, higher reliability, higher availability, higher utilization, greater flexibility, and lower cost than using separate computing devices.

Computing hardware203includes hardware and corresponding resources from one or more computing devices. For example, computing hardware203may include hardware from a single computing device (e.g., a single server) or from multiple computing devices (e.g., multiple servers), such as multiple computing devices in one or more data centers. As shown, computing hardware203may include one or more processors207, one or more memories208, one or more storage components209, and/or one or more networking components210. Examples of a processor, a memory, a storage component, and a networking component (e.g., a communication component) are described elsewhere herein.

The resource management component204includes a virtualization application (e.g., executing on hardware, such as computing hardware203) capable of virtualizing computing hardware203to start, stop, and/or manage one or more virtual computing systems206. For example, the resource management component204may include a hypervisor (e.g., a bare-metal or Type 1 hypervisor, a hosted or Type 2 hypervisor, and/or the like) or a virtual machine monitor, such as when the virtual computing systems206are virtual machines211. Additionally, or alternatively, the resource management component204may include a container manager, such as when the virtual computing systems206are containers212. In some implementations, the resource management component204executes within and/or in coordination with a host operating system205.

A virtual computing system206includes a virtual environment that enables cloud-based execution of operations and/or processes described herein using computing hardware203. As shown, a virtual computing system206may include a virtual machine211, a container212, a hybrid environment213that includes a virtual machine and a container, and/or the like. A virtual computing system206may execute one or more applications using a file system that includes binary files, software libraries, and/or other resources required to execute applications on a guest operating system (e.g., within the virtual computing system206) or the host operating system205.

Although the network monitoring system201may include one or more elements203-213of the cloud computing system202, may execute within the cloud computing system202, and/or may be hosted within the cloud computing system202, in some implementations, the network monitoring system201may not be cloud-based (e.g., may be implemented outside of a cloud computing system) or may be partially cloud-based. For example, the network monitoring system201may include one or more devices that are not part of the cloud computing system202, such as device300ofFIG.3or device400ofFIG.4, which may include a standalone server or another type of computing device. The network monitoring system201may perform one or more operations and/or processes described in more detail elsewhere herein.

Network220includes one or more wired and/or wireless networks. For example, network220may include a cellular network, a public land mobile network (PLMN), a local area network (LAN), a wide area network (WAN), a private network, the Internet, and/or the like, and/or a combination of these or other types of networks. The network220enables communication among the devices of environment200.

The network device230includes one or more devices capable of receiving, processing, storing, routing, and/or providing traffic (e.g., a packet, other information or metadata, and/or the like) in a manner described herein. For example, the network device230may include a router, such as a label switching router (LSR), a label edge router (LER), an ingress router, an egress router, a provider router (e.g., a provider edge router, a provider core router, and/or the like), a virtual router, and/or the like. Additionally, or alternatively, the network device230may include a gateway, a switch, a firewall, a hub, a bridge, a reverse proxy, a server (e.g., a proxy server, a cloud server, a data center server, and/or the like), a load balancer, and/or a similar device. In some implementations, the network device230may be a physical device implemented within a housing, such as a chassis. In some implementations, the network device230may be a virtual device implemented by one or more computing devices of a cloud computing environment or a data center. In some implementations, the network device230may be associated with a feature, hardware, or software and the network device230and/or the network monitoring system201may collect feature or debug data associated with the feature, hardware, or software based on a configuration file generated by the network monitoring system201.

FIG.3is a diagram of example components of a device300, which may correspond to network monitoring system201, computing hardware203, and/or network device230, among other examples. In some implementations, network monitoring system201, computing hardware203, and/or network device230, among other examples, may include one or more devices300and/or one or more components of device300. As shown inFIG.3, device300may include a bus310, a processor320, a memory330, a storage component340, an input component350, an output component360, and a communication component370.

Bus310includes a component that enables wired and/or wireless communication among the components of device300. Processor320includes a central processing unit, a graphics processing unit, a microprocessor, a controller, a microcontroller, a digital signal processor, a field-programmable gate array, an application-specific integrated circuit, and/or another type of processing component. Processor320is implemented in hardware, firmware, or a combination of hardware and software. In some implementations, processor320includes one or more processors capable of being programmed to perform a function. Memory330includes a random access memory, a read only memory, and/or another type of memory (e.g., a flash memory, a magnetic memory, and/or an optical memory).

Storage component340stores information and/or software related to the operation of device300. For example, storage component340may include a hard disk drive, a magnetic disk drive, an optical disk drive, a solid state disk drive, a compact disc, a digital versatile disc, and/or another type of non-transitory computer-readable medium. Input component350enables device300to receive input, such as user input and/or sensed inputs. For example, input component350may include a touch screen, a keyboard, a keypad, a mouse, a button, a microphone, a switch, a sensor, a global positioning system component, an accelerometer, a gyroscope, an actuator, and/or the like. Output component360enables device300to provide output, such as via a display, a speaker, and/or one or more light-emitting diodes. Communication component370enables device300to communicate with other devices, such as via a wired connection and/or a wireless connection. For example, communication component370may include a receiver, a transmitter, a transceiver, a modem, a network interface card, an antenna, and/or the like.

Device300may perform one or more processes described herein. For example, a non-transitory computer-readable medium (e.g., memory330and/or storage component340) may store a set of instructions (e.g., one or more instructions, code, software code, program code, and/or the like) for execution by processor320. Processor320may execute the set of instructions to perform one or more processes described herein. In some implementations, execution of the set of instructions, by one or more processors320, causes the one or more processors320and/or the device300to perform one or more processes described herein. In some implementations, hardwired circuitry may be used instead of or in combination with the instructions to perform one or more processes described herein. Thus, implementations described herein are not limited to any specific combination of hardware circuitry and software.

FIG.4is a diagram of example components of a device400. Device400may correspond to network monitoring system201, computing hardware203, and/or network device230, among other examples. In some implementations, network monitoring system201, computing hardware203, and/or network device230, among other examples, may include one or more devices400and/or one or more components of device400. As shown inFIG.4, device400may include one or more input components410-1through410-B (B≥1) (hereinafter referred to collectively as input components410, and individually as input component410), a switching component420, one or more output components430-1through430-C(C≥1) (hereinafter referred to collectively as output components430, and individually as output component430), and a controller440.

Input component410may be one or more points of attachment for physical links and may be one or more points of entry for incoming traffic, such as packets. Input component410may process incoming traffic, such as by performing data link layer encapsulation or decapsulation. In some implementations, input component410may transmit and/or receive packets. In some implementations, input component410may include an input line card that includes one or more packet processing components (e.g., in the form of integrated circuits), such as one or more interface cards (IFCs), packet forwarding components, line card controller components, input ports, processors, memories, and/or input queues. In some implementations, device400may include one or more input components410.

Switching component420may interconnect input components410with output components430. In some implementations, switching component420may be implemented via one or more crossbars, via busses, and/or with shared memories. The shared memories may act as temporary buffers to store packets from input components410before the packets are eventually scheduled for delivery to output components430. In some implementations, switching component420may enable input components410, output components430, and/or controller440to communicate with one another.

Output component430may store packets and may schedule packets for transmission on output physical links. Output component430may support data link layer encapsulation or decapsulation, and/or a variety of higher-level protocols. In some implementations, output component430may transmit packets and/or receive packets. In some implementations, output component430may include an output line card that includes one or more packet processing components (e.g., in the form of integrated circuits), such as one or more IFCs, packet forwarding components, line card controller components, output ports, processors, memories, and/or output queues. In some implementations, device400may include one or more output components430. In some implementations, input component410and output component430may be implemented by the same set of components (e.g., and input/output component may be a combination of input component410and output component430).

Controller440includes a processor in the form of, for example, a CPU, a GPU, an APU, a microprocessor, a microcontroller, a DSP, an FPGA, an ASIC, and/or another type of processor. The processor is implemented in hardware, firmware, or a combination of hardware and software. In some implementations, controller440may include one or more processors that can be programmed to perform a function.

In some implementations, controller440may include a RAM, a ROM, and/or another type of dynamic or static storage device (e.g., a flash memory, a magnetic memory, an optical memory, etc.) that stores information and/or instructions for use by controller440.

In some implementations, controller440may communicate with other devices, networks, and/or systems connected to device400to exchange information regarding network topology. Controller440may create routing tables based on the network topology information, may create forwarding tables based on the routing tables, and may forward the forwarding tables to input components410and/or output components430. Input components410and/or output components430may use the forwarding tables to perform route lookups for incoming and/or outgoing packets.

FIG.5is a flowchart of an example process500associated with data collection configuration file generation. In some implementations, one or more process blocks ofFIG.5may be performed by a device (e.g., network monitoring system201). In some implementations, one or more process blocks ofFIG.5may be performed by another device or a group of devices separate from or including the device, such as a network device (e.g., network device230). Additionally, or alternatively, one or more process blocks ofFIG.5may be performed by one or more components of device300, such as processor320, memory330, storage component340, input component350, output component360, and/or communication component370; one or more components of device400, such as input component410, switching component420, output component430, and/or controller440; and/or the like.

As shown inFIG.5, process500may include receiving a configuration request to generate a configuration file associated with collecting feature or debug data associated with a feature, hardware, or software associated with a network device (block510). For example, the device may receive a configuration request to generate a configuration file associated with collecting feature or debug data associated with a feature, hardware, or software associated with a network device, as described above.

As further shown inFIG.5, process500may include determining a command profile associated with the feature, hardware, or software, wherein the command profile identifies a set of commands associated with obtaining the feature or debug data from the network device (block520). For example, the device may determine a command profile associated with the feature, hardware, or software, as described above. In some implementations, the command profile identifies a set of commands associated with obtaining the feature or debug data from the network device.

As further shown inFIG.5, process500may include determining, based on the configuration request, a collection scheme associated with collecting feature or debug data associated with the feature, hardware, or software, wherein the collection scheme is associated with an event that causes the feature or debug data to be collected from the network device (block530). For example, the device may determine, based on the configuration request, a collection scheme associated with collecting feature or debug data associated with the feature, hardware, or software. In some implementations, the collection scheme is associated with an event that causes the feature or debug data to be collected from the network device.

As further shown inFIG.5, process500may include determining respective parameters of one or more commands of the set of commands (block540). For example, the device may determine respective parameters of one or more commands of the set of commands, as described above.

As further shown inFIG.5, process500may include determining, based on the respective parameters, respective arguments of the one or more commands (block550). For example, the device may determine, based on the respective parameters, respective arguments of the one or more commands, as described above.

As further shown inFIG.5, process500may include generating the configuration file based on the respective arguments and the collection scheme (block560). For example, the device may generate the configuration file based on the respective arguments and the collection scheme, as described above.

As further shown inFIG.5, process500may include generating, based on the configuration file, one or more executable modules (block570). For example, the device may generate, based on the configuration file, one or more executable modules, as described above.

As further shown inFIG.5, process500may include causing the feature or debug data to be collected from the network device based on executing the one or more executable modules (block580). For example, the device may cause the feature or debug data to be collected from the network device based on executing the one or more executable modules, as described above.

In a first implementation, the configuration request is received in association with a user input that includes a description of the feature, hardware, or software, wherein the command profile is determined based on an analysis of the description of the feature, hardware, or software.

In a second implementation, alone or in combination with the first implementation, determining the command profile comprises identifying, from the configuration request, one or more characteristics of the feature, hardware, or software that are described in the configuration request, wherein the one or more characteristics correspond to the respective parameters, and determining, based on the one or more characteristics, the set of commands.

In a third implementation, alone or in combination with one or more of the first and second implementations, the configuration request is received in association with a user input that includes a description of the event, and the collection scheme is determined based on an analysis of the description of the event.

In a fourth implementation, alone or in combination with one or more of the first through third implementations, the event comprises a scheduled event that is associated with a schedule for collecting the feature or debug data.

In a fifth implementation, alone or in combination with one or more of the first through fourth implementations, the event is associated with the network device operating under a particular condition.

In a sixth implementation, alone or in combination with one or more of the first through fifth implementations, process500includes, prior to performing the action, determining, based on the configuration request, one or more tags associated with the feature, hardware, or software, and storing the configuration file in association with an identifier of the feature, hardware, or software and the one or more tags.

In a seventh implementation, alone or in combination with one or more of the first through sixth implementations, generating the one or more executable modules comprises identifying a plurality of commands included in the configuration file; identifying, based on the plurality of commands, executable information that includes at least one of: one or more required arguments, one or more optional arguments, one or more multi-use parameters, one or more dynamic value parameters, or one or more events for collecting the feature or debug data; and generating the one or more executable modules based on the executable information.

FIG.6is a flowchart of an example process600associated with data collection configuration file generation. In some implementations, one or more process blocks ofFIG.6may be performed by a device (e.g., network monitoring system201). In some implementations, one or more process blocks ofFIG.6may be performed by another device or a group of devices separate from or including the device, such as a network device (e.g., network device230). Additionally, or alternatively, one or more process blocks ofFIG.6may be performed by one or more components of device300, such as processor320, memory330, storage component340, input component350, output component360, and/or communication component370; one or more components of device400, such as input component410, switching component420, output component430, and/or controller440; and/or the like.

As shown inFIG.6, process600may include obtaining a command profile associated with a feature, hardware, or software of a network; wherein the command profile identifies a set of commands associated with collecting, from a network device, feature or debug data associated with the feature, hardware, or software (block610). For example, the device may obtain a command profile associated with a feature, hardware, or software of a network, as described above. In some implementations, the command profile identifies a set of commands associated with collecting, from a network device, feature or debug data associated with the feature, hardware, or software.

As further shown inFIG.6, process600may include determining, based on one or more characteristics of the feature, hardware, or software, respective parameters of one or more commands of the set of commands (block620). For example, the device may determine, based on one or more characteristics of the feature, hardware, or software, respective parameters of one or more commands of the set of commands, as described above.

As further shown inFIG.6, process600may include determining, based on the respective parameters, respective arguments of the one or more commands (block630). For example, the device may determine, based on the respective parameters, respective arguments of the one or more commands, as described above.

As further shown inFIG.6, process600may include generating a configuration file based on the respective arguments and a collection scheme, wherein the collection scheme is associated with one or more events that cause the feature or debug data to be collected from the network device (block640). For example, the device may generate a configuration file based on the respective arguments and a collection scheme, as described above. In some implementations, the collection scheme is associated with one or more events that cause the feature or debug data to be collected from the network device.

As further shown inFIG.6, process600may include determining, based on the respective arguments and the collection scheme, one or more tags associated with the feature, hardware, or software (block650). For example, the device may determine, based on the respective arguments and the collection scheme, one or more tags associated with the feature, hardware, or software, as described above.

As further shown inFIG.6, process600may include storing, in a data structure, a mapping that associates the one or more tags and the configuration file (block660). For example, the device may store, in a data structure, a mapping that associates the one or more tags and the configuration file, as described above.

In a first implementation, the feature, hardware, or software comprises at least one of: a particular type of network device, a particular type of service provided by the network device, a particular type of network operation performed by the network device, a particular type of network metric associated with a performance of the network device; or a set of data required for troubleshooting an error, an event, or a symptom.

In a second implementation, alone or in combination with the first implementation, the command profile is obtained in association with a user input that identifies the one or more characteristics.

In a third implementation, alone or in combination with one or more of the first and second implementations, at least one of the one or more events comprises a scheduled event that is associated with a schedule for collecting the feature or debug data from the network device, or an unscheduled event that is associated with the network device operating under a particular condition.

In a fourth implementation, alone or in combination with one or more of the first through third implementations, the one or more tags associated with the feature, hardware, or software are determined based on a user input provided in association with the command profile.

In a fifth implementation, alone or in combination with one or more of the first through fourth implementations, process600includes receiving a collection request, determining that the collection request is associated with the feature, hardware, or software, obtaining the configuration file from the data structure, generating, based on the collection request and the configuration file, one or more executable modules, and collecting the feature or debug data from the network device or another network device of the network based on the one or more executable modules.

AlthoughFIG.6shows example blocks of process600, in some implementations, process600may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted inFIG.6. Additionally, or alternatively, two or more of the blocks of process600may be performed in parallel.

FIG.7is a flowchart of an example process700associated with data collection configuration file generation. In some implementations, one or more process blocks ofFIG.7may be performed by a device (e.g., network monitoring system201). In some implementations, one or more process blocks ofFIG.6may be performed by another device or a group of devices separate from or including the device, such as a network device (e.g., network device230). Additionally, or alternatively, one or more process blocks ofFIG.7may be performed by one or more components of device300, such as processor320, memory330, storage component340, input component350, output component360, and/or communication component370; one or more components of device400, such as input component410, switching component420, output component430, and/or controller440; and/or the like.

As shown inFIG.7, process700may include obtaining feature, hardware, or software information associated with a feature, hardware, or software of a network (block710). For example, the device may obtain feature, hardware, or software information associated with a feature, hardware, or software of a network, as described above.

As further shown inFIG.7, process700may include determining, based on the feature, hardware, or software information, a command profile associated with collecting feature or debug data from a network device of the network, wherein the feature or debug data is associated with the feature, hardware, or software (block720). For example, the device may determine, based on the feature, hardware, or software information, a command profile associated with collecting feature or debug data from a network device of the network, as described above. In some implementations, the feature or debug data is associated with the feature, hardware, or software.

As further shown inFIG.7, process700may include determining, for a command of the command profile, a parameter of the command that corresponds to a characteristic of the feature, hardware, or software (block730). For example, the device may determine, for a command of the command profile, a parameter of the command that corresponds to a characteristic of the feature, hardware, or software, as described above.

As further shown inFIG.7, process700may include determining, for the command and based on the parameter, an argument for collecting the feature or debug data from the network device (block740). For example, the device may determine, for the command and based on the parameter, an argument for collecting the feature or debug data from the network device, as described above.

As further shown inFIG.7, process700may include integrating the argument into a configuration file associated with the feature, hardware, or software to generate an updated configuration file (block750). For example, the device may integrate the argument into a configuration file associated with the feature, hardware, or software to generate an updated configuration file, as described above.

As further shown inFIG.7, process700may include deploying the updated configuration file to permit the updated configuration file to be used to collect the feature or debug data from the network device (block760). For example, the device may deploy the updated configuration file to permit the configuration file to be used to collect the feature or debug data from the network device, as described above.

In a first implementation, the feature, hardware, or software information comprises at least one of a document that describes the network device, a guide associated with interacting with the network device, or a user input that includes a description of the feature, hardware, or software.

In a second implementation, alone or in combination with the first implementation, process700includes, prior to integrating the argument into the configuration file, determining, based on the argument and the feature, hardware, or software information, a collection scheme for collecting the feature or debug data, wherein the collection scheme includes at least one of a schedule for collecting the feature or debug data, or an event associated with triggering collection of the feature or debug data.

In a third implementation, alone or in combination with one or more of the first and second implementations, integrating the argument into the configuration file includes identifying the configuration file based on the configuration file being mapped to an identifier of the feature, hardware, or software in a data structure, generating a copy of the configuration file, and integrating the argument into the copy of the configuration file, wherein the updated configuration file corresponds to the copy of the configuration file.

In a fourth implementation, alone or in combination with one or more of the first through third implementations, causing the device to deploy the updated configuration file includes generating one or more executable modules based on the configuration file; and executing the one or more executable modules, or sending the configuration file to the network device to allow the network device to execute the one or more executable modules.

In a fifth implementation, alone or in combination with one or more of the first through fourth implementations, deploying the updated configuration file includes storing the updated configuration file, in association with an identifier of the feature, hardware, or software, in a data structure, or transmitting, to the network device, the updated configuration file to cause the network device to use the updated configuration file to collect the feature or debug data.

AlthoughFIG.7shows example blocks of process700, in some implementations, process700may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted inFIG.7. Additionally, or alternatively, two or more of the blocks of process700may be performed in parallel.