Reminder (and homework): workshop in Sydney next Thursday and Friday

[adrian.f.cole]

In less than a week, we are meeting again, this time in Sydney. There is dial-in information now, if you're off site.

https://docs.google.com/document/d/19SQOio1z7mHqb79MzLQCiKdkq5tdirOW8OCcTQNQdUg/edit#

An overwhelming majority of folks want to discuss interop this time around, in terms of shared data formats. For example, propagation format (ex trace-context) or out-of-band formats such as zipkin, census or x-ray. Via shared formats, one can participate and decorate traces as they pass through intermediaries or are invoked by cloud-run services such as lambda.

Trace propagation formats

In the past, some discussions delayed due to lack of understanding about existing formats. For example, many commercial formats are not documented, or require paywall access to view. Playing 20 questions unnecessarily delays mutual understanding. So.. here's some homework.

If you have a trace context format, please capture it in a google doc and add it to the shared folder, marking shared all for comments. Your doc can simply be a link to other materials for starters. It will really help if you do this now, as some folks have long flights and can read it. Even better if you can grab an open slot to discuss your format!

Please also review issues in the trace-context specification and comment on them, or prepare some points you'd like to discuss. Having clear takeaway goals helps guide our time, so especially highlight show-stoppers or things that delay your ability to interop. For example, some may be delayed because they neither use nor can export to a dapper-like trace ID. Others might be delayed due to concerns with overhead or readability. Come up with your own list.

AWS Interop

More than a few have been interested in aws trace interop. Abhishek will be on-site, and it is guaranteed some time will be spent on this during the workshop. If you are not on-site, hop on gitter and maybe ask what you want there. If you will be on-site, please prepare yourself if you want to play with AWS interop. For example, make sure you have a working amazon account and can launch a lambda if that's what you are interested in. We won't have a lot of time, so preparation like this allows us to focus on tracing, not environment setup.

Standards

Thanks mainly to Alois, we have a couple slots for standards like chats. For example, W3C is a standards body which has controls such as a minimum number of parties before something can be called a standard. Please attend remotely or otherwise if you are interested in standards work.

Your notes here!

Please reply-back with things you'd like others' feedback on. The main point of these workshops is to allow a couple focus days from industry folks. Not everyone can comment on a daily basis, so this is an opportunity to collaborate without the distractions. If you have other things you'd like to ask others, please reply back.

Until then, thanks for the time reading this.. tata for now.

[wu.shen...@gmail.com]

Here is the Skywalking 3.2.x propagation protocol. It simply used a key-value pair for HTTP. Cole, as you know, I can't access the google doc, so post the document link here: https://github.com/OpenSkywalking/skywalking/wiki/Skywalking-3-Cross-Process-Propagation-Headers-Protocol

在 2017年10月27日星期五 UTC+8上午10:08:27，adrian.f.cole写道：