#support

Troubleshooting Script Testing of Ports Discussion

TLDR Pocho verified the troubleshooting script only tests grpc and not http, and suggested an option to test both. Ankit welcomed a PR for this improvement.

2mo

Join the chat

Oct 02, 2023 (2 months ago)

Photo of md5-227a186751065f5b4cb212751ba7caac

Pocho

02:24 PM

Hi team, for the troubleshooting script, is it only binded to port 4317? seems when we run ./troubleshoot checkEndpoint --endpoint ourloadbalancer-name.elb.us-east-1.amazonaws.com:4317 it comes back fine but when appended with port 4318 it fails even though the lb is set to accept both and service is listening on both ports in cluster.

Seems the troubleshooting script is only testing the grpc port and not htttp? Can someone confirm this?

04:03

Pocho

04:03 PM

Ok I was able confirm that the troubleshooting tool is set to only test grpc and NOT http Looking at the commit here https://github.com/SigNoz/troubleshoot/blob/main/checkEndpoint/checkEndpoint.go one can see it’s set to only spit out a grpc troubleshooter.

package checkEndpoint

import (
    "context"
    "fmt"
    "time"

    ""
    ""
    ""
    ""
    ""
)

I was able to modify the checkEndpoint.go for my needs to test port 4318 successfully. I think it would make sense to have the option of testing both ports via this tool. Is this something the team would want a PR for or not worth it? Thanks!

Oct 03, 2023 (2 months ago)

Photo of md5-dbe7088320fe1d922707613e02f3420d

Ankit

03:57 AM

a PR would be welcomed Pocho

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

Troubleshooting OpenTelemetry Python App Instrumentation in Signoz

Musa had issues with Python app instrumentation in Signoz. After some troubleshooting with Srikanth, they managed to resolve the problem by defining the OTLP endpoint and service name.

4mo

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

Log Monitoring Connection Error in Signoz

Utkarsh encountered a connection error while adding log monitoring using Signoz. nitya-signoz identified the incorrect otlp exporter port and suggested using 4317.

9mo