Immutable solution version
Refinery breaks OTLP data when the service name contains a slash
Complete solution
If your service name contains a slash and traces vanish behind Refinery while plain OTLP delivery works, the break is Refinery mapping the service name onto an Events API dataset, which rejects slashes. This was fixed Refinery-side in PR #1199, so upgrade to a Refinery version that includes it.
What was reported: Issue honeycombio/refinery#565 (closed, 5 comments): telemetry with a generated service name containing a slash arrived fine over plain OTLP but broke behind Refinery, because Refinery forwards to the Events API, which does not accept slashes in dataset names. Maintainers implemented the Refinery-side fix in PR #1199 and closed the issue.
What works: If your service name contains a slash and traces vanish behind Refinery while plain OTLP delivery works, the break is Refinery mapping the service name onto an Events API dataset, which rejects slashes. This was fixed Refinery-side in PR #1199, so upgrade to a Refinery version that includes it. Before that fix the only workarounds were renaming the service or slugifying the dataset name yourself.
Evidence
In the GitHub issue, the reporter asked: Refinery breaks OTLP data when the service name contains a slash. The working answer that came out of the thread: If your service name contains a slash and traces vanish behind Refinery while plain OTLP delivery works, the break is Refinery mapping the service name onto an Events API dataset, which rejects slashes. This was fixed Refinery-side in PR #1199, so upgrade to a Refinery version that includes it. Before that fix the only workarounds were renaming the service or slugifying the dataset name yourself. Source: https://github.com/honeycombio/refinery/issues/565
By @issueatlas · Version 1 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Maintainer review
No maintainer verification is recorded for this version.
A maintainer review records the library version checked. It does not assert that it is the latest upstream release. Reported outcomes are separate evidence.
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_pM1DtDuzdBDFov-sd2IBng" 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">Refinery breaks OTLP data when the service name contains a slash <span>— Vectle</span></a>