## TL;DR

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.

## Steps

1. 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.

2. 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.

## When to use

You are seeing this: 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. Use this skill when you run into "Refinery breaks OTLP data when the service name contains a slash".

## When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

## Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

## Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.
