Add blog entry about Jaeger OTLP and deprecation#1892
Conversation
|
Not a blog approver, but I think it's very clear and well-organized! I always appreciate these aspects of any written communication. |
cartermp
left a comment
There was a problem hiding this comment.
Looks good overall! Just some small questions.
| - Are you an OpenTelemetry user currently sending data to Jaeger? | ||
| - Are you using the Jaeger client exporters, or have you already made the switch | ||
| to OTLP? | ||
| - How painful will it be for you to migrate to native OTLP with Jaeger? |
There was a problem hiding this comment.
Not sure if this is worth putting in the blog post, but a fairly "obvious" action we should take is ensuring that every piece of docs that explains how to set up a jaeger exporter needs updating to show how to do it with OTLP. I would expect anyone's feedback to this question to be dependent on what the plan is for that.
There was a problem hiding this comment.
Yeah agreed. I hope this isn't too much cart before the horse, and I would expect that we could update the docs during the deprecation phase.
austinlparker
left a comment
There was a problem hiding this comment.
overall lgtm -- will this be cross-published onto the Jaeger blog?
chalin
left a comment
There was a problem hiding this comment.
See inline comments, thanks.
|
@breedx-splk do you have permissions to cross-post to the jaeger blog as well? |
Co-authored-by: Patrice Chalin <chalin@users.noreply.github.com>
Co-authored-by: Patrice Chalin <chalin@users.noreply.github.com>
Co-authored-by: Patrice Chalin <chalin@users.noreply.github.com>
Co-authored-by: Patrice Chalin <chalin@users.noreply.github.com>
@austinlparker @cartermp A really good idea. I've reached out to @yurishkuro on the spec issue to see if he can help with cross-posting. |
|
@breedx-splk sounds good to me. I am happy to merge as-is for now. Just a question of timing. |
|
I have a couple suggestions:
|
|
Ok, the survey is up and I've added links to it. I've also taken @yurishkuro's advice and spelled out exactly which exporters are to be deprecated and some high level descriptions of the user impact for each. |
Co-authored-by: Yuri Shkuro <yurishkuro@users.noreply.github.com>
this text occurs is in the readme twice. |
Oof, thanks, I think that was a merge/rebase fail. Fixing that up now. |
|
@breedx-splk if you want to repost this to Jaeger blog, we have two options:
|
Thanks @yurishkuro. I'm flexible -- but I don't currently have a Medium account, so if you're willing to do a copy/paste that would be awesome! ❤️ |
|
|
||
| We intend to **deprecate Jaeger exporters from OpenTelemetry** in the near | ||
| future, and are looking for your feedback to determine the length of the | ||
| depreation phase. The best way to provide feedback is by |
There was a problem hiding this comment.
typo: depreation -> deprecation
Thanks again for your help and support! 🤜🏻 🤛🏻 |
|
Looking forward to the survey results. Please post them in the PR. Do you have something in mind for how long you want to keep the survey open? 1-2w? |
|
@yurishkuro 2w seems good to me. |
Feedback welcome. Thanks!
Preview: https://deploy-preview-1892--opentelemetry.netlify.app/blog/2022/jaeger-native-otlp/