-
Notifications
You must be signed in to change notification settings - Fork 506
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
oltp grpc exporter failing in k8s deployment using helm charts #114
Comments
Hey @parth-purohit do you still need help with this issue? If so, can you provide:
Thanks! |
Hi @TylerHelmuth I tried using the latest version and still facing the issue with opentelemetry-collector-0.9.4
Thanks! |
Thanks. I'll be on PTO until next week but I will look when I get back. Can you include your values.yaml as well? |
Any chance you have a proxy in your environment that the agent would be interacting with? |
Hi @TylerHelmuth I tried running it on a different machine and it worked. Previous machine had some rules blocking traffic so it was failing. We can close the this issue. Thanks :) |
@dmitryax Ready to close. |
Hi Team,
I have deployed both otel-collector as daemonset and standalone deployment as per the README docs in below link
https://github.com/open-telemetry/opentelemetry-helm-charts/tree/main/charts/opentelemetry-collector
agentCollector:
enabled: true
standaloneCollector:
enabled: true
The oltp grpc exporter in agent pod is failing with below error:
Steps followed:
helm install --set standaloneCollector.enabled=true my-opentelemetry-collector open-telemetry/opentelemetry-collector
kubectl logs -f daemonset/my-opentelemetry-collector-agent
Could you please help resolve this issue.
The text was updated successfully, but these errors were encountered: