Configure a segment for signals and monitored entities related to multiple Kubernetes clusters in a common stack.
This article is intended for administrators and Kubernetes operators who need to organize and logically structure workloads on Kubernetes clusters.
In this article, you'll learn how to create a segment to conveniently filter observability signals and monitored entities in the Kubernetes domain.
storage:filter-segments:write and storage:filter-segments:read permissions. To learn how to set up the permissions, see Permissions in Grail.
Kubernetes and open Explorer.Anyone in the environment so others can find and use this segment.At this point, the segment doesn't specify what data it should include. In the next section, we will reference data to be filtered with this segment.
k8s.cluster.name = gke-klu.
In this step, we show how to
Problems
Services
DashboardsTo analyze general health of our stack in
Problems
ProblemsTo analyze health and performance of services of our stack in
Services
Services and select Explorer tab.To analyze Kubernetes workloads of our stack in
Dashboards
Dashboards and select Ready-made dashboards.Applying a segment to dashboards will filter for data explicitly included in segment. Some tiles may no longer show results because queried data isn't included in the applied segment.
You’ve configured a segment for a set of Kubernetes clusters that form a common stack. You’ve learned how segments can be applied to conveniently filter data in different apps. You've seen an example how to analyze health and performance of a monitoring environment without having to write or understand a single line of DQL yourself.
Just as for Kubernetes clusters, segments can also be built with the context of Kubernetes namespaces. Simply use k8s.namespace.name and select all related entities of Kubernetes namespaces (dt.entity.cloud_application_namespace) instead.