The described technology is generally directed towards a message broker resource monitoring service that obtains message broker resource parameter data of a resource, based on communications of a message broker. Based on the resource parameter data and historical data, message broker resource monitoring service obtains a predicted message delivery time value, which can be in association with confidence. If the predicted message delivery time value satisfies a resource deletion criterion, e.g., the predicted message delivery time value, with sufficient confidence, exceeds a threshold value, the message broker resource monitoring service triggers an action to delete the resource. To obtain the predicted value, a regression such as symmetric conformal quantile regression can be applied to the parameter data, e.g., to obtain a predicted message delivery time/latency value.

A faulty node is identified in a cloud native environment by retrieving a topology that describes a relationship between a plurality of nodes in a network, retrieving a list of alarms in the network, determining a child node in the network located at the bottom of the topology that has a first alarm based on the alarm list, determining a parent node of the child node located above the child node and below or on an apex node of the network that has a second alarm based on the topology, determining whether the parent node is an apex node in the network based on the topology, and based on a determination that the parent node is the apex node in the network, identify the parent node as the faulty node.

Distributed network address discovery in non-uniform node networks can be performed. Regarding a client request for a service, network management component (NMC) can determine a network address space associated with a client based on a network identifier associated with the client or a node identifier. NMC can determine a group of candidate nodes (CN group) from a group of nodes based on network addresses associated with nodes of the node group and the network address space. NMC can determine a group of available candidate nodes (ACN group), from the CN group, available and able to process the request and perform the service based on operational statuses associated with the nodes of the CN group or services associated with those nodes. From the ACN group, NMC can determine a ranked list of network addresses associated with available nodes that can process the request based on defined service performance criteria.

A network management apparatus according to an embodiment includes: a storage device configured to store information indicating a correspondence relationship between information objects related to a logical layer, information objects related to a physical layer in a network configuration, and information objects related to a facility layer which are objects in which the information objects related to the physical layer are housed; an acquisition unit configured to acquire an information object related to an occurrence path of a failure in the logical layer of the network configuration, from the storage device; and a search unit configured to search for, among the information objects related to the facility layer stored in the storage device, an information object related to the facility layer and the physical layer associated with the information object related to the occurrence path of the failure acquired from the acquisition unit, as a candidate for a facility that causes the failure.

A wireless communication network manages a wireless access node. The wireless access node wirelessly exchanges user data with wireless User Equipment (UEs) and exchanges the user data with one or more network elements. The wireless access node generates status indicators that characterize wireless access node operation during the user data exchanges. An Element Management System (EMS) determines EMS load based on EMS operation and transfers load data that indicates the EMS load for delivery to the wireless access node. The wireless access node receives the load data transferred by the EMS. The wireless access node identifies individual priorities for individual ones of the status indicators. The wireless access node determines individual reporting times for the individual ones of the status indicators based on the load data and the individual priorities. The wireless access node transfers the individual ones of the status indicators to the EMS per the individual reporting times.

A method for determining a fault root cause includes obtaining first fault information, where the first fault information includes M alarms, and M is an integer greater than or equal to 1; determining, from N pieces of known fault information based on the M alarms, at least one piece of known fault information that matches the first fault information, where each of the N pieces of known fault information includes a plurality of alarms; and determining, based on a fault root cause of the at least one piece of known fault information, information related to a root cause of the first fault information. The root cause of the first fault information is determined by using the known fault information that matches the first fault information.

A network management system (NMS) is described that provides a granular troubleshooting workflow at an application session level using an application session-specific topology from a client device to a cloud-based application server. During an application session of a cloud-based application, a client device running the application exchanges data through one or more access point (AP) devices, one or more switches at a wired network edge, and one or more network nodes, e.g., switches, routers, and/or gateway devices, to reach a cloud-based application server. For a particular application session, the NMS generates a topology based on network data received from a subset of network devices, e.g., client devices, AP devices, switches, routers, and/or gateways, that were involved in the particular application session over a duration of the particular application session. In this way, the NMS enables backward-looking troubleshooting of the particular application session.

Embodiments of the present disclosure provide for predicted operational support data object selection and provision functionality. Predicted operational support data object(s) may be selected and provided to address particular malfunction classification(s) affecting networked device(s) on a dynamic home communications network. Some embodiments include identifying, in real-time, a device identification data set associated with a networked device set communicable with the dynamic home communications network; retrieving a device activity data set associated with the networked device set; applying a malfunction classification data model to the device activity data set to select the predicted operational support data object from the device operational support management repository; and outputting the predicted operational support data object to a client device in communication with the dynamic home communications network. The malfunction classification data model is trained based on training data, external aggregated activity data, and malfunction device history data.

Rapid failure detection and recovery in wireless communication networks is needed in order to meet, among other things, carrier class Ethernet transport channel standards. Thus, resilient wireless packet communications is provided using a hardware-assisted rapid transport channel failure detection algorithm and a Gigabit Ethernet data access card with an engine configured accordingly. In networks with various topologies, this is provided in combination with their existing protocols, such as rapid spanning tree and link aggregation protocols, respectively.

Embodiments of a device and method are disclosed. In an embodiment, a method for network device troubleshooting involves at a cloud server, connecting to a neighboring network device of a faulty network device, where the neighboring network device and the faulty network device are located within a network deployed at a customer site, and where the neighboring network device communicates with the faulty network device according to a short-range wireless communications protocol, and at the cloud server, performing a network device troubleshooting operation on the faulty network device using the neighboring network device as a proxy.