Its a mess!!

[LRagji]

• This only affects the JavaScript OpenTelemetry library
• This may affect other libraries, but I would like to get opinions here first

Ok I am new or noob on Observability stack, so please help

I am trying to run otel-lgtm which has all the things needed locally on docker (Charts, Collector etc etc) This works and an able to move forward a little by little on that front.

When i switch to instrumentation side(just interested in metrics & spans) OTEL is the way to go, but here is the challenge i followed Getting started and i am reaching nowhere.

1. I used getNodeAutoInstrumentations() it loads tons of instrumentation as i can see from debug logs, but whenever i hit my express endpoint nothing !!
2. Then i looked at metrics exported i simply cannot find simplest CPU, Memory, Network utilization, it gives me all advanced v8stuff but the basics ones are missing. !!!
3. To debug further i went down the route of looking at express example here express example to my surprise it looks nothing like the getting started version which i started with.
4. To get simple metrics like CPU,Network,Memory i found this host metrics but they are using promethus i suppose which is again in different language.

It feels like every example is done with a different alien language and pattern which resembles nothing of the getting started pattern that i encounter, nothing works out of the box, and there are tons of npm and security updates on the package within like 5 days..

Can anybody give me a clear path of how auto-instrumentation can work out of box, my code is pushed here

_{Tip: React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.}