Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Why and how GitHub is adopting OpenTelemetry

github.blog

Post reply on HN
Print view View original

81–90 of 113 posts

Re: Why and how GitHub is adopting OpenTelemetry

#81

Post by porker »

wdb wrote: post #45
infogulch wrote: post #41

For everyone blindly rage triggered by the presence of the bytes "t-e-l-e-m-e-t-r-y", cogman10 elsewhere ITT [1] summarized that concern well: > It's like being afraid your browser profiler is being used to spy on you. Could it do that? Sure. but there are so many easier ways to accomplish the same task. So take a second to straighten out your panties and then actually look at the thing first. It's just an open-sourc…

It doesn't really compete Datadog, Dynatrace, Honeycomb, Lightstep, new Relic are all partners in defining the specification and help implementing it. Most of them already allowing ingesting traces over the OLTP protocol

Yes, where it helps is every programming language and framework can have one integration with OpenTelemetry, rather than custom ones for each separate telemetry system.

Re: Why and how GitHub is adopting OpenTelemetry

#82

Post by hendry »

bassdropvroom wrote: post #80
hendry wrote: post #70

Earlier quoted context omitted.

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

Opentelemetry is a lot more than that. It can handle traces across services.

You can log and use a tool like AWS LogInsights to see the trace across services..

No code changes needed.

Re: Why and how GitHub is adopting OpenTelemetry

#85

Post by tedk-42 »

Datagenerator wrote: post #71
tedk-42 wrote: post #60

Earlier quoted context omitted.

With your level of debugging, I'd say the problem was pebcak

Removed code is debugged code, according to the infamous suckless website and the creator of ZeroMQ. (1) 1) http://suckless.org/philosophy/

OK but not related to the issue mentioned by the poster. Good code isn't minimalistic, else we'd be writing all our code in a code golf style with fewest possible characters.

Funny that my comment got flagged - If you really believe removing something fixes your problem, what about other people who could have the same issue as you or the people that don't have your issue and used the library successfully?

You've effectively removed yourself as the possible cause to the problem and you probably are the problem if no-one else has reported the issue. You're the problem for not reporting it and you're the problem for complaining about it 'not working' when you did so little to try socialise a fix or look into it more deeply.

Re: Why and how GitHub is adopting OpenTelemetry

#88

Post by hobofan »

jonatan-ivanov wrote: post #79
hobofan wrote: post #76

Earlier quoted context omitted.

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."

I guess because you might not want to go to prod with something on GH scale that is not stable and still subject to have breaking changes? Fyi: that quote has been there for a while.

It's usually the opposite: You might not want to go to prod with something like this on an SMB scale where you have little resources to navigate tech debt.

On a Github scale where you have more engineers available, it's often worth it to adopt cutting-edge alpha/beta software for their novel features, as you generally also have more expertise/mechanisms to ensure stability of the overall product and run less risk of being suffocated in tech debt.

Re: Why and how GitHub is adopting OpenTelemetry

#89

Post by weberer »

kortex wrote: post #66

Mandatory "do some research before jumping to freaking out at GitHub for 'spyware.'" Yes technically you could use OT to exfiltrate data; guess what, you can do it with http headers, too. Been using OpenTelemetry for python and golang. It's great. I really like using Jaeger for tracing across small ML webapps. We have users on the scale of dozens so I just trace everything without sampling. Way, way easier than going…

They problem is that Microsoft continuously used the term "telemetry" as a euphemism for the dystopian corporate spyware they shipped with Windows 10. So now to the average end user, the two concepts are the same.

This is compounded by the fact that Github is now a Microsoft company and Microsoft has been caught in the past hiding "telemetry" in programs compiled with Visual Studio.

https://old.reddit.com/r/cpp/comments/4ibauu/visual_studio_a...

Re: Why and how GitHub is adopting OpenTelemetry

#90

Post by yannoninator »

scrollaway wrote: post #59
yannoninator wrote: post #21

I’m now gravely concerned about GitHub after reading this. So now I should be excited about telemetry and that GitHub uses this in their systems? This raises alarm bells into if I should be using them for my repositories at all. Unsure if I should trust GitHub after this now. Downvoters: I don’t understand here? So I should be excited about telemetry? Why?

You're getting downvoted because you are complaining about something you don't understand, which puts into question the "after reading this" part of your post. Jumping on the first opportunity to rant about telemetry without even checking what the article is talking about will do that.

then why name it open "telemetry" in the first place? you know it has an extremely bad connotation to spyware.

> which puts into question the "after reading this"

> without even checking what the article is talking about will do that.

please don't do that, this is against the HN guidelines.

https://news.ycombinator.com/newsguidelines.html

Post reply on HN