Abstract: Network traffic external to a service mesh can be analyzed and displayed. For example, a system can receive first telemetry data associated with a service mesh and can receive second telemetry data associated with an external virtual application network. The system may then determine at least one connection point between the service mesh and the external virtual application network based on a comparison of the first telemetry data and the second telemetry data. The connection point can include a flow of network traffic between the service mesh and the external virtual application network. Additionally, the system can generate a graphical user interface, which can include a first section associated with the service mesh, a second section associated with the external virtual application network, and a visual indicator of the connection point between service mesh and external virtual application network.

Abstract: Implementations for dynamically visualizing service mesh topologies with event-based messaging are described. An example method may include obtaining, by a processing device, topology data characterizing a service mesh comprising a plurality of nodes; obtaining tracing data associated with events processed by a message broker servicing the plurality of nodes; identifying, based on the tracing data, a message flow between at least two nodes of the plurality of nodes of the service mesh, wherein the at least two nodes represent a source and a destination of a message associated with the events; and providing, via a graphical user interface (GUI), visualization of the service mesh with the message flow.

Abstract: Processing logic may obtain a configuration file of each of one or more proxies. Processing logic may parse the configuration file of each of the one or more proxies to determine one or more connections for each of the one or more proxies as defined by the configuration file. Each connection may support incoming or outgoing communication for each of the one or more proxies. Processing logic may generate a map that includes the one or more connections for each of the one or more proxies.

Abstract: Processing logic may obtain a configuration file of each of one or more proxies. Processing logic may parse the configuration file of each of the one or more proxies to determine one or more connections for each of the one or more proxies as defined by the configuration file. Each connection may support incoming or outgoing communication for each of the one or more proxies. Processing logic may generate a map that includes the one or more connections for each of the one or more proxies.

Abstract: Implementations for dynamically visualizing microservice mesh topologies are described. An example method may include receiving a first request for a first type of visualization of a microservice mesh comprising nodes, obtaining first information regarding the nodes of the microservice mesh corresponding to the first type of visualization, providing, in a graphical user interface (GUI), the first type of visualization of the microservice mesh using the first information, receiving a second request for a second type of visualization of the microservice mesh, obtaining second information regarding the nodes of the microservice mesh corresponding to the second type of visualization, the second type of visualization different form the first type of visualization, and providing, via an update to the GUI, the second type of visualization of the microservice mesh using the second information.

Abstract: Implementations for dynamically visualizing microservice mesh topologies are described. An example method may include receiving a first request for a first type of visualization of a microservice mesh comprising nodes, obtaining first information regarding the nodes of the microservice mesh corresponding to the first type of visualization, providing, in a graphical user interface (GUI), the first type of visualization of the microservice mesh using the first information, receiving a second request for a second type of visualization of the microservice mesh, obtaining second information regarding the nodes of the microservice mesh corresponding to the second type of visualization, the second type of visualization different form the first type of visualization, and providing, via an update to the GUI, the second type of visualization of the microservice mesh using the second information.

Abstract: Implementations for dynamically visualizing microservices mesh topologies are described. An example method may include receiving a first request for a first type of visualization of a microservices mesh comprising nodes, obtaining first information regarding the nodes of the microservices mesh corresponding to the first type of visualization, providing, in a graphical user interface (GUI), the first type of visualization of the microservices mesh using the first information, receiving a second request for a second type of visualization of the microservices mesh, obtaining second information regarding the nodes of the microservices mesh corresponding to the second type of visualization, the second type of visualization different form the first type of visualization, and providing, via an update to the GUI, the second type of visualization of the microservices mesh using the second information.

Abstract: Systems and methods for enabling additional metrics in a monitoring system to diagnose problems are disclosed. An example method may include collecting first metric data at a first collection frequency, determining whether the first metric data exceeds a first boundary defined by a first metric rule, responsive to determining that the first metric data exceeds the first boundary, collecting second metric data at a second collection frequency and collecting the first metric data at a third collection frequency, the second metric data and the third collection frequency defined by the first metric rule, determining whether the first metric data no longer exceeds the first boundary, and responsive to determining the first metric data no longer exceeds the first boundary, terminating collection of the second metric data while continuing to collect the first metric data at the first collection frequency.

Abstract: Systems and methods for enabling additional metrics in a monitoring system to diagnose problems are disclosed. An example method may include collecting first metric data at a first collection frequency, determining whether the first metric data exceeds a first boundary defined by a first metric rule, responsive to determining that the first metric data exceeds the first boundary, collecting second metric data at a second collection frequency and collecting the first metric data at a third collection frequency, the second metric data and the third collection frequency defined by the first metric rule, determining whether the first metric data no longer exceeds the first boundary, and responsive to determining the first metric data no longer exceeds the first boundary, terminating collection of the second metric data while continuing to collect the first metric data at the first collection frequency.

Abstract: Systems and methods are disclosed for managing information technology resources. Management capabilities available for a particular IT resource are defined via at least one management interface. The management interface includes port types that specify attributes and operations available in a Web service to manage the IT resource. The port types are mapped to descriptors in a ModelMBeanInfo interface than can be used with an MBean that corresponds to the Web service.