Abstract: Illustrative embodiments provide an efficient, resilient high-availability (“HA”) router architecture. In illustrative embodiments, metric and event data is made resilient to node failover by replication. The same data is stored on the database of each router. Instead of pushing metrics directly from all of each node's software to each node's database, replication is instead handled by the database loader application subscribing to queues on both nodes. In some embodiments, records are written in the queues to topics that have a certain time to live (TTL), so the loader on one node has the duration of the TTL to read from the other node's queue in order to achieve replication.

Abstract: Illustrative embodiments provide an efficient, resilient high-availability (“HA”) router architecture. In illustrative embodiments, metric and event data is made resilient to node failover by replication. The same data is stored on the database of each router. Instead of pushing metrics directly from all of each node's software to each node's database, replication is instead handled by the database loader application subscribing to queues on both nodes. In some embodiments, records are written in the queues to topics that have a certain time to live (TTL), so the loader on one node has the duration of the TTL to read from the other node's queue in order to achieve replication.

Abstract: Techniques are disclosed for the identification of applications from communication sessions of network traffic between client devices and the generation of application-specific metrics for network traffic associated with the applications. In one example, a router obtains metrics for a plurality of packets. The router determines a session of a plurality of sessions associated with each packet. For each determined session, the router generates metrics for the session from the metrics of the packets associated with the session and determines an application of a plurality of applications associated with the session. For each determined application, the router generates metrics for the application from the metrics of the sessions associated with the application and transmits, to a device, the metrics for the application. In some examples, the router generates the metrics for each application on a per-client, per-next-hop, or per-traffic class basis.

Abstract: Techniques are described for monitoring application performance in a computer network. For example, a network management system (NMS) includes a memory storing path data received from a plurality of network devices, the path data reported by each network device of the plurality of network devices for one or more logical paths of a physical interface from the given network device over a wide area network (WAN). Additionally, the NMS may include processing circuitry in communication with the memory and configured to: determine, based on the path data, one or more application health assessments for one or more applications, wherein the one or more application health assessments are associated with one or more application time periods for a site, and in response to determining at least one failure state, output a notification including identification of a root cause of the at least one failure state.

Abstract: Techniques are disclosed for the identification of applications from communication sessions of network traffic between client devices and the generation of application-specific metrics for network traffic associated with the applications. In one example, a router obtains metrics for a plurality of packets. The router determines a session of a plurality of sessions associated with each packet. For each determined session, the router generates metrics for the session from the metrics of the packets associated with the session and determines an application of a plurality of applications associated with the session. For each determined application, the router generates metrics for the application from the metrics of the sessions associated with the application and transmits, to a device, the metrics for the application. In some examples, the router generates the metrics for each application on a per-client, per-next-hop, or per-traffic class basis.

Abstract: Techniques are described for monitoring application performance in a computer network. For example, a network management system (NMS) includes a memory storing path data received from a plurality of network devices, the path data reported by each network device of the plurality of network devices for one or more logical paths of a physical interface from the given network device over a wide area network (WAN). Additionally, the NMS may include processing circuitry in communication with the memory and configured to: determine, based on the path data, one or more application health assessments for one or more applications, wherein the one or more application health assessments are associated with one or more application time periods for a site, and in response to determining at least one failure state, output a notification including identification of a root cause of the at least one failure state.

Abstract: Techniques are disclosed for the identification of applications from communication sessions of network traffic between client devices and the generation of application-specific metrics for network traffic associated with the applications. In one example, a router obtains metrics for a plurality of packets. The router determines a session of a plurality of sessions associated with each packet. For each determined session, the router generates metrics for the session from the metrics of the packets associated with the session and determines an application of a plurality of applications associated with the session. For each determined application, the router generates metrics for the application from the metrics of the sessions associated with the application and transmits, to a device, the metrics for the application. In some examples, the router generates the metrics for each application on a per-client, per-next-hop, or per-traffic class basis.

Abstract: Illustrative embodiments provide an efficient, resilient high-availability (“HA”) router architecture. In illustrative embodiments, metric and event data is made resilient to node failover by replication. The same data is stored on the database of each router. Instead of pushing metrics directly from all of each node's software to each node's database, replication is instead handled by the database loader application subscribing to queues on both nodes. In some embodiments, records are written in the queues to topics that have a certain time to live (TTL), so the loader on one node has the duration of the TTL to read from the other node's queue in order to achieve replication.