Abstract: Automated computer-implemented processes and systems are directed to troubleshooting a network used by an application in a data center. The processes and system execute a framework for automated network troubleshooting of an application. The framework performs automated fault localization by traversing a dependency graph that models the network from the observed performance problem, guided by the causality relationships, and for each edge of the graph, performs a test to determine problem causality, terminates at a set of well-defined criteria, and outputs at least one potential root cause for the application performance problem.

Abstract: Methods and systems described herein are directed resolving object dependencies in a data center. A trie data structure that represents network paths of objects utilized by a selected source object is constructed. The trie data structure comprises nodes linked by edges. Each node represents an edge identification (“ID”) of source objects and destination objects of one or more network paths of objects utilized by the selected source object in a user-defined time interval. The trie data structure is traversed to resolve the different versions of source objects and destination objects utilized by the selected source object in subintervals of the time interval. A graph of the objects and destination objects utilized by the selected source object in the subintervals is generated and used to identify source objects and destination objects utilized by the selected source object during a performance problem of the selected source object.

Abstract: Embodiments described herein generally involve identifying workloads in a networking environment based on a flow record from an observation point. In one embodiment, network data is received from one or more endpoints and used to determine a plurality of administrative domains. Each administrative domain comprises a distinct section of the networking environment within which every Internet Protocol (IP) address is unique. The network data may be used to generate observation point mapping information that maps each observation point to an administrative domain, lookup tables associated with each of the plurality of administrative domains that map IP addresses to administrative domains, and a workload identification table that maps combinations of IP addresses and administrative domains to workloads.

Abstract: Embodiments described herein generally involve identifying workloads in a networking environment based on a flow record from an observation point. In one embodiment, network data is received from one or more endpoints and used to determine a plurality of administrative domains. Each administrative domain comprises a distinct section of the networking environment within which every Internet Protocol (IP) address is unique. The network data may be used to generate observation point mapping information that maps each observation point to an administrative domain, lookup tables associated with each of the plurality of administrative domains that map IP addresses to administrative domains, and a workload identification table that maps combinations of IP addresses and administrative domains to workloads.