This message was deleted.
# supports
Slackbot
06/30/2022, 2:33 PMThis message was deleted.
m
manohar mirle
06/30/2022, 2:51 PMTried another approach but no luck:
otlphttp:
endpoint: "x.x.x.x:8081/deeptrace"
tls:
insecure: false
cert_file: "/etc/cert.pem"
key_file: "/etc/key.pem"
insecure_skip_verify: true
traces:
receivers: [otlp]
processors: [signozspanmetrics/prometheus,batch]
exporters: [otlphttp,clickhouse]
Error: cannot build exporters: error creating otlphttp exporter: endpoint must be a valid URL
otel-collector_1 | 2022/06/30 144733 collector server run finished with error: cannot build exporters: error creating otlphttp exporter: endpoint must be a valid URL
manohar mirle
06/30/2022, 3:00 PMAnother try with the below configs:
otlphttp:
endpoint: "https://x.x.x.x:8081/deeptrace"
pipelines:
traces:
receivers: [otlp]
processors: [signozspanmetrics/prometheus,batch]
exporters: [otlphttp,clickhouse]
"failed to make an HTTP request: Post \"https://x.x.x.x:8081/deeptrace/v1/traces\": dial tcp x.x.x.x8081 connect: connection refused"
p
Pranay
06/30/2022, 4:45 PM
@Prashant Shahi any insights on this?
p
Prashant Shahi
06/30/2022, 8:31 PMHey @manohar mirle !
Couple of questions:
• why nginx in between two collectors?
• Does https://x.x.x.x:8081/deeptrace/v1/traces resolve to
https://<OtelCollector-Endpoint>:4318/v1/tracem
manohar mirle
07/01/2022, 4:32 AMHi @Prashant Shahi,
nginx is for converting https to http and delegating the data to different collectors based the type of data.
Will check the second point and update you. But, the there is a issue before reaching that stage
manohar mirle
07/01/2022, 6:44 AM@Prashant Shahi
Geeting below error in the collector which is exporting the traces:
manohar mirle
07/01/2022, 6:44 AM09Z info exporterhelper/queued_retry.go:215 Exporting failed. Will retry the request after interval. {"kind": "exporter", "name": "otlphttp", "error": "error exporting items, request to https://abc.com:443/deeptrace/v1/traces responded with HTTP Status Code 502", "interval": "23.541514772s"}
manohar mirle
07/01/2022, 6:44 AMIn the receiver collector it is throwing below error :
manohar mirle
07/01/2022, 6:46 AM2022-07-01T115804.350+0530 warn zapgrpc/zapgrpc.go:191 [core] grpc: Server.Serve failed to create ServerTransport: connection error: desc = "transport: http2Server.HandleStreams received bogus greeting from client: \"POST /deeptrace/v1/trace\"" {"grpc_log": true}
p
Prashant Shahi
07/01/2022, 7:52 AMI don't think you will need to include
https443tls.insecurefalsePrashant Shahi
07/01/2022, 7:53 AMAlso, would it be possible for you to use subdomain
<http://deeptrace.abc.com|deeptrace.abc.com><http://abc.com/deeptrace|abc.com/deeptrace>Prashant Shahi
07/01/2022, 7:58 AMI tested with nginx with SSL certificates pointed to OTLP http endpoint, I was able use subdomain but custom basepath didn't work for me.
m
manohar mirle
07/01/2022, 8:48 AMTried it without giving https & 443. THis is what I am getting:
Exporting failed. Will retry the request after interval. {"kind": "exporter", "name": "otlphttp", "error": "failed to make an HTTP request: Post \"abc.com/deeptrace/v1/traces\": unsupported protocol scheme \"\"", "interval": "6.278612655s"}
Exporting failed. The error is not retryable. Dropping data. {"kind": "exporter", "name": "otlp", "error": "Permanent error: rpc error: code = Unknown desc = transport: received unexpected content-type \"text/html\"", "dropped_items": 6}
manohar mirle
07/01/2022, 8:50 AMNeed to check the alternative option of creating subdomain
p
Prashant Shahi
07/01/2022, 8:53 AMin otelconfig, can you try passing
<http://abc.com/deeptrace|abc.com/deeptrace>Prashant Shahi
07/01/2022, 8:54 AMwithout
v1/tracesm
manohar mirle
07/01/2022, 10:21 AMInfact we are passing like that only
abc.com/deeptrace
179 Views