Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow explicit timestamps for Span start/end. #22

Closed
wants to merge 3 commits into from

Conversation

carlosalberto
Copy link
Contributor

No description provided.

@carlosalberto
Copy link
Contributor Author

Addresses #24

One thing that that mentioned was that OT uses microseconds - which might not be the case for this new API ;)

@tylerbenson
Copy link
Member

FWIW, I am strongly in favor of NOT using micros. I would rather see something like TimeUnit as a second argument.

@yurishkuro
Copy link
Member

FWIW, I am strongly in favor of NOT using micros. I would rather see something like TimeUnit as a second argument.

+1

Why are there 34 files in this PR? Doesn't seem to match the title.

@bogdandrutu
Copy link
Member

Should this be closed because of #43?

@SergeyKanzhelev
Copy link
Member

Closing this as I believe current decision is to use SpanData for these scenarios

@bogdandrutu bogdandrutu deleted the start_end_with_explicit_tstamp branch April 15, 2019 23:06
jkwatson pushed a commit that referenced this pull request Jul 30, 2020
* Implemented TraceConfigZ zPage (#22)

* Added link to index zpage

* Used AutoValue for TableRow classes

* Changed wording of HTML content

* Changed Builder to interface, fixed build issues

* Removed tableRow classes, added omitEmpty in parseQueryMap

* Added test for invalid inputs

* Changed to use illegalArgumentException
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants