Hi Chris,
On 18 March 2016 at 14:35, Chris Snider <chris.sni...@issinc.com> wrote:
>
>
> For our application stack, we use Zipkin with a backing Cassandra store in
> a Docker environment. This also uses a custom httpclient that is
> integrated into the various levels of the app stack and service
> implementations. Zipkin adds a custom header that is tracked through the
> calls.
>
Looks like Zipkin is a more advanced approach along the same lines. From
what I can tell from a quick read it uses 3-5 headers?
*X-B3-TraceId*: overall trace id
*X-B3-SpanId*: id for current step/component in a graph of services
*X-B3-ParentSpanId*: SpanId from any parent component/step
*X-B3-Flags* & *X-B3-Sampled*: track "debug" requests and whether
additional performance sampling is requested
Each ID is 64bits hex-encoded (ie. half the length of a UUID)
Does that sound about right?
I'm not overly keen to add such a complex implementation -- would what's
currently be proposed be useful for you? Do your team find the ability to
trace requests helpful?
https://brandur.org/request-ids discusses a similar pattern as I've
proposed, though each step (eg. frontend, GeoServer, WPS task, cascaded
WFS, database) would all generate their own UUIDs then append them together.
Cheers,
Rob :)
------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785231&iu=/4140
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
