How to configure Otel with X-ray exporter for quarkus application

[s9r-5]

I am trying to configure this but not able to :
I am able to see node on x-ray portal but not any trace

My config:

apiVersion: opentelemetry.io/v1alpha1
kind: OpenTelemetryCollector
metadata:
name: sidecar-oms-otel
spec:
image: otel/opentelemetry-collector-contrib:latest
mode: sidecar
config: |
receivers:
otlp:
protocols:
grpc:
http:
awsxray:
endpoint: 0.0.0.0:2000
transport: udp
exporters:
jaeger:
endpoint: "jaeger-service.jaeger-adot-collector.svc.cluster.local:14250"
tls:
insecure: true
awsxray:
region: "us-east-2"
extensions:
awsproxy:
service:
extensions: [awsproxy]
pipelines:
traces:
receivers: [awsxray, otlp]
exporters: [awsxray, jaeger]

Logs :

2023-05-03T16:53:01.511Z info service/telemetry.go:92 Setting up own telemetry...
22
2023-05-03T16:53:01.511Z info service/telemetry.go:149 Serving Prometheus metrics {"address": ":8888", "level": "Basic"}
21
2023-05-03T16:53:01.511Z info extension/extension.go:148 Stability level of component is undefined {"kind": "extension", "name": "awsproxy"}
20
2023-05-03T16:53:01.512Z info exporter@v0.76.1/exporter.go:286 Deprecated component. Will be removed in future releases. {"kind": "exporter", "data_type": "traces", "name": "jaeger"}
19
2023-05-03T16:53:01.512Z warn jaegerexporter@v0.76.3/factory.go:57 jaeger exporter is deprecated and will be removed in July 2023. See open-telemetry/opentelemetry-specification#2858 for more details. {"kind": "exporter", "data_type": "traces", "name": "jaeger"}
18
2023-05-03T16:53:01.512Z info awsxrayreceiver@v0.76.3/receiver.go:60 Going to listen on endpoint for X-Ray segments {"kind": "receiver", "name": "awsxray", "data_type": "traces", "udp": "0.0.0.0:2000"}
17
2023-05-03T16:53:01.512Z info udppoller/poller.go:106 Listening on endpoint for X-Ray segments {"kind": "receiver", "name": "awsxray", "data_type": "traces", "udp": "0.0.0.0:2000"}
16
2023-05-03T16:53:01.512Z info awsxrayreceiver@v0.76.3/receiver.go:71 Listening on endpoint for X-Ray segments {"kind": "receiver", "name": "awsxray", "data_type": "traces", "udp": "0.0.0.0:2000"}
15
2023-05-03T16:53:01.512Z info exporter@v0.76.1/exporter.go:286 Development component. May change in the future. {"kind": "exporter", "data_type": "logs", "name": "logging"}
14
2023-05-03T16:53:01.512Z warn loggingexporter@v0.76.1/factory.go:109 'loglevel' option is deprecated in favor of 'verbosity'. Set 'verbosity' to equivalent value to preserve behavior. {"kind": "exporter", "data_type": "logs", "name": "logging", "loglevel": "debug", "equivalent verbosity level": "Detailed"}
13
2023-05-03T16:53:01.513Z info service/service.go:129 Starting otelcol-contrib... {"Version": "0.76.3", "NumCPU": 8}
12
2023-05-03T16:53:01.513Z info extensions/extensions.go:41 Starting extensions...
11
2023-05-03T16:53:01.513Z info extensions/extensions.go:44 Extension is starting... {"kind": "extension", "name": "awsproxy"}
10
2023-05-03T16:53:01.513Z info awsproxy@v0.76.3/extension.go:43 X-Ray proxy server started on 0.0.0.0:2000 {"kind": "extension", "name": "awsproxy"}
9
2023-05-03T16:53:01.513Z info extensions/extensions.go:48 Extension started. {"kind": "extension", "name": "awsproxy"}
8
2023-05-03T16:53:01.513Z warn internal/warning.go:51 Using the 0.0.0.0 address exposes this server to every network interface, which may facilitate Denial of Service attacks {"kind": "receiver", "name": "otlp", "data_type": "logs", "documentation": "https://github.com/open-telemetry/opentelemetry-collector/blob/main/docs/security-best-practices.md#safeguards-against-denial-of-service-attacks"}
7
2023-05-03T16:53:01.513Z info otlpreceiver@v0.76.1/otlp.go:94 Starting GRPC server {"kind": "receiver", "name": "otlp", "data_type": "logs", "endpoint": "0.0.0.0:4317"}
6
2023-05-03T16:53:01.513Z warn internal/warning.go:51 Using the 0.0.0.0 address exposes this server to every network interface, which may facilitate Denial of Service attacks {"kind": "receiver", "name": "otlp", "data_type": "logs", "documentation": "https://github.com/open-telemetry/opentelemetry-collector/blob/main/docs/security-best-practices.md#safeguards-against-denial-of-service-attacks"}
5
2023-05-03T16:53:01.513Z info otlpreceiver@v0.76.1/otlp.go:112 Starting HTTP server {"kind": "receiver", "name": "otlp", "data_type": "logs", "endpoint": "0.0.0.0:4318"}
4
2023-05-03T16:53:01.514Z info jaegerexporter@v0.76.3/exporter.go:184 State of the connection with the Jaeger Collector backend {"kind": "exporter", "data_type": "traces", "name": "jaeger", "state": "CONNECTING"}
3
2023-05-03T16:53:01.514Z info awsxrayreceiver@v0.76.3/receiver.go:105 X-Ray TCP proxy server started {"kind": "receiver", "name": "awsxray", "data_type": "traces"}
2
2023-05-03T16:53:01.514Z info service/service.go:146 Everything is ready. Begin running and processing data.
1
2023-05-03T16:53:02.514Z info jaegerexporter@v0.76.3/exporter.go:184 State of the connection with the Jaeger Collector backend {"kind": "exporter", "data_type": "traces", "name": "jaeger", "state": "READY"}