# Linkerd-jaeger with a alloy collector continously has InvalidContentType

**URL:** <https://linkerd.buoyant.io/t/linkerd-jaeger-with-a-alloy-collector-continously-has-invalidcontenttype/772>\
**Category:** Linkerd General Discussion\
**Tags:** tracing\
**Created:** [June 4, 2025, 12:20pm UTC](https://linkerd.buoyant.io/t/linkerd-jaeger-with-a-alloy-collector-continously-has-invalidcontenttype/772 "2025-06-04T12:20:29Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![me](https://avatars.discourse-cdn.com/v4/letter/m/e99b99/32.png) [@me](https://linkerd.buoyant.io/u/me)\
**Post date:** [June 4, 2025, 12:20pm UTC](https://linkerd.buoyant.io/t/linkerd-jaeger-with-a-alloy-collector-continously-has-invalidcontenttype/772/1 "2025-06-04T12:20:29Z")

</div>

I’m trying to get linkerd-jaeger running with opentelemetry and alloy as an collector. Currently I didn’t get it to work. There is an error mentioning InvalidContentType when the linkerd-proxy is trying to deliver the informations to the otel (grpc) endpoint on alloy. The deployed traefik is doing it and I get the information but not linkerd.  
As linkerd-jaeger is now also using opentelemetry I would expect that’s doing the job. But as of now I haven’t got it working.  
Has somebody already done that?  
m.

---

<div class="post-metadata">

**Author:** ![Flynn](https://yyz1.discourse-cdn.com/flex029/user_avatar/linkerd.buoyant.io/flynn/32/41_2.png) [@Flynn](https://linkerd.buoyant.io/u/Flynn)\
**Post date:** [June 5, 2025, 3:22pm UTC](https://linkerd.buoyant.io/t/linkerd-jaeger-with-a-alloy-collector-continously-has-invalidcontenttype/772/2 "2025-06-05T15:22:47Z")

</div>

What version of Linkerd are you running? and can you share your linkerd-jaeger configuration? Thanks!