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

Server-side per-operation timing #78

Open
MikeGoldsmith opened this issue Oct 23, 2017 · 5 comments
Open

Server-side per-operation timing #78

MikeGoldsmith opened this issue Oct 23, 2017 · 5 comments
Assignees

Comments

@MikeGoldsmith
Copy link
Contributor

No description provided.

@MikeGoldsmith MikeGoldsmith self-assigned this Oct 23, 2017
@brett19
Copy link
Contributor

brett19 commented Oct 23, 2017

What exactly is 'server-side tracing'?

@MikeGoldsmith
Copy link
Contributor Author

It's per operation server-side timings. I used the same name as the PRD for now, I'll update it once a more accurate name is available.

@MikeGoldsmith MikeGoldsmith changed the title Server-Side Tracing Server-side per-operation timing Oct 26, 2017
@pchovgh
Copy link

pchovgh commented Jul 26, 2019

I am new to github so pardon me if I am doing something stupid. I see server_us & server_duration_us, can you please help understand the difference?

Thanks

@MikeGoldsmith
Copy link
Contributor Author

Hi @pchovgh - this was an error in the JSON output in the blog article which has been fixed. There is just a server_us property that represents the take taken in the server to process the request.

@pchovgh
Copy link

pchovgh commented Jul 26, 2019 via email

avsej added a commit to avsej/sdk-rfcs that referenced this issue Apr 29, 2024
avsej added a commit to avsej/sdk-rfcs that referenced this issue May 20, 2024
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

No branches or pull requests

3 participants