Hi Andrea,
On 18 March 2016 at 10:22, Andrea Aime wrote:
> Hi Robert,
> sorry for the late reply, busy times, could not answer right away and then
> lost it in the build
> server failures storm that we have been into lately
>
No worries, I completely understand :)
>>- Alter the Request cl
@lists.sourceforge.net
Subject: Re: [Geoserver-devel] Request IDs
Hi Chris,
On 18 March 2016 at 14:35, Chris Snider
mailto: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 integrate
Hi Chris,
On 18 March 2016 at 14:35, Chris Snider 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. Zipk
Subject: Re: [Geoserver-devel] Request IDs
On Fri, Mar 18, 2016 at 12:53 PM, Robert Coup
mailto:robert.c...@koordinates.com>> wrote:
One small extra note, it could also be useful to have also have the request id
in the response header, so that
if I have a problematic request in the client,
On Fri, Mar 18, 2016 at 12:53 PM, Robert Coup
wrote:
> One small extra note, it could also be useful to have also have the
>> request id in the response header, so that
>> if I have a problematic request in the client, I can go and look for the
>> id and then grep the logs for just the log
>> lin
Hi Robert,
sorry for the late reply, busy times, could not answer right away and then
lost it in the build
server failures storm that we have been into lately
On Tue, Mar 8, 2016 at 8:32 PM, Robert Coup
wrote:
> Hi folks,
>
> Just exploring the best way to go about this. We use a X-Request-ID he
