-
Notifications
You must be signed in to change notification settings - Fork 155
[Manage data] Expand 'Transform and enrich data' to match IA plan #316
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
Conversation
Thanks for working on this @kilfoyle! Looks great to me 👏 |
--- | ||
|
||
# Ingest pipelines | ||
# Elasticsearch ingest pipelines |
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.
# Elasticsearch ingest pipelines | |
# {{es}} ingest pipelines |
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.
Thanks @karenzone! I agree with the change, however attributes are not currently working in titles, and some other places, so until that's resolved I'll leave the raw text (that's what I see other people doing in their PRs).
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.
Nice work, @kilfoyle. And some good suggestions, @wajihaparvez. 🚀
Co-authored-by: wajihaparvez <[email protected]>
Co-authored-by: wajihaparvez <[email protected]>
Co-authored-by: wajihaparvez <[email protected]>
Co-authored-by: wajihaparvez <[email protected]>
Co-authored-by: wajihaparvez <[email protected]>
This reworks the "Transform and enrich data" section to supplement the content from Karen's ingest guide PR with content describing the child pages in this section, in accordance with the IA plan.
Please see: Docs preview
Rel: https://github.com/elastic/docs-projects/issues/366
Note to self: The "Elastic Agent processors" and all of the links to the Logstash docs need to be fixed after that content has been migrated.I understand that this part happens automatically when the reference content is migrated.