Adharsh

> [@adharshctr](https://github.com/adharshctr) can you help check the issue? I think we did not test the latest release yet. Thanks Sure

Hi @mmphego I recreated the same environment and ran the first application after a minor refactor. The traces are now visible in Instana. When you initialize OpenTelemetry first (or manually...

> [@adharshctr](https://github.com/adharshctr) can you highlight the changes you have made? Thanks Initialized the traceloop on the Top.

@mmphego Can you try setting **OTEL_EXPORTER_OTLP_INSECURE=true** to resolve SSL issue ? Also remove **insecure** from OTLPSpanExporter.

@mmphego I assume traces work fine with gRPC, and the issue is only with HTTP?

@mmphego I had tested the application that you had shared. It is working from my end and getting the traces. Could you check whether the port is reachable? curl -v...

Could you please update the script as shown below and then try running the application once? ``` os.environ["TRACELOOP_BASE_URL"] = "http://instana-agent.instana-agent.svc.cluster.local:4318" Traceloop.init(app_name="llm-tracing", telemetry_enabled=False) ```

@mmphego I also tested the script below and was able to get the traces. The change I made was updating the ENDPOINT to "http://instana-agent.instana-agent.svc.cluster.local:4318" ``` cat traceloop_test.py #!/usr/bin/env python3 #...

Hi @mmphego If you send a OpenTelemetry response body (**with fixed traceId and spanId**) to an endpoint, the receiver or exporter may overwrite those IDs with new ones because OpenTelemetry...

Hi @mmphego Are you able to view the traces after changing the filter to Service Name, Call Name, or Span Attributes?