Hey @Srikanth Chekuri, I am trying to auto-instrument a python app in a daemon set mode , I am following the instructions on https://signoz.io/docs/tutorial/opentelemetry-operator-usage/#across-the-nodes---daemonset

apiVersion: opentelemetry.io/v1alpha1
kind: Instrumentation
metadata:
  name: my-instrumentation
spec:
  exporter:
    endpoint: <http://my-release-signoz-otel-collector.platform.svc.cluster.local:4317>
  propagators:
    - tracecontext
    - baggage
    - b3
  sampler:
    type: parentbased_traceidratio
    argument: "0.25"
  java:
    image: ghcr.io/open-telemetry/opentelemetry-operator/autoinstrumentation-java:latest
  nodejs:
    image: ghcr.io/open-telemetry/opentelemetry-operator/autoinstrumentation-nodejs:latest
  python:
    image: ghcr.io/open-telemetry/opentelemetry-operator/autoinstrumentation-python:latest
  dotnet:
    image: ghcr.io/open-telemetry/opentelemetry-operator/autoinstrumentation-dotnet:latest

kubectl apply -f - <<EOF
apiVersion: opentelemetry.io/v1alpha1
kind: OpenTelemetryCollector
metadata:
  name: simplest
spec:
  mode: daemonset
  config: |
    receivers:
      otlp:
        protocols:
          grpc:
          http:
    processors:
      batch:
    exporters:
      logging:
    service:
      pipelines:
        traces:
          receivers: [otlp]
          processors: [batch]
          exporters: [logging]
EOF

It is giving me error

requests.exceptions.ConnectionError: ('Connection aborted.', ConnectionResetError(104, 'Connection reset by peer'))

Can you please help me to resolve this or what can be the cause of this

First thing, please do not send the message to the whole channel when there is no need. What's the point of doing it? Please change the endpoint from

<http://my-release-signoz-otel-collector.platform.svc.cluster.local:4317>

to

<http://my-release-signoz-otel-collector.platform.svc.cluster.local:4318>

and try again.

Sure will not sent to channel, my bad, and thanks will try again with the above modification