Red Hat, Inc.

Hewlett-packard Development Company, L.p.

Jay Shaughnessy

John Joseph Mazzitelli

Travis Scott Tripp

William Brothers

Joshua D Hawkins

Heiko Wolfgang Rupp

Philip Andrew Flocken

Noreen K Lee

Phil A Flocken

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.

Dynamically visualizing service mesh topologies with event-based messaging

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.

Mapping proxy connectivity

A request for a traffic topology of a service mesh including traffic between multiple services that utilize multiple communication protocols is received. In response to receiving the request, metric data associated with the traffic between the multiple services is acquired. The traffic topology of the traffic between the multiple services is generated using the metric data, the traffic topology illustrating corresponding traffic for one or more of the multiple communication protocols and one or more metrics associated with the corresponding traffic.

Customizable visualization of a traffic topology of a service mesh

A method includes appending contextual information and identification information of the computing inventory data to time series data of computing metrics data to generate a relationship indication. The method further includes providing the relationship indication to be displayed via a graphical user interface of a client device in response to a request, wherein the relationship indication comprises a plurality of links between the computing inventory data and the computing metrics data.

Linking computing metrics data and computing inventory data

A method includes, in response to receiving a request for a graphical visualization of a microservice mesh comprising one or more nodes, obtaining information associated with services operating at the one or more nodes and connections between the one or more nodes. The method further includes determining, in view of the information, one or more types of requests associated with each of the services. The method further includes generating the graphical visualization of the microservice mesh. The graphical visualization includes a first vertex corresponding to a particular service and a second vertex corresponding to a type of a request received by the service. The first vertex and second vertex are connected by an edge that corresponds to the request.

Dynamic visualization of requests traveling through a microservice mesh

Mechanisms for identifying a component cluster among a plurality of components in a distributed computing environment are disclosed. Configuration information that corresponds to the plurality of components is accessed. The configuration information includes inter-component communication information. The inter-component communication information between the plurality of components is matched to determine a plurality of pairs of components that communicate with one another. Relationships between the components in the pairs of components are determined. A data structure that identifies the component cluster of the pairs of components and the relationships between the components in the pairs of components is generated.

Identifying a component cluster

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.

Dynamically visualizing microservices mesh topologies

A method includes receiving, at a first server device, computing inventory data from one or more application components of a computing device, and receiving, at the first service device, computing metrics data from the one or more application components of the computing device. The computing inventory data is received from a second server device. The method further includes determining, by a processing device, a hierarchical relationship indication at least partially in view of the computing metrics data and the computing inventory data, and further providing the hierarchical relationship indication to a client device in response to a request.

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.

Various system and method embodiments are disclosed that include using a first node to receive messages including error information from a plurality of client computers via a computer network. Recommendations for resolving errors associated with the error information are made available to the client computers via the computer network.

Systems and methods for controlling error reporting and resolution

Customer support personnel can access via a vendor's portal an automated support vendor website to view the status of a fault incident that is being handled by the vendor's automated support system. In an illustrated embodiment, the customer can actually alter the status of the fault incident while it is being handled on the vendor's site.

Growing community of inventors

Mt. Laurel, NJ, United States of America

Jay Shaughnessy