opentelemetry.io icon indicating copy to clipboard operation
opentelemetry.io copied to clipboard

a blog post about getting started with otel and rust

Open NavehMevorach opened this issue 2 years ago • 7 comments

Hi guys, Our team created a great blog post about getting started with Otel and Rust. We think its a great blog post (its also was featured in the rust community)

As usual - we removed any refrence to Aspecto and used Jaeger for the visualization.

I tried my best to follow all the notes you guys gave us in our prevous blog post so I hope this time there wont be many changes =)

NavehMevorach avatar Sep 21 '22 12:09 NavehMevorach

@NavehMevorach:

  • please make sure that the build does not fail.
  • please have a look at the comment from @djc

svrnm avatar Sep 28 '22 15:09 svrnm

@NavehMevorach can you make sure that your code is building, then I can review your blog post once again, thanks!

svrnm avatar Oct 05 '22 09:10 svrnm

Agree with @svrnm feedback: in making our documentation better to assist new users to OTel, Getting Started content is very important. I've no objections to the blog itself, but see adding the content to the docs as more important than putting out a blog. Blog content is harder to find over time, and can seem to be out of date. By putting it in the documentation itself, it appears authoritative and up to date. @NavehMevorach what do you think? If you're onboard, we could create an issue to add the Rust Getting Started content to the documentation, which could use some of the information from the blog.

melbgirl avatar Oct 07 '22 19:10 melbgirl

Agree with @svrnm feedback: in making our documentation better to assist new users to OTel, Getting Started content is very important. I've no objections to the blog itself, but see adding the content to the docs as more important than putting out a blog. Blog content is harder to find over time, and can seem to be out of date. By putting it in the documentation itself, it appears authoritative and up to date. @NavehMevorach what do you think? If you're onboard, we could create an issue to add the Rust Getting Started content to the documentation, which could use some of the information from the blog.

Fine by us.

NavehMevorach avatar Oct 11 '22 18:10 NavehMevorach

@NavehMevorach can you make sure that your code is building, then I can review your blog post once again, thanks!

Fixed

NavehMevorach avatar Oct 11 '22 18:10 NavehMevorach

Some more comments, in general, please be cautious that you use the right terms & definitions used by the community (auto instrumentation, instrumentation library, event, etc.)

cc: @open-telemetry/rust-approvers please give this a look, I can only validate the text, not the code, I also don't know enough about the specifics of the rust implementation.

svrnm avatar Oct 13 '22 09:10 svrnm

@svrnm is there a style guide for the blog I wasn't able to find a reference.

We can run a prettier over the blog post before it's going out, but beyond that there are no strict rules

svrnm avatar Oct 18 '22 07:10 svrnm

We can run a prettier over the blog post before it's going out,

Yes, let's run Prettier before this gets published.

chalin avatar Oct 28 '22 13:10 chalin

@NavehMevorach I know this is already taking a lot of time, but I am hopeful that we get this blog post in eventually, can you give the comments provided a look? TY

svrnm avatar Nov 23 '22 15:11 svrnm

@NavehMevorach any updates?

svrnm avatar Dec 12 '22 09:12 svrnm

Closing due to inactivity. If you'd like to get this on the blog, feel free to ping here or resubmit and we'll take another look.

cartermp avatar Dec 17 '22 00:12 cartermp