-
Notifications
You must be signed in to change notification settings - Fork 882
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
fix(analysis): Graphite query - remove whitespaces #2752
Conversation
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## master #2752 +/- ##
==========================================
- Coverage 81.64% 81.62% -0.02%
==========================================
Files 133 133
Lines 20172 20157 -15
==========================================
- Hits 16469 16454 -15
Misses 2849 2849
Partials 854 854
☔ View full report in Codecov by Sentry. |
Signed-off-by: mdsjip <2284562+mdsjip@users.noreply.github.com>
e97d01c
to
ef90c16
Compare
Signed-off-by: mdsjip <2284562+mdsjip@users.noreply.github.com>
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
@zachaller will these changes be included in the next release soon? 🙂 |
If metric query contains surrounding whitespace, then it's not trimmed and Graphite host returns
400 Bad Request
Simplest example of analysis template:
When this is parsed from YAML, this query contains a newline in the end, so when it's "trimmed", it still contains a trailing space, so when put into the query, it becomes:
This leads to
400 Bad Request
response from Graphite, example cURL command:Proposed solution: replace all whitespace in the query with an empty string.
Checklist:
"fix(controller): Updates such and such. Fixes #1234"
.