https://signoz.io
Join Slack
This message was deleted.
# support
s
This message was deleted.
✅ 1
p
@주현태 can you share what you see on running this. https://signoz.io/docs/install/troubleshooting/
u
@Pranay This is the result of running with endpoint set to 172.17.0.1 and localhost. Docker containers are running.
p
got it. So your SigNoz otel collector is not accessible from your application. I think you need to check the address you have given - this grid may be helpful - https://signoz.io/docs/install/troubleshooting/#signoz-otel-collector-address-grid
p
Hey @주현태 👋 We don't officially support Windows yet. There is an open issue on the same. Do check out this comment on the opened issue, if it helps. https://github.com/SigNoz/signoz/issues/645#issuecomment-1027629006
This is the result of running with endpoint set to 172.17.0.1 and localhost.
The OtelCollector address grid does not include instruction for windows. Below command should do the equivalent to check if OtelCollector is accessible and accepting traces:
Copy code
docker run -it --network clickhouse-setup_default signoz/troubleshoot checkEndpoint --endpoint=otel-collector:4317
u
@Pranay @Prashant Shahi Thanks for your help. I solved the issue as shown in the attached image. It was a permission problem of the clickhouse's store data. So, I used the docker internal volume. Refer to the URL below. https://medium.com/@tina168wong/problem-of-mysql-volumes-in-docker-in-ubuntu-wsl2-5aed9ce10013 Thank you.🙏
p
Awesome, thanks a lot for sharing back @주현태
👏 1
🙏 1
12 Views
Open in Slack
PreviousNext
Powered by

SigNoz Community

SigNoz is an open-source APM. It helps developers monitor their applications & troubleshoot problems, an open-source alternative to DataDog, NewRelic, etc.

Powered by