Add default evenhub settings for each log type #27459
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
When we only put one default eventhub settings in this reference, the user might be confused they can use a single eventhub for all event types even the field mappings and parsing logic are different. Let's add all default settings with the notes that the user needs to understand each log type has different fields, expicitly.
|
Pinging @elastic/obs-docs (Team:Docs) |
💚 Build Succeeded
Expand to view the summary
Build stats
Trends 🧪❕ Flaky test reportNo test was executed to be analysed. |
bmorelli25
approved these changes
Aug 19, 2021
|
OK, I think I fixed the lint issues. This is a generated file, so the change has to be made in the source file and propagated with |
bmorelli25
added a commit
to bmorelli25/beats
that referenced
this pull request
Aug 19, 2021
Co-authored-by: Brandon Morelli <brandon.morelli@elastic.co>
bmorelli25
added a commit
to bmorelli25/beats
that referenced
this pull request
Aug 19, 2021
Co-authored-by: Brandon Morelli <brandon.morelli@elastic.co>
bmorelli25
added a commit
to bmorelli25/beats
that referenced
this pull request
Aug 19, 2021
Co-authored-by: Brandon Morelli <brandon.morelli@elastic.co>
bmorelli25
added a commit
that referenced
this pull request
Aug 23, 2021
bmorelli25
added a commit
that referenced
this pull request
Aug 23, 2021
bmorelli25
added a commit
that referenced
this pull request
Aug 23, 2021
Icedroid
pushed a commit
to Icedroid/beats
that referenced
this pull request
Nov 1, 2021
…ic#27510) Co-authored-by: Brandon Morelli <brandon.morelli@elastic.co> Co-authored-by: Insuk (Chris) Cho <isi.cho@gmail.com>
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.
What does this PR do?
When we only put one default eventhub settings in this reference, the user might be confused they can use a single eventhub for all event types even the field mappings and parsing logic are different. Let's add all default settings with the notes that the user needs to understand each log type has different fields, expicitly.
Why is it important?
The user could use one single eventhub and having trouble when the logs are parsed from Elasticsearch side.
Checklist
CHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.