opentelemetry-proto-go VS jest-opentelemetry

VictoriaMetrics CTO here.

The referred library is the official OpenTelemetry package for reading metrics in Go language [1] - more details are available at [2].

Note that we at VictoriaMetrics like the idea of unified observability standard like OpenTelemetry. The issue is in the current otel implementation. It is too bloated and very inefficient. This contradicts to our experience with observability cases, which need very optimized format for metrics' transfer in order to reduce costs on CPU and network traffic needed to transfer and process these metrics.

VictoriaMetrics continues investing in OpenTelemetry by providing integration docs [3] and improving the existing functionality for otel metrics' ingestion [4].

[1] https://github.com/open-telemetry/opentelemetry-proto-go

[2] https://github.com/VictoriaMetrics/VictoriaMetrics/pull/2570...

[3] https://docs.victoriametrics.com/guides/getting-started-with...

[4] https://github.com/VictoriaMetrics/VictoriaMetrics/issues/60...

Jest-opentelemetry was created out of a pain that @galklm and I felt when working on complex systems with multiple side effects, some of which happen asynchronously. People were changing the code of different services frequently, but weren't always aware of the dependencies across the system. So often, things would break - resulting in us up at 4am debugging the issue and reverting some recent deployments.

(Adding here our repo - https://github.com/traceloop/jest-opentelemetry, although this honestly doesn't mean to be a self-promoting post. I'm actually looking for honest feedback).