Why central observability?

Why Observability Header Image
Raj Nair
Raj Nair

Founder & CEO

22 April, 2022

2 min read




Organizations undertaking modernization must support a hybrid deployment model where data and workloads often have to be in different locations — near premises (data center or edge) and public cloud. For compliance, data sometimes needs to be in a certain geography to meet regulations & 
security standards. Certain public clouds offer special processing advantages for certain workloads. Thus, to address these scenarios, workloads need to be able to be deployed across locations and yet have observability to help manage and troubleshoot fault conditions.


Current tools for observability are focused on single cluster deployments and require the operator to correlate using logs from multiple clusters to develop a comprehensive view of the end-to-end picture. This makes it difficult to pinpoint trouble spots and identify issues. Clearly, this is not a good way to 
operate production infrastructures and has contributed to growth of very large single clusters that have stifled the development of applications that truly need to be distributed as described above.


An important tenet of a distributed deployment is the need to have a single pane of glass to observe a distributed deployment. An “application slice” (available in Avesha’s KubeSlice product) is a building block to make Kubernetes infrastructure manageable with focussed visibility. Avesha’s KubeSlice Manager product achieves this objective by offering a slice-wide view of a deployment that shows what is happening across a slice from one place. This includes information about inter-service traffic via the tunnel endpoints represented as Sankey graphs for bandwidth and inter-service latency via a hub controller fed from Service Mesh (e.g. Linkerd or Istio). KubeSlice Manager product is a self-service product to allow application developers to create application slices and multi-cluster namespaces on their own without any assistance from devops or netops teams. Once installed, the KubeSlice allows the platform team to templatize clusters and set slice limits in a scalable manner.