-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
[Elastic Agent] Add event.dataset to all events #20076
Merged
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
botelastic
bot
added
needs_team
Indicates that the issue/PR needs a Team:* label
and removed
needs_team
Indicates that the issue/PR needs a Team:* label
labels
Jul 20, 2020
Pinging @elastic/ingest-management (Team:Ingest Management) |
Collaborator
ph
approved these changes
Jul 21, 2020
michalpristas
approved these changes
Jul 22, 2020
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.
Looks ok
4 tasks
blakerouse
added a commit
to blakerouse/beats
that referenced
this pull request
Jul 22, 2020
* Inject add_fields event.dataset along side dataset. * Add event.dataset to all published events. * Add changelog. (cherry picked from commit c4010d9)
blakerouse
added a commit
to blakerouse/beats
that referenced
this pull request
Jul 22, 2020
* Inject add_fields event.dataset along side dataset. * Add event.dataset to all published events. * Add changelog. (cherry picked from commit c4010d9)
4 tasks
blakerouse
added a commit
that referenced
this pull request
Jul 22, 2020
blakerouse
added a commit
that referenced
this pull request
Jul 22, 2020
melchiormoulin
pushed a commit
to melchiormoulin/beats
that referenced
this pull request
Oct 14, 2020
* Inject add_fields event.dataset along side dataset. * Add event.dataset to all published events. * Add changelog.
leweafan
pushed a commit
to leweafan/beats
that referenced
this pull request
Apr 28, 2023
…tic#20137) * Inject add_fields event.dataset along side dataset. * Add event.dataset to all published events. * Add changelog. (cherry picked from commit c231090)
This was referenced Aug 3, 2023
4 tasks
Merged
4 tasks
5 tasks
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?
Adds
event.dataset
to match the same asdataset.name
from the event. This is done on all configurations, even the sidecar monitoring beats.Why is it important?
So published events do not prevent other features from working in Kibana and ML.
Checklist
[ ] I have made corresponding changes to the documentation[ ] I have made corresponding change to the default configuration filesCHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.How to test this PR locally
Run
elastic-agent
ensure that all events published to elasticsearch haveevent.dataset
that matches thedataset.name
.Related issues