Create an exporter configuration guide for Jaeger

[austinlparker]

We need a quick start guide for configuring traces to be sent to the Jaeger exporter, which should also include setting up Jaeger (locally, at least?). Basically the idea is "here's what you need to do in order to run Jaeger so you can see traces" as a starting point.

[Bhargavamacha]

Can I take this up? I have done it successfully locally.

[austinlparker]

Sure!

[Bhargavamacha]

I am planning on using opentelemetry-js' one of the examples to send data to Jaeger. Would that suffice?

[austinlparker]

That's fine for a start, yeah. We can add other languages to it after the initial work is done.

[Bhargavamacha]

I have created a document explaining how to get Jaeger up and running.
https://docs.google.com/document/d/1On-NA39ra9c6EO8AuBC-Zc0NfUSBjKgnm528drvqp3E/edit?usp=sharing
Any suggestions on which way I should go right now?

[austinlparker]

It'll need to be in markdown for us to use it on the site. I think it will be most useful if you could cover how to configure the opentelemetry exporter to Jaeger itself, and discuss any configuration options and what they do.

[Bhargavamacha]

Cool, I'll do that

[Bhargavamacha]

I made a rough draft of the Quickstart:
https://github.com/Bhargavamacha/jaegerforot/blob/master/Exporter%20configuration%20guide%20for%20Jaeger.md
Let me know if there are any edits

[mtwo]

Looks great! Can you create a PR to put it into the website repo? I'll add comments there

[ffe4]

@Bhargavamacha are there any updates on this issue or #45 ?

[Bhargavamacha]

The issue has been solved, it was merged to the master branch. #119

[ffe4]

@Bhargavamacha same with #45 ?

[Bhargavamacha]

I haven't opened a PR for it yet, will do it.

[austinlparker]

#119 only added guides for JavaScript. IMO, it'd be nice if there was a 'generic' landing page for Jaeger/Zipkin configs that had instructions for each language independently.

[Bhargavamacha]

Yeah, I think that's a good idea. Maybe a page saying integrations with all the integrations and options to choose the language for the specific documentation? I haven't been active for a few months, so I am not entirely sure if it's in the works or is already present.

[austinlparker]

There's a bit of a longer-term plan for this fall to rework the docs page entirely, where this would be a good fit.

[ffe4]

@austinlparker So, do we want a page with generic text for all languages and boxes with code where you can choose a tab for the specific language you are interested in?

[Bhargavamacha]

There's a bit of a longer-term plan for this fall to rework the docs page entirely, where this would be a good fit.

Sure, sounds good. In the meantime, we can get started with it right, collecting the resources and creating them if there aren't any? Would love to take lead and work through with it.

[austinlparker]

Yeah, I think a generic page with different tabs would be great. @Bhargavamacha if you'd like to take point on this, feel free!

[Bhargavamacha]

Cool, I'll get a basic framework of the webpage ready. Should a new issue be created?

[austinlparker]

Sure thing.

[austinlparker]

I'm going to close these because each language will have specific guides on export.