docs: add quickstart code example

[vreynolds]

Which problem is this PR solving?

• Adding a minimal quickstart setup to readme, so visitors can get something up without clicking around the docs
• Closes Add minimal setup to README #2347

Short description of the changes

subjective tradeoffs:

• node metapackage for fewer dependency lines and more instrumentation out of the box, but other docs use individual instrumentation pacakges
• console exporter so no need to set up a tracing backend, but you don't get to see nice graphs

[codecov]

Codecov Report

Merging #2365 (0278662) into main (3bc3452) will decrease coverage by 0.01%.
The diff coverage is n/a.

❗ Current head 0278662 differs from pull request most recent head b5c1e09. Consider uploading reports for the commit b5c1e09 to get more accurate results

@@            Coverage Diff             @@
##             main    #2365      +/-   ##
==========================================
- Coverage   92.79%   92.77%   -0.02%     
==========================================
  Files         145      145              
  Lines        5221     5221              
  Branches     1070     1070              
==========================================
- Hits         4845     4844       -1     
- Misses        376      377       +1     

Impacted Files	Coverage Δ
...emetry-core/src/platform/node/RandomIdGenerator.ts	87.50% <0.00%> (-6.25%)	⬇️

[dyladan]

Looks good to me. Since this is likely the first documentation users see I would like to have comments that explain what the more confusing parts are doing.

[CptSchnitz]

Shouldn't @opentelemetry/node and not @opentelemetry/sdk-node be installed if the tracing is initiated like this?

[vreynolds]

Shouldn't @opentelemetry/node and not @opentelemetry/sdk-node be installed if the tracing is initiated like this?

I initially imported node and tracing individually, but sdk-node was mentioned in the SIG meeting and seemed like a better candidate here, since it's meant to be a more wholesale package for Node users (includes both tracing and metrics).

[CptSchnitz]

Shouldn't @opentelemetry/node and not @opentelemetry/sdk-node be installed if the tracing is initiated like this?

I initially imported node and tracing individually, but sdk-node was mentioned in the SIG meeting and seemed like a better candidate here, since it's meant to be a more wholesale package for Node users (includes both tracing and metrics).

i just looked at the readme for sdk-node and it seems like its initialization is much simpler compared to doing everything manually, maybe its better to adapt the quick start to use it.
https://github.com/open-telemetry/opentelemetry-js/blob/main/packages/opentelemetry-sdk-node/README.md

[dyladan]

Shouldn't @opentelemetry/node and not @opentelemetry/sdk-node be installed if the tracing is initiated like this?

I initially imported node and tracing individually, but sdk-node was mentioned in the SIG meeting and seemed like a better candidate here, since it's meant to be a more wholesale package for Node users (includes both tracing and metrics).

i just looked at the readme for sdk-node and it seems like its initialization is much simpler compared to doing everything manually, maybe its better to adapt the quick start to use it.
https://github.com/open-telemetry/opentelemetry-js/blob/main/packages/opentelemetry-sdk-node/README.md

I would also support this. You can either update this PR or we can review and merge this (since it is an improvement) and do the sdk-node in a sparate PR. Up to you.

[vreynolds]

Aha, I'm using it as a meta package, instead of utilizing the actual simplified setup. Got it, and agree that it would be better. Updating now.