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: docs/migration-from-sck.md
+28Lines changed: 28 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -335,3 +335,31 @@ To delete the SCK deployment, find the name of the deployment using the `helm ls
335
335
* ```index="Your logs index"```
336
336
* Check the metrics index to see if you are receiving metrics from your Kubernetes cluster
337
337
* ```| mcatalog values(metric_name) WHERE index="Your metrics index"```
338
+
339
+
## Differences between Splunk Connect for Kubernetes and Splunk OpenTelemetry Collector for Kubernetes
340
+
341
+
### Read logs location
342
+
343
+
Splunk Connect for Kubernetes by default read containers logs from `/var/log/containers/*`
344
+
Splunk OpenTelemetry Collector for Kubernetes by default read containers logs from `/var/log/pods/*`
345
+
Change is reflected in `source` filed for extracted logs.
346
+
347
+
### Default `sourcetype` for containers logs
348
+
349
+
Both Splunk Connect for Kubernetes and Splunk OpenTelemetry Collector for Kubernetes define `sourcetype` for container logs as `kube:container:<container_name>` by default. But, Splunk Connect for Kubernetes explicitly defines the sourcetype of Kubernetes core components as `kube:<container_name>`. They are defined [here](https://github.com/splunk/splunk-connect-for-kubernetes/blob/2cae9b12bbd6545c9ef09b23e619b9783d9ceb38/helm-chart/splunk-connect-for-kubernetes/values.yaml#L330-L408)
350
+
`sourcetype`configuration can be changed by adding `logsCollection.containers.extraOperators` configuration.
351
+
352
+
### Extracted fields for logs
353
+
354
+
Splunk OpenTelemetry Collector for Kubernetes follows naming convention for OpenTelemetry for extracted fields. Table below present differences in filed names extracted by Splunk OpenTelemetry Collector for Kubernetes and Splunk Connect for Kubernetes
355
+
356
+
| Splunk Connect for Kubernetes | Splunk OpenTelemetry Collector for Kubernetes |
0 commit comments