#general

Troubleshooting SigNoz Ports and Windows Compatibility

TLDR Ramya faced issues with SigNoz ports and internal Java errors. Yash rV advised checking port numbers and trying on a Linux machine, as SigNoz has limited support on Windows.

4mo

Join the chat

Jul 25, 2023 (4 months ago)

Photo of md5-080141ed2f7a4ebfb0eb0761cd5d70f2

Ramya

10:09 AM

Yash rV do u have any idea about this?

Photo of md5-cf77c5ac54f90e38660b2ee9331d5457

Yash rV

10:59 AM

1. By default, SigNoz listens on ports 4317 and 4318 for incoming telemetry data, instead, it seems that you are exporting data to port 3301 which is used for frontend. Refer here for instrumenting your spring boot application. You can also see the sample app.
2. It is to be noticed from the message that there are some internal errors within your Java application. To resolve this, please ensure that you launch the app correctly and address any potential issues.

Ramya

11:25 AM

4317/4318 is also not working

11:25

Ramya

11:25 AM

Yash rV

Yash rV

11:34 AM

Are you on a Windows machine? If so, I suggest trying the same on a Linux machine or even WSL, because as of now SigNoz is not fully supported on Windows.

Ramya

11:34 AM

yes

11:35

Ramya

11:35 AM

I want to first verify in local

11:35

Ramya

11:35 AM

then will try to implement in AWS

Yash rV

11:39 AM

Ok. I would suggest you try the same on WSL or on any other Linux machine in this case. Because as of now SigNoz is not fully supported on Windows.

Ramya

11:50 AM

Yash rV cmd will not work?

SigNoz Community

Built with ClickHouse as datastore, SigNoz is an open-source APM to help you find issues in your deployed applications & solve them quickly | Knowledge Base powered by Struct.AI

Indexed 1023 threads (61% resolved)

Join Our Community

Similar Threads

SigNoz Production Feedback and Improvement Suggestions

Users shared their SigNoz experiences and feedback. Issues mentioned include memory consumption, UI/UX improvements, connection difficulties, and automation limitations.

9mo

Troubleshooting SigNoz Auto-Instrumentation Configuration

igor is having trouble configuring auto-instrumentation for Java applications using SigNoz, with traces not appearing in the SigNoz UI. Prashant advises to check logs of the otel sidecar, use service name for endpoint, verify supported libraries, and test with telemetrygen. However, the issue still persists.

8mo

Configuring OTel Collector to Export Data to SigNoz

James asked how to configure the otel collector to send data to SigNoz. Ankit suggested using the otlp exporter in the collector configuration. James found that SigNoz uses its own otel collector and adjusted the port bindings accordingly.

5mo

SigNoz Install Script Errors

Nishant encountered errors with the install.sh script. Prashant suggested using `bash install.sh` or `./install.sh` instead of `sh`.

7mo

Troubleshooting SigNoz Monitoring for AWS EC2 Docker-Compose Application

dipak has problems with SigNoz integration to monitor containers in an AWS EC2 Docker-Compose application. Prashant suggests updating the dashboard and using different guides for log collection, metrics collection and application instrumentation. Issues are still unresolved.

3mo