[docs] Add the subobjects adoption guide to docs #9874
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jsoriano
approved these changes
May 15, 2024
docs/subobjects_adoption_guide.md
Outdated
|
|
||
| #### Field vs. Data Stream | ||
|
|
||
| Users can set the subobjects mapping parameter on a single field or for the whole data stream (root level). |
There was a problem hiding this comment.
Should we give any recommendation about when to use one or the other option?
There was a problem hiding this comment.
Yep, adding a couple of paragraphs.
There was a problem hiding this comment.
@jsoriano, I moved this section to the following overview; it seems to make more sense. I also added a couple of paragraphs that mention cases for field and data stream levels.
Let me know what you think.
🚀 Benchmarks reportTo see the full report comment with |
zmoog
force-pushed
the
zmoog/subobjects-adoption-guide
branch
from
1c5e346
to
04c8c21
Compare
|
/test |
1 similar comment
|
/test |
|
|
/test |
zmoog
force-pushed
the
zmoog/subobjects-adoption-guide
branch
from
04c8c21
to
3f90caa
Compare
|
/test |
2 similar comments
|
/test |
|
/test |
|
A few integrations keep failing due to the following error: |
|
/test |
Co-authored-by: Jaime Soriano Pastor <jaime.soriano@elastic.co>
Co-authored-by: Jaime Soriano Pastor <jaime.soriano@elastic.co>
zmoog
force-pushed
the
zmoog/subobjects-adoption-guide
branch
from
3f90caa
to
a1432ea
Compare
💚 Build Succeeded
History
cc @zmoog |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Proposed commit message
Add history, usage, and recommendations for using the subobjects mapping parameter in Elasticsearch and in integrations.
Checklist
I have reviewed [tips for building integrations](https://github.com/elastic/integrations/blob/main/docs/tips_for_building_integrations.md) and this pull request is aligned with them.I have verified that all data streams collect metrics or logs.I have added an entry to my package'schangelog.ymlfile.I have verified that Kibana version constraints are current according to guidelines.