feat: web metrics preserve data types, allow insecure tls, and make jsonPath optional #731
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.
Resolves #728, #718, #717
When using jsonPath, the web metric always converted the result into a string. This is why the
asFloat
andasInt
helpers were introduced, in to convert these strings into numbers so that mathematical comparison could be performed. This change preserves the original types so thatasFloat
andasInt
are no longer necessary (as long as the original data types are numeric).Previously,
jsonPath
was a required field. This change allowsjsonPath
to be omitted, in which case the entire body is the payload.Added an
insecure: true
field that allows the web metric to disable TLS host verification when making HTTP requests.