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
we can see the otelcolInstrumentation statefulset is up and working, service/service.go:148 Everything is ready. Begin running and processing data.
the trace gateway is up and working: service/service.go:148 Everything is ready. Begin running and processing data.
the trace sampler is working as well
Describe the bug A clear and concise description of what the bug is.
when release the helm , this is the related config:
we can see the otelcolInstrumentation statefulset is up and working,
service/service.go:148 Everything is ready. Begin running and processing data.
the trace gateway is up and working:
service/service.go:148 Everything is ready. Begin running and processing data.
the trace sampler is working as well
when we configure the application service with the endpoint of http://sumologic-collector-otelagent.sumologic.svc.cluster.local:4318 to send traces, the application can receive 200, but i dont see any traces processed, no logs shown in above 3 pods.
i wonder if i did something wrong,
hope you can help me pls
Logs Logs which can be helpful in investigating the issue.
Command used to install/upgrade Collection Direct command which you used to install/upgrade collection.
Configuration Configuration used for Collection e.g. user-values.yaml for helm.
To Reproduce Steps to reproduce the behavior.
Expected behavior A clear and concise description of what you expected to happen.
Environment (please complete the following information):
we are using this helm chart version
https://github.com/SumoLogic/sumologic-kubernetes-collection/blob/v3.11.0/docs/opentelemetry-collector.md#traces
helm ls -n sumologic
):3.11.0
kubectl version
):1.30.0
aws
Anything else do we need to know Add any other context about the problem here, e.g. issue happens only occasionally.
The text was updated successfully, but these errors were encountered: