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.