Closed maulikp-splunk closed 3 years ago
Hi @maulikp-splunk ,
Deployment of otel-collector was failing because Google added their own build of otel-collector for metrics collection to GKE nodes by default and there was a conflict on port 8888 for internal collector's metrics collection.
Google switched their agent from 8888 to 8200, and the agent should be automatically upgraded by now. So if you try to install the splunk-otel-collector again there shouldn't be any issues.
Please let me know how it goes.
Thank you @dmitryax !! You are the best as always !! I tried installing it today, and works perfectly fine!
Hello team,
I am using helm version
splunk-otel-collector-0.26.1
on GKE(1.19.9-gke.1400)
and noticed that splunk-otel-collector pod is inCrashLoopBackOff
state.Here are log details from otel-collector container in splunk-otel-collector pod: