SUSE Observability walk-through
SUSE Observability
Last updated
SUSE Observability
SUSE Observability
Last updated
Hi! So, you've integrated your Kubernetes or OpenShift clusters and you are ready to get started.
After setting up your , you can go open the Main menu to explore your resources. You can for example start with the Services.
This brings you to the service overview which shows all services running in your clusters. If you click any of the other items underneath Kubernetes you will go to the overview page of that type of resource. It will show all resources of that type in all clusters and all namespaces at first.
At the right top, you have the option to filter your selection to a certain cluster and/ or namespace to see the resources for which you are responsible.
At the bottom left, you find two inputs.
The time-range selector. This selects the time range for all metrics, logs and events you see throughout the product.
The topology-time selector. This is used to travel back to a certain moment in time to see the exact state of your systems as observed at that moment in time.
You can for example filter on a certain namespace, in this case, I filter the services down to 'sock-shop' which is a demo application using different microservices written in different programming languages and using different ways of communication to act as a nice example for troubleshooting an issue. If you now click on Topology you will see the topology of the currently selected components (in this case the services of the sock-shop).
In the topology, you see all resources, in this case services.
If you click a component (in this case a service) it shows you the details of a service including the most important metrics, in the case of a service, for example, the latency, throughput and error rate. Next to the most important metrics the health of the component is shown and expanded if there is anything going wrong.
If you click a relation you will see the detail of the relation including all components part of it. In the case of a service map you will see all components involved in the service-to-service communication. If you want to open a component to see all details of that resource (e.g. the details of this service a certain service) you can click on the 'Open Component' button from a selected component (which you then see in the Right Hand Side panel) or you can open the component by clicking on the name of the component in the overview page tab.
After opening a Kubernetes resource you will get a Highlight perspective showing you all the highlights of that component.
The component meta-data
The actions available on the component, in the case of a service, it gives you the ability to show the Status and/ or Configuration information. If you want to see the logs you can open the pods via the related resources which give you access to the Logs.
Related resources. This section shows all related resources to this resource in this case 2 other services to which it communicates and 1 pod which backs this services.
The monitors sections shows you all monitors applied to this Resource including their state a the selected topology-time.
The metrics section shows you all the important metrics for this service. The metrics include the selected telemetry-time interval.
A health time-line for a service shows the health of this resource over time.
A event time-line showing all events happening on this service over time.
Let's now explore a triggered monitor by clicking on the 'HTTP - 5xx error ratio' one.
