Telemetry in the Go Toolchain

iamdamian wrote: post #3

4ad wrote: post #2

Another thread: https://news.ycombinator.com/item?id=34707583 . @dang can we merge these?

These posts and the conversations happening in them seem quite different.

If you're right, I'm sorry. Normally I'd have doublechecked that but I'm rushing out the door atm, so have to go with the usual pattern match.

Re: Telemetry in the Go Toolchain

#6

Post by Arnavion » Wed, Feb 08, 2023, 11:38 PM UTC

iamdamian wrote: post #3

4ad wrote: post #2

Another thread: https://news.ycombinator.com/item?id=34707583 . @dang can we merge these?

These posts and the conversations happening in them seem quite different.

The swtch.com post is the "introductory blog post" linked at the end of the GH discussion OP, and the GH discussion is the "discussion about how the Go toolchain can adopt telemetry" linked at the end of the swtch.com post.

Re: Telemetry in the Go Toolchain

#7

Post by rapnie » Thu, Feb 09, 2023, 7:29 AM UTC

dang wrote: post #4

4ad wrote: post #2

Another thread: https://news.ycombinator.com/item?id=34707583 . @dang can we merge these?

Comments moved thither. Thanks!

Did something go wrong? Algolia lists this submission as "108 points|h1x|16 hours ago|153 comments".

The other thread reference above is a different submission with "217 points by trulyrandom|18 hours ago|244 comments" and is not specific to the Golang metrics issue.

Re: Telemetry in the Go Toolchain

#8

Post by dang » Fri, Feb 10, 2023, 4:42 AM UTC

rapnie wrote: post #7

dang wrote: post #4

Earlier quoted context omitted.

Comments moved thither. Thanks!

Did something go wrong? Algolia lists this submission as "108 points|h1x|16 hours ago|153 comments". The other thread reference above is a different submission with "217 points by trulyrandom|18 hours ago|244 comments" and is not specific to the Golang metrics issue.

IIRC the two URLs pointed to articles with identical or nearly identical content.