[Fleet] Fix data stream API when event.ingested is null#135817
Merged
kpollich merged 2 commits intoelastic:mainfrom Jul 6, 2022
Merged
[Fleet] Fix data stream API when event.ingested is null#135817kpollich merged 2 commits intoelastic:mainfrom
kpollich merged 2 commits intoelastic:mainfrom
Conversation
Contributor
|
Pinging @elastic/fleet (Team:Fleet) |
Member
Author
|
Issue is present on my 8.4 snapshot QA cloud deploy: |
Member
Author
|
@elasticmachine merge upstream |
💚 Build SucceededMetrics [docs]
History
To update your PR or re-run it, just comment with: cc @kpollich |
Member
Author
|
Issue appears to be resolved in the cloud deployment off of 8.4-SNAPSHOT for this PR
Going to merge this. |
8 tasks
Contributor
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
7 participants
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.
Summary
Closes elastic/elastic-agent#654
I don't actually have a great way to test this, so I'm working on getting a cloud deploy set up to attempt to reproduce the issue linked above. Putting this PR up so we can deploy it to cloud as well to compare.