fix: Fix panic for non-existing metric names #9757
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Required for all PRs:
related to #9756
In case you specify a
metric_name
within a parser configuration section you will actually set a query to fill the metric name. If this query references a non-existing node the code will panic as the resultingnil
value cannot be converted tostring
(see #9756). However, this might also happen in case you try to specify a constant metric name but omit thestring('...')
around that name.Catch the panic before it occurs and add test cases to test it works correctly.