You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's surprising that you need to escape the . in foo.bar in the jsonPath expression, because according to the JSONPath specification you should not need to in a string lookup, so it's important to document it here.
A jsonPath expression that does not match anything in the json document returns an empty string, and if the collector does not resolve the name it sets record to an empty string, which makes it hard to distinguish between a broken JSONPath and the name not resolving.
The text was updated successfully, but these errors were encountered:
Describe the rationale for the suggested feature.
Currently the Host DNS analyzere example only shows how to spot wildcard DNS. It does not show how to spot when DNS does or does not resolve.
This is actually a moderately tricky thing to do reliably due to vagaries of
jsonCompare
and the k8s json path library.Describe the feature
Add an example of checking a name that will fail if the name does not resolve and pass if it does, as so:
Additional context
It's surprising that you need to escape the
.
infoo.bar
in thejsonPath
expression, because according to the JSONPath specification you should not need to in a string lookup, so it's important to document it here.A
jsonPath
expression that does not match anything in the json document returns an empty string, and if the collector does not resolve the name it setsrecord
to an empty string, which makes it hard to distinguish between a broken JSONPath and the name not resolving.The text was updated successfully, but these errors were encountered: