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/ninja-workshops/11-ingest_processor_for_observability_cloud/1-getting-started/1-access-cloud-instances.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,10 +22,12 @@ Login to Splunk Show using your [splunk.com](https://login.splunk.com/) credenti
Take note of the Participant Number provided in your Splunk Show event details. This number will be included in the `sourcetype` that you will use for searching and filtering the Kubernetes data. Because this is a shared environment only use the participant number provided so that other participants data is not effected.
25
+
Take note of the `User Id` provided in your Splunk Show event details. This number will be included in the `sourcetype` that you will use for searching and filtering the Kubernetes data. Because this is a shared environment only use the participant number provided so that other participants data is not effected.
26
26
27
27
{{% /notice %}}
28
28
29
+

30
+
29
31
## 2. Splunk Observability Cloud Instances
30
32
31
33
You should have also received an email to access the Splunk Observability Cloud workshop organization (You may need to check your spam folder). If you have not received an email, let your workshop instructor know. To access the environment click the **Join Now** button.
Copy file name to clipboardExpand all lines: content/en/ninja-workshops/11-ingest_processor_for_observability_cloud/3-create-an-ingest-pipeline/1-login-to-splunk.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,27 +8,27 @@ In this section you will create an Ingest Pipeline which will convert Kubernetes
Copy file name to clipboardExpand all lines: content/en/ninja-workshops/11-ingest_processor_for_observability_cloud/3-create-an-ingest-pipeline/2-review-k8s-events.md
+13-7Lines changed: 13 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,23 +8,29 @@ In this section you will review the Kubernetes Audit Logs that are being collect
You should now see the Kubernetes Audit Logs for your environment. Notice that the events are fairly robust. Explore the available fields and start to think about what information would be good candidates for metrics and dimensions. Ask yourself: What fields would I like to chart and how would I like to be able to filter, group, or split those fields?
32
+
<center>
33
+
<b>You should now see the Kubernetes Audit Logs for your environment. Notice that the events are fairly robust. Explore the available fields and start to think about what information would be good candidates for metrics and dimensions. Ask yourself: What fields would I like to chart and how would I like to be able to filter, group, or split those fields?</b>
Copy file name to clipboardExpand all lines: content/en/ninja-workshops/11-ingest_processor_for_observability_cloud/3-create-an-ingest-pipeline/3-create-ingest-pipeline.md
+21-19Lines changed: 21 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ In this section you will create an Ingest Pipeline which will convert Kubernetes
4. In the **Define your pipeline’s partition** step of the Ingest Processor configuration page select **Partition by sourcetype**. Select the **= equals** Operator and enter `kube:apiserver:audit:PARTICIPANT_NUMBER` (Be sure to replace PARTICIPANT_NUMBER with the participant number you were assigned) for the value. Click **Apply**.
31
+
**4.** In the **Define your pipeline’s partition** step of the Ingest Processor configuration page select **Partition by sourcetype**. Select the **= equals** Operator and enter `kube:apiserver:audit:USER_ID` (Be sure to replace USER_ID with the User ID you were assigned) for the value. Click **Apply**.
6. In the **Add sample data** step of the Ingest Processor configuration page select **Capture new snapshot**. Enter `k8s_audit`for the name and click **Capture**.
37
+
**6.** In the **Add sample data** step of the Ingest Processor configuration page select **Capture new snapshot**. Enter `k8s_audit_USER_ID` (Be sure to replace USER_ID with the User ID you were assigned) for the Snapshot name and click **Capture**.
9. In the **Select a data destination** step of the Ingest Processor configuration page select **splunk_indexer**. Under **Specify how you want your events to be routed to an index** select **Default**. Click **Done**.
49
+
**9.** In the **Select a data destination** step of the Ingest Processor configuration page select **splunk_indexer**. Under **Specify how you want your events to be routed to an index** select **Default**. Click **Done**.
**Replace `UNIQUE_FIELD` in the metric name with a unique value which will be used to identify your metric in Observability Cloud.**
56
+
**Replace `UNIQUE_FIELD` in the metric name with a unique value (such as your initials) which will be used to identify your metric in Observability Cloud.**
57
57
{{% /notice %}}
58
58
59
59
```
@@ -63,12 +63,14 @@ import logs_to_metrics from /splunk/ingest/commands
63
63
$pipeline =
64
64
| from $source
65
65
| thru [
66
-
//define the metric name, type, and value for the Kubernetes Events
{{% notice title="New to SPL2?" style="info" icon="lightbulb" %}}
@@ -83,15 +85,15 @@ Here is a breakdown of what the SPL2 query is doing:
83
85
84
86
{{% /notice %}}
85
87
86
-
11. In the upper-right corner click the **Preview** button  or press CTRL+Enter (CMD+Enter on Mac). From the **Previewing $pipeline** dropdown select **$metrics_destination**. Confirm you are seeing a preview of the metrics that will be sent to Splunk Observability Cloud.
88
+
**11.** In the upper-right corner click the **Preview** button  or press CTRL+Enter (CMD+Enter on Mac). From the **Previewing $pipeline** dropdown select **$metrics_destination**. Confirm you are seeing a preview of the metrics that will be sent to Splunk Observability Cloud.
12. In the upper-right corner click the **Save pipeline** button . Enter a name for your pipeline and click **Save**.
92
+
**12.** In the upper-right corner click the **Save pipeline** button . Enter `Kubernetes Audit Logs2Metrics USER_ID`for your pipeline name and click **Save**.
Copy file name to clipboardExpand all lines: content/en/ninja-workshops/11-ingest_processor_for_observability_cloud/3-create-an-ingest-pipeline/4-confirm-metrics.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,11 +8,11 @@ Now that an Ingest Pipeline has been configured to convert Kubernetes Audit Logs
1. Login to the **Splunk Observability Cloud** organization you were invited for the workshop. In the upper-right corner, click the **+** Icon -> **Chart** to create a new chart.
11
+
**1.** Login to the **Splunk Observability Cloud** organization you were invited for the workshop. In the upper-right corner, click the **+** Icon -> **Chart** to create a new chart.
12
12
13
13

14
14
15
-
2. In the **Plot Editor** of the newly created chart enter the metric name you used while configuring the **Ingest Pipeline**.
15
+
**2.** In the **Plot Editor** of the newly created chart enter the metric name you used while configuring the **Ingest Pipeline**.
Copy file name to clipboardExpand all lines: content/en/ninja-workshops/11-ingest_processor_for_observability_cloud/4-update-pipeline-and-visualize/1-update-ingest-pipeline.md
2. To add dimensions to the metric from the raw Kubernetes audit logs update the SPL2 query you created for the pipeline by replacing the `logs_to_metrics` portion of the query with the following.
13
+
**2.** To add dimensions to the metric from the raw Kubernetes audit logs update the SPL2 query you created for the pipeline by replacing the `logs_to_metrics` portion of the query with the following:
@@ -26,20 +26,40 @@ Using the `dimensions` field in the SPL2 query you can add dimensions from the r
26
26
You should consider adding any common tags across your services so that you can take advantage of context propagation and related content in Splunk Observability Cloud.
27
27
{{% /notice %}}
28
28
29
-
3. In the upper-right corner click the **Preview** button  or press CTRL+Enter (CMD+Enter on Mac). From the **Previewing $pipeline** dropdown select **$metrics_destination**. Confirm you are seeing a preview of the metrics that will be sent to Splunk Observability Cloud.
29
+
The updated pipeline should now be the following:
30
+
31
+
```
32
+
/*A valid SPL2 statement for a pipeline must start with "$pipeline", and include "from $source" and "into $destination".*/
33
+
/* Import logs_to_metrics */
34
+
import logs_to_metrics from /splunk/ingest/commands
35
+
$pipeline =
36
+
| from $source
37
+
| thru [
38
+
//define the metric name, type, and value for the Kubernetes Events
**3.** In the upper-right corner click the **Preview** button  or press CTRL+Enter (CMD+Enter on Mac). From the **Previewing $pipeline** dropdown select **$metrics_destination**. Confirm you are seeing a preview of the metrics that will be sent to Splunk Observability Cloud.
4. Confirm you are seeing the dimensions in the dimensions column of the preview table. You can view the entire dimensions object by clicking into the table.
53
+
**4.** Confirm you are seeing the dimensions in the dimensions column of the preview table. You can view the entire dimensions object by clicking into the table.
5. In the upper-right corner click the **Save pipeline** button . On the “You are editing an active pipeline modal” click **Save**.
57
+
**5.** In the upper-right corner click the **Save pipeline** button . On the “You are editing an active pipeline modal” click **Save**.
<b>Because this pipeline is already active, the changes we’ve made will take effect immediately. Your metric should now be split into multiple metric timeseries using the dimensions you added.</b>
62
+
<b>Because this pipeline is already active, the changes you made will take effect immediately. Your metric should now be split into multiple metric timeseries using the dimensions you added.</b>
43
63
44
64
In the next step you will create a visualization using different dimensions from the kubernetes audit events.
0 commit comments