4 ms·
Have you seen the OTEL auto instrumentation package[1]? It supports a number of common frameworks (as middleware) and libraries (via monkeypatches) setting up s
by vadman97 3y ago
Have you seen the OTEL auto instrumentation package[1]? It supports a number of common frameworks (as middleware) and libraries (via monkeypatches) setting up spans for you to capture things like external http requests, database/cache queries, etc. [2]
[1] https://opentelemetry.io/docs/instrumentation/js/automatic/ https://opentelemetry.io/docs/instrumentation/js/automatic/
[2] https://github.com/open-telemetry/opentelemetry-js-contrib/tree/main/metapackages/auto-instrumentations-node#supported-instrumentations https://github.com/open-telemetry/opentelemetry-js-contrib/t...
- _boffin_ 3y agoTested those before, but still doesn't get what i'm looking for, which is inside the black box without manually adding the spans. The implementations for bunyan or winston would come the closet, but still doesn't achieve what i'm looking for.
- eep_social 3y agoI think the Ruby auto-instrumentation library does wrap practically every method but we ended up finding it too verbose. I think this is a bit of a goldilocks problem insofar as getting it just right is not easy and varies per application.
- _boffin_ 3y agoOne of the things i think that can be done is also limit the number of spans collected via configuration.
- eep_social 3y agoAye, but then you’re trading off between a centralized config that does sampling vs customized per-service (or whatever boundary) configs. There’s no free lunch, was mostly my point.