Skip to content

Conversation

@Qard
Copy link
Contributor

@Qard Qard commented Aug 30, 2018

Retargetting #524 to api-v2...

Fixes #421

@Qard Qard mentioned this pull request Aug 30, 2018
@Qard Qard changed the title Distributed tracing feat: distributed tracing Aug 30, 2018
@Qard Qard force-pushed the distributed-tracing branch 2 times, most recently from 5c28cc2 to fe39c08 Compare August 30, 2018 17:05
@Qard Qard requested a review from watson August 30, 2018 17:15
@Qard Qard self-assigned this Aug 30, 2018
@Qard Qard force-pushed the distributed-tracing branch 2 times, most recently from eb08831 to 8d08556 Compare September 5, 2018 23:30
@Qard
Copy link
Contributor Author

Qard commented Sep 5, 2018

Rebased with #557 to get tests passing.

@Qard Qard force-pushed the distributed-tracing branch 5 times, most recently from 6c0b200 to 4892168 Compare September 6, 2018 00:11
@Qard Qard force-pushed the distributed-tracing branch 5 times, most recently from 4fd6de6 to 011f5d9 Compare September 10, 2018 18:45
Copy link
Contributor

@watson watson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You forgot to add the traceId to the transaction (and error?) payload if I remember the API correctly.


Object.defineProperty(this, 'id', {
get () {
return this.context.id.toString('hex')
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's probably best to cache this value. Currently it's not used more than once, but I wouldn't be surprised if we started to output this in logs as well.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should probably actually just log the context object, in the future, so the trace id is there too. 🤔

@Qard Qard force-pushed the distributed-tracing branch from 011f5d9 to f0dedbc Compare September 10, 2018 22:59
@Qard
Copy link
Contributor Author

Qard commented Sep 10, 2018

@watson I made some changes to try having a shared buffer and string getters.

@Qard Qard force-pushed the distributed-tracing branch 5 times, most recently from 4a6a1a1 to 8fd0cb9 Compare September 11, 2018 21:27
@Qard Qard force-pushed the distributed-tracing branch from bd05282 to 24d5548 Compare October 1, 2018 21:44
@watson
Copy link
Contributor

watson commented Oct 17, 2018

@Qard the merge conflicts look a little bit complicated, so I didn't want to spend too much time on it. I assume you could do it very quickly 😃

@watson
Copy link
Contributor

watson commented Oct 17, 2018

@Qard never mind. I managed to fix the merge conflicts

@watson watson merged commit 9d4c4ac into elastic:api-v2 Oct 17, 2018
@Qard Qard deleted the distributed-tracing branch October 17, 2018 19:45
watson pushed a commit to watson/apm-agent-nodejs that referenced this pull request Oct 27, 2018
Qard added a commit that referenced this pull request Oct 31, 2018
watson pushed a commit to watson/apm-agent-nodejs that referenced this pull request Nov 6, 2018
watson pushed a commit that referenced this pull request Nov 6, 2018
Qard added a commit that referenced this pull request Nov 8, 2018
watson pushed a commit to watson/apm-agent-nodejs that referenced this pull request Nov 13, 2018
watson pushed a commit to watson/apm-agent-nodejs that referenced this pull request Nov 13, 2018
watson pushed a commit to watson/apm-agent-nodejs that referenced this pull request Nov 13, 2018
watson pushed a commit to watson/apm-agent-nodejs that referenced this pull request Nov 13, 2018
watson pushed a commit to watson/apm-agent-nodejs that referenced this pull request Nov 13, 2018
watson pushed a commit to watson/apm-agent-nodejs that referenced this pull request Nov 13, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants