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
Copy file name to clipboardExpand all lines: content/en/tko/session-5/docs/check-new-navigator.md
+25-33Lines changed: 25 additions & 33 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,23 +3,21 @@ title: The new Kubernetes Navigator
3
3
linkTitle: Touring the Kubernetes Navigator v2
4
4
weight: 22
5
5
---
6
-
## 1 The k8s cluster & cluster detail Pane
6
+
## 1. The k8s cluster & cluster detail Pane
7
7
8
8
Go to the **Infrastructure** page in the Observability UI and select **Kubernetes**, this will offer you a number of kubernetes services. For this exercise pick the `K8s cluster` pane.
9
9
10
10
11
11
12
12
The first thing you notice is that the pane indicates how many clusters are being monitored for you. The pane also shows a tiny graph of the load being handled across those clusters for a birds eye view. Lastly, if there is a alert for one of the clusters it will be highlighted here too.
13
13
14
-
Click or select on the pane and you will be taken to the `Infrastructure/Kubernetes/ K8s clusters` overview pane. Here you will find a list off all the Kubernetes clusters that are sending data to the Splunk Observability Cloud platform.
14
+
Click or select on the pane and you will be taken to the `Infrastructure/Kubernetes/ K8s clusters` overview pane. Here you will find a list off all the Kubernetes clusters that are sending data to the Splunk Observability Cloud platform.
15
15
16
16
### 1.1 Finding your K8s cluster name
17
17
18
-
Your first task is to identify and find your own cluster.
18
+
Your first task is to identify and find your own cluster. The cluster will be named after your EC2 instance name: `ws-5-X-k3s-cluster` where `X` is the number of the EC2 instance assigned to you.
19
19
20
-
The cluster will be named after your EC2 instance name: `ws-5-X-k3s-cluster` where `X` is the number of the EC2 instance assigned to you.
21
-
22
-
To find your node name look at the prompt of your EC2 instance, assuming you are assigned the 7th ec2 instance the prompt will show
20
+
To find your node name look at the prompt of your EC2 instance, assuming you are assigned the 7th EC2 instance the prompt will show
23
21
24
22
```bash
25
23
ubuntu@ws-5-7 ~ $
@@ -28,79 +26,75 @@ ubuntu@ws-5-7 ~ $
28
26
This means your cluster is named: `ws-5-7-k3s-cluster` make a note as you will need this later in the workshop as a filter.
Find your Cluster in the Observability Kubernetes Navigator, and identify the amoutn of containers that are running at this point.
29
+
Find your Cluster in the Observability Kubernetes Navigator, and identify the amount of containers that are running at this point.
32
30
33
31
**Tip:** You may need to switch the Color By option to containers and refresh the screen a few times until the cluster data is correlated in the background. Also, it is recommended to set the timeframe to be `15m` (down from `3h` which is default).
34
32
{{% /alert %}}
35
33
36
34
### 1.2 Using the K8s cluster Selection Pane
37
35
38
-
The k8s cluster Selection Pane by default, will offer a list view of your clusters like shown below.
36
+
The K8s cluster Selection Pane by default, will offer a list view of your clusters like shown below.
You can scroll down the k8s cluster list or by using the filter on the top toolbar, *(marked with a blue stripe)*, with the field `k8s.cluster.name`, to find your Cluster. </br>
43
-
You can enter a partial name into the search box such as 'ws-5-7', to find quickly find your Cluster.
40
+
You can scroll down the K8s cluster list or by using the filter on the top toolbar, *(marked with a blue stripe)*, with the field `k8s.cluster.name`, to find your Cluster.
44
41
45
-
Also its is a good idea to switch the default time from the default 3 hours back to 15 minutes.
42
+
You can enter a partial name into the search box such as 'ws-5-7', to find quickly find your Cluster. Also, its is a good idea to switch the default time from the default 3 hours back to 15 minutes.
46
43
47
44
If there are many clusters, you can change the Result per page box *Marked by an orange line*, to increase the list size.
48
45
49
-
You will note that each cluster row has a colored mark at the end of each row. These will change according the `color by` option, *Marked by a green line*, you have selected as to indicate its range.
46
+
You will note that each cluster row has a colored mark at the end of each row. These will change according the `color by` option, *Marked by a green line*, you have selected as to indicate its range.
47
+
48
+
These are the possible options at this time:
50
49
51
-
These are the possible options at this time:</br>
52
50
53
51
54
52
Next, you can change the the list view to a heat map view by selecting either the Heatmap or List icon *(Marked by a purple line).*
55
53
56
-
This will result in the follow representation:</br>
54
+
This will result in the follow representation:
55
+
57
56
58
57
59
58
This might be a useful view if you have many cluster as they can be grouped together using the group by option *Marked by the green line* . The colors of each node will follow the color by choice similar to the list view.
60
59
61
60
The last option, is the Find Outliers based on historical analytics of your clusters based on what is selected in the `colored by` box.
62
61
63
62
This view is better used when you view all or a selection of you cluster. It will give you a quick insight which of your clusters are behaving differently than they do normally and may need further investigation.
64
-
You may not see relevant info, The clusters in this workshop are short lived and have not send enough meaningful data for the historical analytics to detect deviations.
63
+
64
+
You may not see relevant info, the clusters in this workshop are short lived and have not send enough meaningful data for the historical analytics to detect deviations.
65
65
66
66
### 1.3 The K8s cluster detail Pane
67
67
68
68
Initially,the cluster detail pane will show you the overall performance across all the servers as show below.
69
+
69
70
70
71
71
72
As soon as you select your own cluster, you can see the overall performance of your luster, in this view you also can see if your cluster is affected by an alert:
You may note that a `single alert` has fired for this example Cluster
76
+
You may note that a `single alert` has fired for this example Cluster.
76
77
77
-
## 3. The Nodes & Node Details Pane
78
+
## 2. The Nodes & Node Details Pane
78
79
79
-
Go to the **Infrastructure** page in the Observability UI and select **Kubernetes**, this again will offer you a number of kubernetes services. For this exercise pick the `K8s Nodes` pane.
80
+
Go to the **Infrastructure** page in the Observability UI and select **Kubernetes**, this again will offer you a number of kubernetes services. For this exercise pick the `K8s Nodes` pane. When selected it may show a cluster that you have selected previously.
80
81
81
82
82
83
83
-
When Selected it may show a cluster that you have select4d previously,
84
-
85
-
-------
86
-
87
84
In a production environment you would expect to see multiple Nodes within a Cluster which would now all be visible and shown as individual pale blue squares, each containing green squares which represent pods, however in our workshop environment you each have a single node within your Cluster, represented by the large single blue square.
88
85
89
86
Drill down into the single Node by hovering over the pale blue background, then clicking on either the magnifying glass that appears in the top left corner, or double clicking on the pale blue background, this will take you to the Node level view.
90
87
91
-
92
88
You should now be able to see all the Pods and Containers running on your single Node Cluster...
93
89
94
90
95
91
96
-
but more importantly, the 'side panel' should have also switched to the Info Tab and is now showing lots of contextual information about the Node.
92
+
But, more importantly, the *side panel* should have also switched to the Info Tab and is now showing lots of contextual information about the Node.
There are various Panes showing details on the Properties of the Node, and all the various Workloads running on it, even though we are still on the 'Map' tab within Kubernetes Navigator.
101
97
102
-
---
103
-
104
98
At the top of the side panel, click on the Expand icon  which takes you to the full screen tab of the currently displayed resource, which in this case is a Node, so we end up on the Node Details Tab.
105
99
106
100
Node Details shows you lots of great detail about what is happening on this Node, with charts for total CPU Usage, Mem Usage, Network traffic etc for all the Pods running on the Node with a list of any Events just to the right of these Charts.
@@ -111,7 +105,7 @@ You also have scrollable table views of both the Workloads and Containers runnin
111
105
How much memory and how many CPU cores does our one node have?
112
106
{{% /alert %}}
113
107
114
-
## 4. Workloads & Workload Details Tabs
108
+
## 3. Workloads & Workload Details Tabs
115
109
116
110
Assuming you have been able to answer the question about the Node CPU cores, you will now need to switch to the Workloads tab on the top toolbar. The Workloads tab details all the workloads that are deployed within your cluster.
117
111
@@ -127,7 +121,7 @@ To get more detail on a specific Workload, simply click on its name in the Workl
127
121
128
122
---
129
123
130
-
### Workload Detail tab
124
+
### 3.1 Workload Detail tab
131
125
132
126
Here you will get the general info about your Workload, the CPU and Memory the Containers are consuming, the Pods and their Phase, details of any Events, and finally a list of Pods related to this Workload.
133
127
@@ -137,14 +131,12 @@ As with the other Kubernetes Navigator views clicking on the name of a Pod withi
137
131
How many containers does the `splunk-otel-collector-agent` Pod contain?
138
132
{{% /alert %}}
139
133
140
-
## 5. Pod Detail & Container Details Tabs
141
-
142
-
The last two Tabs that make up the Kubernetes Navigator are Pod Detail and Container Detail.
134
+
## 4. Pod Detail & Container Details Tabs
143
135
144
-
The Pod Detail view will show you the Pod Properties, CPU, Memory and Network usage along with any events relevant to the Pod.
136
+
The last two Tabs that make up the Kubernetes Navigator are Pod Detail and Container Detail. The Pod Detail view will show you the Pod Properties, CPU, Memory and Network usage along with any events relevant to the Pod.
145
137
146
138
Clicking through to the Container Detail Tab, you should know how to do this by now, but just to play safe, select one of the Containers in the list then click the expand button  to navigate to the Container Detail Tab.
147
139
148
140
If you navigated straight to the Container Detail Tab by simply clicking on the Tab, try using the Container ID drop down to select a container, now you will see the benefit of 'clicking through' to get to the desired Container!
149
141
150
-
You can now see the details for the Selected Container, with the Container Properties pane offering lots of detail on its configuration
142
+
You can now see the details for the Selected Container, with the Container Properties pane offering lots of detail on its configuration.
Copy file name to clipboardExpand all lines: content/en/tko/session-5/docs/deploy-otel-navi2.md
+6-10Lines changed: 6 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: Deploying the OpenTelemetry Collector in Kubernetes using a NameSpace
3
3
linkTitle: Prep UI & Deploy the OTel Collector
4
4
weight: 21
5
5
---
6
-
## 0. Switching to the new Kubernetes Navigator 2.0 UI
6
+
## 1. Switching to the new Kubernetes Navigator 2.0 UI
7
7
8
8
As we are in the process of switched to the new generation of the Kubernetes Navigator please check if you are already on the new Kubernetes navigator.
9
9
@@ -13,9 +13,7 @@ When you select `Kubernetes` as you focus, you should see a number of services p
13
13
14
14
If you taken straight to the Kubernetes Navigator v1 after selecting `Kubernetes` in the right hand menu, you need to set the feature flag for the new Navigator yourself.
15
15
16
-
To do this, please change the Url in your browser to match the following:
17
-
18
-
https://app.[REALM].signalfx.com/#/Superpowers
16
+
To do this, please change the Url in your browser to match the following: [https://app.[REALM].signalfx.com/#/superpowers](https://app.[REALM].signalfx.com/#/superpowers)
19
17
20
18
Were [REALM] needs to match the Realm we are running this workshop in.
21
19
@@ -37,7 +35,7 @@ You can fix this by pressing the 
37
35
You may need to do this once per service type (Cluster/Nodes/Workloads).
38
36
{{% /alert %}}
39
37
40
-
## 1. Connect to EC2 instance
38
+
## 2. Connect to EC2 instance
41
39
42
40
You will be able to connect to the workshop instance by using SSH from your Mac, Linux or Windows device.
43
41
@@ -47,7 +45,7 @@ To use SSH, open a terminal on your system and type `ssh [email protected]` (replac
47
45
Your workshop instance has been pre-configured with the correct `ACCESS_TOKEN` and `REALM` for this workshop. There is no need for you to configure these.
48
46
{{% /alert %}}
49
47
50
-
## 2. Namespaces in Kubernetes
48
+
## 3. Namespaces in Kubernetes
51
49
52
50
Most of our customers will make use of some kind of private or public cloud service to run Kubernetes. They often choose to have only a few large Kubernetes clusters as it is easier to manage centrally.
53
51
@@ -57,7 +55,7 @@ Any number of namespaces are supported within a cluster, each logically separate
57
55
58
56
Most customers will want to install the Splunk OpenTelemetry Collector in a separate namespace. This workshop will follow that practice.
59
57
60
-
## 3. Install Splunk OTel using Helm
58
+
## 4. Install Splunk OTel using Helm
61
59
62
60
Install the OpenTelemetry Collector using the Splunk Helm chart. First, add the Splunk Helm chart repository and update.
You can monitor the progress of the deployment by running `kubectl get pods` and adding `-n splunk` to the command to see the pods in the `splunk` NameSpace which should typically report that the new pods are up and running after about 30 seconds.
0 commit comments