71–80 of 113 posts
Earlier quoted context omitted.
>> Did you remove the OpenTelemetry package? Exactly!
With your level of debugging, I'd say the problem was pebcak
Earlier quoted context omitted.
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.
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?
Amazing to see people defending telemetry especially in free software. Amazing, and sickening.
It's an interesting move given that OTel is not stable yet. :o
On the website it even says: "OpenTelemetry is in beta across several languages and is suitable for use. We anticipate general availability soon."
Amazing to see people defending telemetry especially in free software. Amazing, and sickening.
At Github's scale their setup and micro services depth would necessitate some type of correlated based tracing like this.
Heck even if your architecture is 1 layer thin OpenTelementry is still useful than crawling through logs every time there's an issue.
It's an interesting move given that OTel is not stable yet. :o
And why exactly is that interesting? Tech companies often use new products before they are stable, how else would they become battle-tested? On the website it even says: "OpenTelemetry is in beta across several languages and is suitable for use. We anticipate general availability soon."
Fyi: that quote has been there for a while.
For anyone interested in learning how to use Open Telemetry for distributed tracing in go, I recently made a demo app to share with some friends: https://github.com/michaelperel/otel-demo . To run, clone it & docker-compose up
Amount of "otel" instrumentation required in your code by LOC looks ridiculous to me. Isn't it a better approach to just use logs? e.g. defer ctx.WithField("path", path).Trace("opening").Stop(&err) from https://medium.com/@tjholowaychuk/apex-log-e8d9627f4a9a