[Meta] Standardize instrumentation docs with sample app

[svrnm]

Since we are very close to have standardized the "Getting Started" docs for all languages (see https://github.com/open-telemetry/opentelemetry.io/issues/2623), we can do the same now for other pages as well. Code-based Instrumentation is the next important one, so I create a ticket similar to #2623.

Each page should have a structure like the following:

• Introduction (standardized already)
• Advanced "roll the dice" example app
• Setup (language specific, load dependencies, etc.), initialize the SDK
• Traces
• Metrics
• Logs

Note

To implement this for a new language, please take a documentation from an existing language (https://opentelemetry.io/docs/instrumentation/js/manual/, https://opentelemetry.io/docs/instrumentation/java/manual/) and adjust it for the language you picked

Also, it is not necessary do solve all points in one PR, doing Example App + Setup + Traces first is a good point to get started.

Tracking:

• C++
  • [ ] Example app
  • [ ] Setup
  • [ ] Traces
  • [ ] Metrics
  • [ ] Logs
• .NET
  • [ ] Example app
  • [ ] Setup
  • [ ] Traces
  • [ ] Metrics
  • [ ] Logs
• Erlang/Elixir
  • [ ] Example app
  • [ ] Setup
  • [ ] Traces
  • [ ] Metrics
  • [ ] Logs
• Go
  • [ ] Example app
  • [ ] Setup
  • [ ] Traces
  • [ ] Metrics
  • [ ] Logs
• Java
  • [x] Example app
  • [x] Setup
  • [x] Traces
  • [ ] Metrics
  • [ ] Logs
• JavaScript
  • [x] Example app
  • [x] Setup
  • [x] Traces
  • [ ] Metrics
  • [ ] Logs
• PHP
  • [x] Example app
  • [x] Setup
  • [x] Traces
  • [ ] Metrics
  • [ ] Logs
• Python
  • [ ] Example app
  • [ ] Setup
  • [ ] Traces
  • [ ] Metrics
  • [ ] Logs
• Ruby
  • [ ] Example app
  • [ ] Setup
  • [ ] Traces
  • [ ] Metrics
  • [ ] Logs
• Rust
  • [ ] Example app
  • [ ] Setup
  • [ ] Traces
  • [ ] Metrics
  • [ ] Logs
• Swift
  • [ ] Example app
  • [ ] Setup
  • [ ] Traces
  • [ ] Metrics
  • [ ] Logs

[theletterf]

I'd like to help with this.

[cartermp]

great! Feel free to just pick one and send a PR; I don't think we have any preferred ordering 🙂

[IAMebonyhope]

I'll love to work on the .NET part

[svrnm]

@IAMebonyhope that's great to hear! To get started I recommend that you take one of the existing docs (java, JavaScript) and use them as a blueprint to create the same part for .NET (example app, setup, traces). Our goal is to provide a consistent and standardized documentation, so you can copy the outline and the words and fill in the .NET code and fix the wording where necessary. Don't hesitate to provide a draft PR early to get our feedback! Thank you!

[IAMebonyhope]

@svrnm here is a draft PR #3834 The example app and manual instrumentation setup sections are ready for review. I am still working on the traces section.