Sudhansu Bandha
09/09/2023, 10:49 AMapiVersion: <http://opentelemetry.io/v1alpha1|opentelemetry.io/v1alpha1>
kind: OpenTelemetryCollector
metadata:
name: sidecar-collector
spec:
mode: sidecar
config: |
receivers:
otlp:
protocols:
http:
grpc:
processors:
batch:
exporters:
logging:
otlp:
endpoint: <http://signals-collector.qualix.ai:4317>
tls:
insecure: true
service:
pipelines:
traces:
receivers: [otlp]
processors: [batch]
exporters: [logging, otlp]
metrics:
receivers: [otlp]
processors: [batch]
exporters: [logging, otlp]
the mentioned configuration is used to send telemetry data to signoz otel collector where signoz setup is performed at a different K8s cluster . I need to find the reason for which this setup is failing. Currently unable to figure out why this is failing. Implemented the spring petclininc app for sidecar following the documentation.
If I try to send telementry data using the go command for telemetrygen along with the mentioned exporter DNS for signoz otel collector it is working
telemetrygen traces --traces 1 --otlp-endpoint <http://signals-collector.qualix.ai:4317|signals-collector.qualix.ai:4317> --otlp-insecure
Prashant Shahi
09/09/2023, 6:33 PMotlp
exporter configuration?
endpoint: <http://signals-collector.qualix.ai:4317|signals-collector.qualix.ai:4317>
tls:
insecure: true
Sudhansu Bandha
09/11/2023, 1:17 AMapiVersion: <http://opentelemetry.io/v1alpha1|opentelemetry.io/v1alpha1>
kind: OpenTelemetryCollector
metadata:
name: sidecar-collector
spec:
mode: sidecar
config: |
receivers:
otlp:
protocols:
http:
grpc:
processors:
batch:
exporters:
logging:
otlp:
endpoint: <http://signals-collector.qualix.ai:4317|signals-collector.qualix.ai:4317>
tls:
insecure: true
service:
pipelines:
traces:
receivers: [otlp]
processors: [batch]
exporters: [logging, otlp]
metrics:
receivers: [otlp]
processors: [batch]
exporters: [logging, otlp]
Prashant Shahi
09/11/2023, 8:56 AM