Troubleshooting Docker File Configuration for Metrics Traces
TLDR Vibhav was trying to pass config in a Docker file and encountered issues with metrics traces not getting pushed. Prashant offered reference, and Srikanth identified potential grpc exporter issue.
Jul 18, 2023 (2 months ago)
Vibhav
08:30 AM
Prashant
09:49 AMhttps://github.com/SigNoz/sample-flask-app/blob/master/Dockerfile
Vibhav
10:26 AMVibhav
10:26 AM{"name": "/","context": {"trace_id": "0x1070ede6e4d6c97afce24d2492ceef46","span_id": "0x40b2fe5abc5fc783","trace_state": "[]"},"kind": "SpanKind.SERVER","parent_id": null,"start_time": "2023-07-18T10:22:44.545395Z","end_time": "2023-07-18T10:22:44.547657Z","status": {"status_code": "UNSET"},"attributes": {"http.method": "GET","http.server_name": "::","http.scheme": "http","net.host.port": 9080,"http.host": "localhost:9080","http.target": "/","net.peer.ip": "::ffff:127.0.0.1","http.user_agent": "curl/7.64.0","net.peer.port": 49024,"http.flavor": "1.1","http.route": "/","http.status_code": 200},Vibhav
10:26 AMVibhav
10:29 AMWARNING:opentelemetry.exporter.otlp.proto.grpc.exporter:Transient error StatusCode.UNAVAILABLE encountered while exporting metrics to localhost:4317, retrying in 2s.
WARNING:opentelemetry.exporter.otlp.proto.grpc.exporter:Transient error StatusCode.UNAVAILABLE encountered while exporting metrics to localhost:4317, retrying in 4s.
Vibhav
12:11 PMsend: b'POST /v1/metrics HTTP/1.1\r\nHost: signoz-otlp:4318\r\nUser-Agent: python-requests/2.31.0\r\nAccept-Encoding: gzip, deflate\r\nAccept: /\r\nConnection: keep-alive\r\nContent-Type: application/x-protobuf\r\nContent-Length: 183\r\n\r\n'
send: b'\n\xb4\x01\n\xb1\x01\n"\n\x16telemetry.sdk.language\x12\x08\n\x06python\n%\n\x12telemetry.sdk.name\x12\x0f\n\ropentelemetry\n!\n\x15telemetry.sdk.version\x12\x08\n\x061.19.0\n\x1d\n\x0cservice.name\x12\r\n\x0bproductpage\n"\n\x16telemetry.auto.version\x12\x08\n\x060.40b0'
reply: 'HTTP/1.1 200 OK\r\n'
header: Content-Type: application/x-protobuf
header: Date: Tue, 18 Jul 2023 12:08:09 GMT
header: Content-Length: 2
DEBUG:urllib3.connectionpool:http://signoz-otlp:4318 "POST /v1/metrics HTTP/1.1" 200 2. Getting 200 reponse but unable to see the app in the backend
Prashant
03:37 PMJul 19, 2023 (2 months ago)
Srikanth
01:02 AM
SigNoz Community
Indexed 825 threads (61% resolved)
Similar Threads
SigNoz Instrumentation Error in GCP/GKE with Python and FastAPI
Andre faced an error while instrumenting their app service with SigNoz. Srikanth identified the incorrect config and suggested the correct endpoint, resolving the issue.
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.
Signoz Deployment Error: Unsupported Metric Type
Einav is having trouble with a signoz deployment, receiving an error regarding unsupported metric types. Srikanth suggests they may be encountering a known error and provides a link for reference.
Headers in Monitoring HTTP Endpoints & Otel-Collector Error
Rohit asks about providing headers in monitoring HTTP endpoints and reports errors in otel-collector logs. Srikanth mentions headers are unsupported and requires more investigation for errors.
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.
1