-
Notifications
You must be signed in to change notification settings - Fork 880
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: add support for Graphite metrics provider #1406
feat: add support for Graphite metrics provider #1406
Conversation
8815bce
to
10cbafc
Compare
Address issue argoproj#1403 by adding a Graphite metrics provider. Signed-off-by: Mike Ball <[email protected]>
10cbafc
to
8f4eb59
Compare
Signed-off-by: Mike Ball <[email protected]>
007a999
to
d1c71ac
Compare
Codecov Report
@@ Coverage Diff @@
## master #1406 +/- ##
==========================================
+ Coverage 81.67% 81.73% +0.06%
==========================================
Files 110 112 +2
Lines 14798 14947 +149
==========================================
+ Hits 12086 12217 +131
- Misses 2078 2091 +13
- Partials 634 639 +5
Continue to review full report at Codecov.
|
Signed-off-by: Mike Ball <[email protected]>
Signed-off-by: Mike Ball <[email protected]>
Per code review feedback... > It's a bad idea to use the golang HTTP default client because of possibility of hung connections, since it does not timeout As outlined here: https://medium.com/@nate510/don-t-use-go-s-default-http-client-4804cb19f779 The 10s timeout matches the default of the webmetric provider's HTTP client. Signed-off-by: Mike Ball <[email protected]>
Signed-off-by: Mike Ball <[email protected]>
Previously, `graphite.API#Query` returned the value of the last item in the `datapoints` array returned by the Graphite API. However, this somewhat diverged from the Prometheus metricprovider implementation and fails to consider a use case for obtaining the first or an arbitrary element from the datapoints array, as discussed here: argoproj#1406 (comment) Signed-off-by: Mike Ball <[email protected]>
Previously, `graphite.API#Query` returned the value of the last item in the `datapoints` array returned by the Graphite API. However, this somewhat diverged from the Prometheus metricprovider implementation and fails to consider a use case for obtaining the first or an arbitrary element from the datapoints array, as discussed here: argoproj#1406 (comment) Signed-off-by: Mike Ball <[email protected]>
b4ca2de
to
91e32aa
Compare
Signed-off-by: Mike Ball <[email protected]>
Signed-off-by: Mike Ball <[email protected]>
049c1aa
to
cb56197
Compare
Signed-off-by: Mike Ball <[email protected]>
…cs-provider Signed-off-by: Mike Ball <[email protected]>
@jessesuen Thanks for your patience. I'm curious to hear your feedback on my latest commits. Have I addressed your concerns? |
@mdb can you please rebase to latest master |
Signed-off-by: Jesse Suen <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
Address issue #1403 by adding a Graphite metrics provider.
Checklist:
"fix(controller): Updates such and such. Fixes #1234"
.