opentelemetry-collector
opentelemetry-collector copied to clipboard
Published
20 hours ago •
open-telemetry
open-telemetry
internal telemetry (logs) are not using https
trafficstars
Component(s)
No response
What happened?
Describe the bug
Collector is using http rather than https when sending logs and it is causing server to reject the request.
Steps to reproduce
What did you expect to see?
Logs and metrics sent to signoz.
What did you see instead?
I see metrics but not the logs. I see errors in console when collector try to send logs.
Collector version
0.135.0
Environment information
Environment
OS: (e.g., "Ubuntu 20.04") Compiler(if manually compiled): (e.g., "go 14.2")
Debian 13, Using docker.
OpenTelemetry Collector configuration
receivers:
otlp: # the OTLP receiver the app is sending traces to
protocols:
http:
endpoint: 0.0.0.0:4318
processors:
memory_limiter:
check_interval: 1s
limit_mib: 500
spike_limit_mib: 128
batch:
send_batch_size: 10000
timeout: 10s
exporters:
debug:
verbosity: detailed
otlphttp/traceloop: # Only otelhttp/ worked with traceloop
endpoint: "https://api.traceloop.com"
tls:
insecure: false
headers:
"Authorization": "Bearer ${env:TRACELOOP_API_KEY}"
otlp/signoz: # otlp/ works out of box with signoz
endpoint: "https://ingest.in.signoz.cloud:443"
tls:
insecure: false
headers:
"signoz-ingestion-key": "${env:SIGNOZ_ACCESS_TOKEN}"
service:
telemetry: # internel telemetry
logs:
processors:
- batch:
exporter:
otlp:
protocol: http/protobuf
endpoint: https://ingest.in.signoz.cloud:443
headers:
"signoz-ingestion-key": "${env:SIGNOZ_ACCESS_TOKEN}"
metrics:
readers:
- periodic:
exporter:
otlp:
protocol: http/protobuf
endpoint: https://ingest.in.signoz.cloud:443
headers:
"signoz-ingestion-key": "${env:SIGNOZ_ACCESS_TOKEN}"
pipelines:
traces:
receivers: [otlp]
processors: [memory_limiter, batch]
exporters: [otlphttp/traceloop, otlp/signoz]
Log output
otel-collector-1 | 2025-09-14T07:52:41.073Z info [email protected]/service.go:262 Shutdown complete. {"resource": {"service.instance.id": "d3846fe9-2078-48e3-aa19-96b59593a3f3", "service.name": "otelcol-contrib", "service.version": "0.135.0"}}
otel-collector-1 | Error: failed to shutdown service after error: failed to shutdown telemetry providers: failed to shutdown SDK: failed to send logs to http://ingest.in.signoz.cloud:443/v1/logs: 400 Bad Request (body: <html>
otel-collector-1 | <head><title>400 The plain HTTP request was sent to HTTPS port</title></head>
otel-collector-1 | <body>
otel-collector-1 | <center><h1>400 Bad Request</h1></center>
otel-collector-1 | <center>The plain HTTP request was sent to HTTPS port</center>
otel-collector-1 | <hr><center>nginx</center>
otel-collector-1 | </body>
otel-collector-1 | </html>)
otel-collector-1 | 2025/09/14 07:52:41 collector server run finished with error: failed to shutdown service after error: failed to shutdown telemetry providers: failed to shutdown SDK: failed to send logs to http://ingest.in.signoz.cloud:443/v1/logs: 400 Bad Request (body: <html>
otel-collector-1 | <head><title>400 The plain HTTP request was sent to HTTPS port</title></head>
otel-collector-1 | <body>
otel-collector-1 | <center><h1>400 Bad Request</h1></center>
otel-collector-1 | <center>The plain HTTP request was sent to HTTPS port</center>
otel-collector-1 | <hr><center>nginx</center>
otel-collector-1 | </body>
otel-collector-1 | </html>)
Additional context
No response
Tip
React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.
