Re: Implementor Meeting RSVP

I generally agree. The only (potential) question is whether we want to control latency of this solution tightly. So if events not available easily from an Agent and it takes a while to index them and make available from backend – apps need to expect huge latency. Which sometimes may lead to unwanted side effects. But I’d let DynaTrace folks to comment. Just proxying concern I heard.


From: Yuri Shkuro <>
Date: Friday, August 3, 2018 at 12:37 PM
To: "" <>
Cc: Fabian Lange <>, Nik Molnar <>, "" <>
Subject: Re: Implementor Meeting RSVP

They could write something like a small sidecar that will proxy the http request to the actual instrumented service, then before returning the result query the trace store and add span details to the response. I think this is preferable to building a complicated infra into the test harness.
Sent from my iPhone just by thinking it

On Aug 3, 2018, at 10:58 AM, Sergey Kanzhelev <<>> wrote:
One feedback for the test harness from DynaTrace was that they cannot produce span information from the same instance. So perhaps some separation of container that does headers processing and returns results may be required. I’d let DynaTrace reps to comment.

From: Yuri Shkuro <<>>
Sent: Friday, August 3, 2018 6:58 AM
To: Fabian Lange <<>>
Cc: Nik Molnar <<>>;<>
Subject: Re: Implementor Meeting RSVP

Hi Fabian,

The harness runs a docker-compose, that can pull everything as docker images. It does not **require** running code, unless you want it to. For example, we use a similar approach for testing Jaeger tracing libs, so the only actual code used is of that tracing lib (because this way we can run it on pull requests). I will dial in to the meeting on Monday, happy to discuss this more, but I didn't have time to work more on the harness.

Sent from my iPhone just by thinking it

On Aug 3, 2018, at 4:34 AM, Fabian Lange <<>> wrote:
Hi everybody,
if possible I would like to learn about the current state of testing harness.
Yury did great initial work on this, however there were also voices asking for a more "blackbox" way of testing.
(The harness Yury presented required to have the harness load the code and run it, more like a unit test)

There was an idea that the harness spins up an http server,
starts a simple proxy app "instrumented" by the agent under test,
sends it a request that will cause the proxy app to forward the request back to the harness
and then evaluates the response.

I wonder if anybody did some work on this.

We made out javascript header parser and manipulator library open source, looking forward for feedback. maybe it is helpful:<>


On Wed, 25 Jul 2018 at 23:13, Nik Molnar <<>> wrote:
Better yet, add yourself to the Participants list on the Google Doc:<>


From: Nik Molnar
Sent: Wednesday, July 25, 2018 4:08 PM
To: '<>' <<>>
Subject: Implementor Meeting RSVP

Hello all!

I’m trying to setup space for us to meet on campus at Microsoft for the Implementor Meeting on August 6th and 7th.

To do so, I need a rough head count of attendees. If you plan on coming to the meeting, could you please write back and let me know?


Received on Friday, 3 August 2018 21:08:08 UTC