An embodiment detects, by a packet detection module on a first worker node, a first synchronization message (SYN) issued from a client pod on the first worker node and directed to a first server pod on a second worker node and generates a first SYN record in a connection table stored on the first worker node. The embodiment detects, by the packet detection module, a second SYN issued from the client pod and directed to the first server pod and generates a server pod status record stored in memory on the first worker node indicative of the first server pod having an unhealthy status. The embodiment identifies an available server pod having a healthy status and generates a detour routing rule in a routing table on the first worker node indicative of a revised connection in which the identified available server pod replaces the first server pod.

A gateway performs silent authentication refreshes with an identity management platform in order to extend the expiration of a cookie provided to an endpoint that accesses network applications through the gateway.

Described herein are systems, methods, and software to manage workflow monitoring between a client and one or more web servers. In one implementation, a client may initiate a workflow and maintain timing information associated with HTTP requests to one or more web servers as part of the workflow. The client further obtains, from the one or more web servers, log information for operations initiated from the HTTP requests to the one or more web servers and generates a timing diagram display based on the timing information and the log information.

Described herein are systems, methods, and software to manage workflow monitoring between a client and one or more web servers. In one implementation, a client may initiate a workflow and maintain timing information associated with HTTP requests to one or more web servers as part of the workflow. The client further obtains, from the one or more web servers, log information for operations initiated from the HTTP requests to the one or more web servers and generates a timing diagram display based on the timing information and the log information.

Techniques for monitoring network connectivity using machine learning are provided. A plurality of historical connectivity records is received, and a first machine learning model type, of a plurality of machine learning model types, is selected based on the plurality of historical connectivity records. A machine learning model, of the first machine learning model type, is trained based on the plurality of historical connectivity records, where the machine learning model learns to generate forecasted connectivity records based on the training.

Techniques for monitoring network connectivity using machine learning are provided. A plurality of historical connectivity records is received, and a first machine learning model type, of a plurality of machine learning model types, is selected based on the plurality of historical connectivity records. A machine learning model, of the first machine learning model type, is trained based on the plurality of historical connectivity records, where the machine learning model learns to generate forecasted connectivity records based on the training.

A plurality of connection patterns is determined based on connectivity data collected by a plurality of agents. Each agent of the plurality of agents is installed on a respective compute node of a plurality of compute nodes. The connectivity data collected by each agent of the plurality of agents includes node-local connectivity data indicating node-local connections for the respective compute node on which the agent is installed. The node-local connections include communications with at least one application entity hosted by the respective compute node. A graph representation that is organized with respect to the at least one application entity hosted by each of the plurality of compute nodes is generated based on the plurality of connection patterns.

A plurality of connection patterns is determined based on connectivity data collected by a plurality of agents. Each agent of the plurality of agents is installed on a respective compute node of a plurality of compute nodes. The connectivity data collected by each agent of the plurality of agents includes node-local connectivity data indicating node-local connections for the respective compute node on which the agent is installed. The node-local connections include communications with at least one application entity hosted by the respective compute node. A graph representation that is organized with respect to the at least one application entity hosted by each of the plurality of compute nodes is generated based on the plurality of connection patterns.

A component tracking system includes a plurality of devices that each include a device component monitoring subsystem that monitors for and records the addition and/or removal of device components to/from that device. A device component manager system that is coupled to each of the plurality of devices identifies, via a recording by a first device monitoring subsystem in a first device included in the plurality of devices, the removal of a first device component from the first device. The device component manager system then determines, via a recording by a second device component monitoring subsystem in a second device included in the plurality of devices, that the first device component has been added to the second device within a time period and, in response, the device component manager device prevents a removed first device component alarm.

A component tracking system includes a plurality of devices that each include a device component monitoring subsystem that monitors for and records the addition and/or removal of device components to/from that device. A device component manager system that is coupled to each of the plurality of devices identifies, via a recording by a first device monitoring subsystem in a first device included in the plurality of devices, the removal of a first device component from the first device. The device component manager system then determines, via a recording by a second device component monitoring subsystem in a second device included in the plurality of devices, that the first device component has been added to the second device within a time period and, in response, the device component manager device prevents a removed first device component alarm.