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

feat(plugin) Adds upstream_latency as an option to Statsd plugin #1466

Merged
merged 1 commit into from
Aug 8, 2016

Conversation

bivdub
Copy link
Contributor

@bivdub bivdub commented Aug 5, 2016

Summary

This PR adds upstream_latency as an option for the statsd logging plugin.

Full changelog

*adds upstream_stream latency as an option for statsd, reading the value from message.latencies.proxy
*adds test for the new value

@subnetmarco
Copy link
Member

@shashiranjan84 ^

@shashiranjan84
Copy link
Contributor

shashiranjan84 commented Aug 5, 2016

Thanks @bivdub for PR, would you please squash with rebase to one commit?

https://github.com/Mashape/kong/blob/master/CONTRIBUTING.md

@bivdub bivdub force-pushed the plugins/statsd/add-upstream-latency branch from a44ba2d to a639640 Compare August 5, 2016 05:45
@bivdub
Copy link
Contributor Author

bivdub commented Aug 5, 2016

Fixed, sorry about that. First PR on an open source project.

@shashiranjan84
Copy link
Contributor

@thefosk LGTM, can be merged once tests pass. I ll also update Datadog plugin.

@sonicaghi
Copy link
Member

welcome to the club @bivdub!

@thibaultcha thibaultcha added the pr/ready (but hold merge) No more concerns, but do not merge yet (probably a conflict of interest with another PR or release) label Aug 6, 2016
@subnetmarco
Copy link
Member

@shashiranjan84 do test pass locally?

@shashiranjan84
Copy link
Contributor

@thefosk I did not test locally.

@shashiranjan84
Copy link
Contributor

@thefosk ran statsd plugin test and lint locally, they all passed.

@subnetmarco subnetmarco merged commit 41073c9 into Kong:next Aug 8, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pr/ready (but hold merge) No more concerns, but do not merge yet (probably a conflict of interest with another PR or release)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants