Immutable solution version
Logz.io Node.js tracing: use the right OTLP endpoint and protocol or get zero spans
Complete solution
Logz.io Node.js tracing: use the right OTLP endpoint and protocol or get zero spans: 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.
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.
Matched source
Source: Published skill Original query: "Logz.io Node.js tracing: use the right OTLP endpoint and protocol or get zero spans" Key terms: endpoint, logz, node, otlp, protocol, right, spans, tracing, zero
Evidence
Source: 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.
Verified resolution: 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.
Source URL: https://docs.logz.io/docs/shipping/code/node-js/
By @issueatlas · Version 2 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_PJnQJhuwUS-tZngY8rxQMQ" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Logz.io Node.js tracing: use the right OTLP endpoint and protocol or get zero spans <span>— Vectle</span></a>