-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
docs: Update template and field path syntax #14849
Conversation
✅ Deploy Preview for vector-project ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
Signed-off-by: Spencer Gilbert <spencer.gilbert@datadoghq.com>
Signed-off-by: Spencer Gilbert <spencer.gilbert@datadoghq.com>
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.
Changes look good to me. Seems like deploy is failing, but I can review again when the deploy is up.
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.
Looks good!
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.
Mostly reviewed for spelling/grammar.
website/content/en/docs/reference/configuration/template-syntax.md
Outdated
Show resolved
Hide resolved
…x.md Co-authored-by: neuronull <kyle.criddle@datadoghq.com>
* docs: Update template and field path syntax * +netlify redirect path-fields to vrl/expressions/#path Signed-off-by: Spencer Gilbert <spencer.gilbert@datadoghq.com> * +delete old field-path page Signed-off-by: Spencer Gilbert <spencer.gilbert@datadoghq.com> * +fix link Signed-off-by: Spencer Gilbert <spencer.gilbert@datadoghq.com> * Update website/content/en/docs/reference/configuration/template-syntax.md Co-authored-by: neuronull <kyle.criddle@datadoghq.com> Signed-off-by: Spencer Gilbert <spencer.gilbert@datadoghq.com> Co-authored-by: neuronull <kyle.criddle@datadoghq.com>
Field path notation has been replaced by the shared lookup code. Problematically we don't report errors from these very well see #13033 for the solution there.
Technically these don't require (today) a leading
.
in the path expression, but that may change in the future and, to me, it's less confusing to have two different ways of handling lookups.