Skip to content

Commit 927ce97

Browse files
Add changes to SCK migration doc after testing migration scenario (signalfx#605)
* Add changes to SCK migration doc after testing migration scenario * Update docs/migration-from-sck.md Co-authored-by: harshit-splunk <[email protected]> Co-authored-by: harshit-splunk <[email protected]>
1 parent 6159f52 commit 927ce97

File tree

1 file changed

+28
-0
lines changed

1 file changed

+28
-0
lines changed

docs/migration-from-sck.md

Lines changed: 28 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -335,3 +335,31 @@ To delete the SCK deployment, find the name of the deployment using the `helm ls
335335
* ```index="Your logs index"```
336336
* Check the metrics index to see if you are receiving metrics from your Kubernetes cluster
337337
* ```| 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 |
357+
|-------------------------------|-----------------------------------------------|
358+
| container_id | container.id |
359+
| container_image | container.image.name and container.image.tag |
360+
| container_name | k8s.container.name |
361+
| cluster_name | k8s.cluster.name |
362+
| namespace | k8s.namespace.name |
363+
| pod | k8s.pod.name |
364+
| pod_uid | k8s.pod_uid |
365+
| label_app | k8s.pod.labels.app |

0 commit comments

Comments
 (0)