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

AWS X-Ray – Distributed Tracing System

aws.amazon.com

Post reply on HN
Print view View original

91–100 of 104 posts

Re: AWS X-Ray – Distributed Tracing System

#91

Post by AYBABTME »

j_s wrote: post #69
devbug wrote: post #16

If you're interested in distributed system tracing there's a lot going on. As a starting point, I would recommend reading Google's paper on their project "Dapper." [1] It's essentially the core of most distributed tracing systems. At least those I've encountered. There's a lot of tooling out there that take their cues from Dapper. I've recently been looking into integrating OpenZipkin[2] with our systems. I see at as…

I'm sure this is not new, but still useful to get the word out about the power of universal X-Request-Id: https://twitter.com/dhh/status/795732523640766464

Request IDs and their variants are only giving you correlated events, they don't encode enough information to connect causality and ordering of events. Basically: with request IDs you get a unordered bag of events, with proper tracing (trace id/span id/parent id) you get a DAG of events.

In practice, the analysis a DAG allows you to perform are way more powerful. So if you're in the process of setting that request ID stuff up, consider doing the tracing way.

Re: AWS X-Ray – Distributed Tracing System

#92

Post by mkj »

devbug wrote: post #16

If you're interested in distributed system tracing there's a lot going on. As a starting point, I would recommend reading Google's paper on their project "Dapper." [1] It's essentially the core of most distributed tracing systems. At least those I've encountered. There's a lot of tooling out there that take their cues from Dapper. I've recently been looking into integrating OpenZipkin[2] with our systems. I see at as…

YAPTA is a nice acronym, thanks!

Re: AWS X-Ray – Distributed Tracing System

#93

Post by roncohen »

martin_ wrote: post #82
roncohen wrote: post #78

Earlier quoted context omitted.

And if you're curious about how this sort of thing could look on the client/browser side of things, check out https://opbeat.com/react (I work on it)

Looks awesome! When're you opening up the invites?

Thanks! If you shoot me an e-mail i can get you access: ron@opbeat.com

Re: AWS X-Ray – Distributed Tracing System

#94

Post by svdgraaf »

nathankunicki wrote: post #88
DenisM wrote: post #66

Turns out X-Ray is sampling service, it drops data. You can use it to debug recurring problems, but it's no use when debugging a particular incident with the customer on the phone. Bummer. To provide a performant and cost-effective experience, X-Ray does not collect data for every request that is sent to an application. Instead, it collects data for a statistically significant number of requests. X-Ray should not be…

I was just in the 5:30pm re:Invent session at The Venetian. The service works via the SDK's in various languages, that report tracing information to a local daemon that runs on the host, over UDP. The daemon then batches the data, applies sampling (Which is configurable, all the way to 100% - report everything), and sends it en-masse to AWS. Edit: See Sampling Rules section here - http://docs.aws.amazon.com/xray/late…

geh, I was there as well :)

I concur, it was specifically stated that 100% sampling is an option (and is by default?)

Re: AWS X-Ray – Distributed Tracing System

#95

Post by shubb »

brazzledazzle wrote: post #86
shubb wrote: post #79

Earlier quoted context omitted.

The worry, places I've worked, is that the GPL would spread to proprietary stuff, like a kind of legal infection. They worry that if they use an AGPL javascript library for the video player on their front page, they'll have to opensource the whole web application (I've even sat in on debates over weather using GPL3 programs means you have to opensource any source data you use them to process and publish the result).…

They had to open source the chip design or the driver?

The chip design. It was a PVR box and an activist group wanted to opensource the DRM system they were using because they knew some important codes were baked into the chip so they took them to court. The court felt that the functionality was shared between the GPL kernel driver and the chip, so the chip fell under GPL.

Re: AWS X-Ray – Distributed Tracing System

#96

Post by shubb »

shubb wrote: post #95
brazzledazzle wrote: post #86

Earlier quoted context omitted.

They had to open source the chip design or the driver?

The chip design. It was a PVR box and an activist group wanted to opensource the DRM system they were using because they knew some important codes were baked into the chip so they took them to court. The court felt that the functionality was shared between the GPL kernel driver and the chip, so the chip fell under GPL.

I haven't been able to find any mention of this online. It was around 2009, and I may have misunderstood what I was being told...

Re: AWS X-Ray – Distributed Tracing System

#97

Post by mmclean »

tonyhb wrote: post #83
mmclean wrote: post #77

Earlier quoted context omitted.

Stackdriver Trace [1] is Google's external implementation of Dapper with additional analysis features. It's available for free, even for workloads not running on Google Cloud Platform. (Disclosure: I work on it) [1]: https://cloud.google.com/trace/

This is awesome! Can Google update the docs so that the links for external zipkin integrations work? They currently link in circles and there's no info on how to integrate into OpenTracing/Zipkin

Uh oh - are you referring to the docs on GitHub or the actual docs site (https://cloud.google.com/trace/docs/zipkin)?

Re: AWS X-Ray – Distributed Tracing System

#98

Post by mmclean »

mmclean wrote: post #97
tonyhb wrote: post #83

Earlier quoted context omitted.

This is awesome! Can Google update the docs so that the links for external zipkin integrations work? They currently link in circles and there's no info on how to integrate into OpenTracing/Zipkin

Uh oh - are you referring to the docs on GitHub or the actual docs site ( https://cloud.google.com/trace/docs/zipkin )?

Nevermind, I think we found it. Fixing now.

Re: AWS X-Ray – Distributed Tracing System

#99

Post by cce_ »

dgacmu wrote: post #59
devbug wrote: post #16

If you're interested in distributed system tracing there's a lot going on. As a starting point, I would recommend reading Google's paper on their project "Dapper." [1] It's essentially the core of most distributed tracing systems. At least those I've encountered. There's a lot of tooling out there that take their cues from Dapper. I've recently been looking into integrating OpenZipkin[2] with our systems. I see at as…

On the research front, going back prior to Dapper is x-trace: http://www.x-trace.net/wiki/doku.php and their follow on work, Pivot Tracing: http://pivottracing.io/ (which got a best paper award at SOSP'15.)

Tracelytics was a startup I co-founded based on X-Trace, which ended up as AppNeta's Traceview and is now part of the Solarwinds monitoring cloud suite of products (joining Librato, Pingdom, Papertrail). So look out for more tracing from us as well.

Re: AWS X-Ray – Distributed Tracing System

#100

Post by tonyhb »

mmclean wrote: post #98
mmclean wrote: post #97

Earlier quoted context omitted.

Uh oh - are you referring to the docs on GitHub or the actual docs site ( https://cloud.google.com/trace/docs/zipkin )?

Nevermind, I think we found it. Fixing now.

This part: https://cloud.google.com/trace/docs/zipkin#configure_zipkin_...

It doesn't show zipkin configuration :)

Post reply on HN