-
Notifications
You must be signed in to change notification settings - Fork 60
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
Add ECS known issue for ecs@mappings and fieldless searches #1330
base: main
Are you sure you want to change the base?
Add ECS known issue for ecs@mappings and fieldless searches #1330
Conversation
A documentation preview will be available soon. Request a new doc build by commenting
If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here. |
This pull request does not have a backport label. Could you fix it @zmoog? 🙏
|
All 8.13.x releases are affected.
run docs-build |
@kilfoyle, do you think it's okay to link to the public URL of a KB article? The article's author thoroughly summarized the issue and described workaround and solutions. I would love to leverage this work and use it as the source of truth if there are updates. |
@zmoog If the KB article is truly public then yes, for sure you can just link to it. That would be ideal. However, if I'm not mistaken, either some or all KB articles require a Cloud account to view. If that's the case, we'd need the information to be available in the known issue to support users who don't have a Cloud account, and then we can still link to the KB article for reference. |
docs/en/ingest-management/release-notes/release-notes-8.13.asciidoc
Outdated
Show resolved
Hide resolved
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.
LGTM! 🚀
Thanks for adding this @zmoog. It looks perfect. I added just one super small suggestion.
You don't need to be a paying customer to read the content, but you will need to log in to Elastic Cloud. If you think this scenario does not qualify for this document, I can summarize it for the release notes and keep it up to date until we're out of the ecs@mappings issues. |
…iidoc Co-authored-by: David Kilfoyle <[email protected]>
Sorry, I read the first sentence and started responding! 🤦 Continuing here. The KB articles can be internal only or available to customers. When they're available to customers, they still need an EC account. I'll summarize the KB article for the release notes and link to the original KB article, mentioning that it requires a free EC account. |
Sounds perfect! And everything looks good. Thanks for looking after this @zmoog! |
Update the 8.13 release notes to add a known issue.
Due to changes introduced to support the ecs@mappings component template (see https:/elastic/kibana/pull/174855[elastic/kibana/pull/174855), Fleet no longer includes ECS fields to the integrations'
index.query.default_field
.This may affect integrations that rely on fieldless queries (when no field is specified for a query).
This PR updates the 8.13 release notes to
Relates elastic/integrations#10848