No, OpenTelemetry is focussed on gathering metrics in distributed systems. Metrics, log aggregation and tracing of requests from the entrypoint (load balancer) all the way to the backend services and data stores.

Take a look at the Jaeger and Zipkin websites and it should be pretty clear what it is used for.

And, it should be stated, that it isn't even really about gathering metrics. It is about providing a standard interface to gather metrics. (I know you know this, but with the confusion here, I figure I should go into details).

The point of OpenTelemitry is to make it so you could write the places you get your traces/metrics in one part of code and configure which backend system it is collected into in another part.

So, for example, you'd add a `trace("my slow thing"){ be slow }` into your code and later add `report to zipkin` or `report to Jaeger` in another part. The place where you trace "my slow thing" doesn't care about how to interact with the backend system or which backend vendor is ultimately used. You can start using prometheus, zipkin, new relic, Jaeger, whatever, just so long as they have an OpenTelemetry adapter you are golden.

The analog is SLF4J in Java.

That makes zero sense. Of course accessing a GitHub remote with git means accessing a huge distributed system and involves "load balancer all the way to the backend services and data stores". If anything, that is the core of GitHub and the webui is bolted on.

It's baffling to me, what do people think happens when they pull/push from a GitHub repo?

I interpreted the original question to be concerned about phone home telemetry in the git binary.

Huh? The day GitHub has that much control over the Git project, the world of software as we know it will end.

GitHub ≠ Git. Far from it.

Add to this that it’s Microsoft owned.