pod:
signoz-server-otel-collector-5b5cfcc785-xzx8w...
# contributingt
tao fei
09/06/2023, 9:07 AMpod:
signoz-server-otel-collector-5b5cfcc785-xzx8w 1/1 Running 0 21h
kubectl --namespace apm port-forward signoz-server-otel-collector-5b5cfcc785-xzx8w 4317:4317
Unable to receive data normally. Is my usage correct?
p
Prashant Shahi
09/06/2023, 6:28 PMhow are you sending data to the signoz otel-collector?
t
tao fei
09/07/2023, 12:29 AMThe data I sent through opentelemetry-javaagent.jar
tao fei
09/07/2023, 12:33 AMBut Signoz deployed using Docker Standalone can receive
p
Prashant Shahi
09/08/2023, 2:17 PMDo you have signoz installed using Docker or Kubernetes?
Also, does the endpoint
<http://192.169.2.253:4317>t
tao fei
09/09/2023, 12:53 AMimage.png
tao fei
09/09/2023, 12:55 AMMy endpoint configuration is correct.
tao fei
09/09/2023, 12:57 AMAs shown in the above figure, is port 4317 bound to signoz-server-otel-collector-5b5cfcc785-xzx8w?
tao fei
09/09/2023, 8:41 AMI have installed using Docker Standalone and can now receive it normally.
p
Prashant Shahi
09/09/2023, 6:42 PMWith Docker Standalone, the OTLP ports (4317, 4318) would be exposed in the host machine.
In case of K8s, those ports will not be exposed by default.
If your instrumentation applications are running in the same cluster, you would need to use NodePort or LoadBalancer (if bare metal k8s cluster - you can use MetalLB).