Exposed and documented new fields creation_date and tier_preference for Elasticsearch integration#11942
Closed
3kt wants to merge 0 commit intoelastic:mainfrom
Closed
Exposed and documented new fields creation_date and tier_preference for Elasticsearch integration#119423kt wants to merge 0 commit intoelastic:mainfrom
3kt wants to merge 0 commit intoelastic:mainfrom
Conversation
8 tasks
8 tasks
This was referenced Dec 12, 2024
01e2fd9 to
dd3072a
Compare
9f0f7c2 to
575d4fa
Compare
💚 Build Succeeded
History
|
|
Contributor
Author
|
Closing in favor of #11656 |
This file contains hidden or 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
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
This change documents the new
tier_preferenceandcreation_dateindex fields for the Elasticsearch integration.Checklist
I have verified that all data streams collect metrics or logs.N/A no change was made herechangelog.ymlfile.I have verified that Kibana version constraints are current according to guidelines.No change made hereAuthor's Checklist
How to test this PR locally
By itself, this change doesn't change anything to the behavior of the integration, it will just modify the documentation.