Patent classifications
H04L41/5019
End-to-end service level metric approximation
Described are examples for providing service level monitoring for a network hosting applications as a cloud service. A service level monitoring device may receive end-to-end measurements of service usage collected at user devices for a plurality of applications hosted as a cloud services. The service level monitoring device may determine degraded applications of the plurality of applications based on anomalies in the measurements. The service level monitoring device may determine a service level metric based on an aggregation of the degraded applications. In some examples, the service level monitoring device may detect a network outage affecting the service.
End-to-end service level metric approximation
Described are examples for providing service level monitoring for a network hosting applications as a cloud service. A service level monitoring device may receive end-to-end measurements of service usage collected at user devices for a plurality of applications hosted as a cloud services. The service level monitoring device may determine degraded applications of the plurality of applications based on anomalies in the measurements. The service level monitoring device may determine a service level metric based on an aggregation of the degraded applications. In some examples, the service level monitoring device may detect a network outage affecting the service.
Managing input/output priority based on response time
Aspects include selecting a channel group from a plurality of channel groups for an I/O operation. Each channel group in the plurality of channel groups is associated with a priority level and includes one or more channels. The selecting is based on a priority level assigned to the I/O operation and the priority level associated with the selected channel group. The I/O operation is driven on a selected channel in the selected channel group. A response time for the I/O operation is recorded and an average I/O response time for the selected channel is calculated. It is determined whether the plurality of channel groups should be reformed based at least in part on the calculated average response time for the selected channel. The plurality of channel groups are reformed in response to determining that the plurality of channel groups should be reformed.
Service chain based network slicing
A processor may identify one or more sources. The processor may identify a respective requirement of each of the one or more sources. The processor may determine if a respective requirement is different than another respective requirement. The processor may locate each of the one or more sources in a respective slice on a different container available in a server of a network.
METHODS AND SYSTEMS RELATING TO IMPACT MANAGEMENT OF INFORMATION TECHNOLOGY SYSTEMS
Described are various embodiments of methods and systems relating to impact management of IT systems, including a server-based IT management system comprising a network server having a service function object store that stores a plurality of service function objects, each service function object being a digital representation of a service function and comprising one or more service attributes and one or more service function links for linking each service function object to at least one other service function object; and a network communications interface for receiving information indicative of an operating state for each service function; wherein the operability of any given service function is determined automatically upon the reduction of operating state of any one or more other service functions based on direct and indirect linkages between the given service function and the other service functions and the respective service-loss impact values associated with each said direct and indirect linkages.
AUTOMATIC CONFIGURATION OF SD-WAN LINK RULES ON A PER APPLICATION BASIS USING REAL-TIME NETWORK CONDITIONS
new link requests are received and an application making the request is identified. SD-WAN parameters are retrieved from an application control database. A first parameter is a JLP loss requirement for the application, and can be either low JLP, medium JLP, or high JLP SLA level. A second parameter a downstream/upstream bandwidth capability requirement. Links are determined from the pool of available links that meet the JLP requirement. One of the links is selected for the new link request, from the pool of available links that meet the JLP requirement, based on a downstream and an upstream bandwidth capability. The best link is automatically activated for the new link request
GARBAGE COLLECTION OF REDUNDANT PARTITIONS
A method, system, and computer program product for garbage collection of redundant partitions in distributed data management systems are provided. The method stores data across a set of nodes with the data being stored using one or more partitions and the data and the one or more partitions are replicated across the set of nodes. A first partition is determined to be stale at a first node of the set of nodes. The first partition is marked for deletion locally at the first node. A set of deletion votes are determined for the first partition with each node being associated with a deletion vote. The method determines a deletion decision for the first partition on the first node based on the set of deletion votes.
ENTERPRISE PORT ASSIGNMENT
Methods, systems, and apparatuses may determine a connection topology for a service and send an alert in which the alert includes a service connection topology that includes a plurality of port assignments for each equipment of the connection topology.
ENTERPRISE PORT ASSIGNMENT
Methods, systems, and apparatuses may determine a connection topology for a service and send an alert in which the alert includes a service connection topology that includes a plurality of port assignments for each equipment of the connection topology.
NETWORK FLOW ATTRIBUTION IN SERVICE MESH ENVIRONMENTS
In one embodiment, a monitoring engine obtains mesh flow data for traffic flows between nodes in a service mesh. The monitoring engine associates the mesh flow data with network traffic between an endpoint device and an edge of the service mesh. The monitoring engine identifies, based on the mesh flow data, a particular container workload associated with the traffic flows. The monitoring engine provides an indication that the particular container workload is associated with the network traffic between the endpoint device and the edge of the service mesh.