You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This section is split in two and is going to be a little longer, the first section is a quick intro to the main page, followed by a section to dive deeper into some of the special features of the Splunk Observability suite, before we start to use our application and validate performance.
9
+
This section is split in multiple sections and is going to be a little longer, the first section is a quick intro to the main page, followed by a few sections to dive deeper into some of the special features of the Splunk Observability suite, before we start to use our application and validate performance.
10
10
11
11
Please select Splunk Infrastructure from the menu bar on the right by selecting the . This will bring us to the Infrastructure Home Page. It has 4 distinct sections that provide information on all technology that is sending metrics to the Splunk observability Suite.
In the Kubernetes Navigator, your cluster is represented by the square with the black line, it will contain one or more blue squares representing the node(s), each of them wil contain one or more colored boxes that represent pods.
16
+
and as you can guess, *Green* means healthy & *Red* means that there is a problem.
16
17
17
-
The screenshot above shows the main part of the kubernetes navigator. It will show all the clusters & their nodes that send metrics to the Splunk Observability Suite. In the workshop you will mostly see single node kubernetes cluster.
18
-
19
-
Let's make sure we are looking at our own cluster.
18
+
Given there are two red boxes, lets see what is going on and if this will affect our E-commerce site.
* First, use the  option to pick your cluster.
24
-
* This can be done by selecting *k8s.cluster.name* from the filter drop down box.
25
-
* You then can start typing the name of you cluster, (as provided by your instructor). The name should also appear in the drop down values. Select yours and make sure just the one for your workshop is highlighted with a .
26
-
* Click the {{% button style="blue" %}} Apply Filter {{% /button %}} button to focus on our Cluster
27
-
* We now should have a single cluster visible.
28
-
{{% /notice %}}
22
+
* First, set the time window we are working with to th last 15 minutes. You do this by using the drop down in the Filter pane  to *the last 15 minutes*.
23
+
* The Cluster Metric charts you can see below the cluster representation, provide information on your cluster, like the memory consumption and the number of pods per node. none of these will explain why there are red pods.
24
+
* Let's check if the Spunk Kubernetes Analyzer can tell us something more useful, so click on **K8s analyzer**.
29
25
30
-
Let's move on the next page of this exercise and look at your cluster in detail.
26
+
* The Spunk Kubernetes Analyzer is a smart process that runs in the background in the Splunk Observability Suite, designed to detect relations between anomalies.
27
+
It should have detected that the two Red pods are similar and come from the same name space.
28
+
* Can you find what name space? (hint, look for *k8s.namespace.name*)
Navigate to the K8s Navigator ... walk through ... filtering, metrics, node dependencies, etc.
32
+
* Click on the name of namespace, this should add a filter to the filter pane, *k8s.namespace.name=development
33
+
* This filter will highlight all pods that are part of the development namespace. As you can see only the two *"bad"* pods are highlighted This is a quick indication that our e-commerce site is not affected by these error pods.
35
34
36
-
Talk around what has been deployed
35
+
* To confirm this click on **K8s node**. This will provide node metrics, and you can see that there are two pods in the development name space, and in the node workloads chart, you should be able to see that the *test=job* is in a failed state.
36
+
* If you now remove the filter for the *k8s.namespace.space* from the filter Pane, the Node workload chart will show you all the workload on this node now, and again only the *test-job* in *development* has failed.
37
37
38
-
* Talk around initial panes goto Nodes
39
-
* Filter to workshop cluster
40
-
* Review default metrics
41
-
* Node dependencies
42
-
* Click on mysql pod
43
-
* Talk around metadata for the container
44
-
* Back to Infrastructure
38
+
The above scenario is common in a shared kubernetes environment, where teams deploy application in different stages. Kubernetes is designed to keep those environment completely separate.
39
+
40
+
{{% /notice %}}
45
41
46
-
Something to trigger alerts in Navigator?
47
-
42
+
We can safely assume these pods do not affect us, so move on to look at few more things.
This pane provides alert information, info on detected services and shows meta data related to the object your looking at, in this case a kubernetes node running on an ec2 instance in AWS.
Meta Data is send along wth the metrics an are very useful to identify trends when identifying issues. An example could be a pod failing when deployed on a specific Operating system.
19
+
20
+
* Can you identify what the Operating System and Architecture is what our node is running using the Meta Data?
21
+
22
+
We can these fields to filter in charts and/or detectors to drill down to a specific subset of metrics we are interested in.
23
+
24
+
{{% /notice %}}
25
+
26
+
An other feature of the Splunk Observability UI, is what we call *Related content*.
27
+
28
+
The Splunk Observability UI will try to show you links to information that is related to the topic you are actively looking at. A good example of this are the services running on this node.
The screenshot above shows the main part of the kubernetes navigator. It will show all the clusters & their nodes that send metrics to the Splunk Observability Suite. In the workshop you will mostly see single node kubernetes cluster.
18
18
19
-
Let's make sure we are looking at our own cluster.
K8s, short for Kubernetes, is an open-source container orchestration platform. It manages the deployment, scaling, and maintenance of containerized applications, and we use it in this workshop to host our e-commerce application
22
+
Some terminology:
23
+
24
+
* A Kubernetes cluster is a group of machines, called nodes, that work together to run containerized applications.
25
+
* Nodes are individual servers or VMs in the cluster. Typically, you would have several nodes in a cluster but you may have just one node, just like in this workshop.
26
+
* Pods are the smallest deployable units in Kubernetes, representing one or more containers that share the same network and storage, enabling efficient application scaling and management
27
+
* Applications is a collection of one or more pods interacting together to provide a service.
28
+
* Namespaces help you keep your applications organized and separate within the cluster,by providing a logical separation for multiple teams or projects within a cluster.
29
+
* Workloads are like a task list and define how many instances of your application should run, how they should be created, and how they should respond to failures
30
+
31
+
{{% /notice %}}
32
+
33
+
Before we dive deeper, let's make sure we are looking at our own cluster.
* First, use the  option to pick your cluster.
37
+
* First, use the  option to pick your cluster.
24
38
* This can be done by selecting *k8s.cluster.name* from the filter drop down box.
25
-
* You then can start typing the name of you cluster, (as provided by your instructor). The name should also appear in the drop down values. Select yours and make sure just the one for your workshop is highlighted with a .
39
+
* You then can start typing the name of you cluster, (as provided by your instructor). The name should also appear in the drop down values. Select yours and make sure just the one for your workshop is highlighted with a .
26
40
* Click the {{% button style="blue" %}} Apply Filter {{% /button %}} button to focus on our Cluster
0 commit comments