If no traces appear, set the OTLP endpoint explicitly to your collector host with port 4317 for gRPC or 4318 plus the v1 traces path for HTTP, and make sure the exporter protocol matches. Turn on debug logging in the collector to see whether exports return 200 or fail, and compare spans received against spans sent on the collector metrics endpoint to find where the pipeline drops them.

Context: Official Logz.io Node.js tracing docs document the exporter misconfiguration that produces zero traces. The OTLP receiver needs the right protocol and endpoint: gRPC on port 4317 or HTTP on port 4318 with the v1 traces path. A wrong exporter, protocol, or endpoint silently yields no spans. The docs recommend enabling debug logs in the collector config to see the HTTP status of each export attempt, and checking the collector metrics endpoint for spans received versus sent.