Collector for Kubernetes: Gather support information ๐
If youโre an existing Splunk Observability Cloud customer and have issues with the Collector, you can contact Support. See how at Splunk Observability Cloud support. Splunk Enterprise and Splunk Cloud customers with Splunk support entitlement can reach out to Splunk Support at Splunk Contact Us .
Gather information for Support ๐
When opening a support request, try to include as much information about the issue as possible, including:
What did you try to do?
What happened?
What did you expect to happen?
Have you found any workaround?
How impactful is the issue?
How can we reproduce the issue?
In addition, include the following information:
Which destination is configured: Splunk Platform or Splunk Observability?
Helm chart version.
Custom values.yaml file you applied with either the
helm install
command or--set
arguments.Are there any manual customization done to the Kubernetes resources once the chart is installed?
Kubernetes cluster details:
Kubernetes version.
Managed or on premises: if managed, which cloud provider and distribution?
ConfigMaps from problematic pods:
kubectl get cm my-splunk-otel-collector-agent -o yaml > my-splunk-otel-collector-agent-cm.yaml
kubectl get cm my-splunk-otel-collector-k8s-cluster-receiver -o yaml > my-splunk-otel-collector-k8s-cluster-receiver-cm.yaml
Logs from problematic pods:
kubectl logs my-splunk-otel-collector-agent-fzn4q otel-collector > my-splunk-otel-collector-agent.log
kubectl logs my-splunk-otel-collector-k8s-cluster-receiver-7545499bc7-vqdsl > my-splunk-otel-collector-k8s-cluster-receiver.log
Note
You can use the kubectl-splunk
support bundle script to gather this information. Find it at the Splunk kubectl GitHub repository .