-
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
[streaming] - Made namespace consistent in logging & put a null check to stop paincs on shutdown #42315
Merged
Merged
[streaming] - Made namespace consistent in logging & put a null check to stop paincs on shutdown #42315
Changes from 5 commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
0176f47
added blanket & infinite retry options and impoved logging
ShourieG a04b20f
removed an unnecessary namespace variable for a debug log causing a b…
ShourieG 864925a
merged conflict resolved
ShourieG 339327b
updated changelog
ShourieG 9ab94bf
fixed a situation when the input would panic during shutdown
ShourieG fcb19b4
addressed Andrew's suggestions
ShourieG 31503e8
updated changelog
ShourieG 71d0403
updated linter
ShourieG 8d1c570
Merge remote-tracking branch 'upstream/main' into streaming/dubug_fix
ShourieG 68b89bd
updated changelog
ShourieG File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
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.
There was nothing wrong with this version of the line. Checking the history, the problem was already addressed via 2ea4a2b which has become part of v8.16.2.
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.
Ok, but is the namespace call required though? We are already mentioning websocket in the error description, and none of the other local debug logs are using namespace. Should we still keep it around at this place ?
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.
Some context data is namespaced (and some isn't).
https://github.com/search?q=repo%3Aelastic%2Fbeats+path%3A%2F%5Ex-pack%5C%2Ffilebeat%5C%2Finput%5C%2Fstreaming%5C%2F%2F+lang%3Ago+%2Flogp%5C.Namespace%5C%28%2F&type=code
If anything I would ensure that it uses the namespace consistently, rather than removing it. The other calls depend on
ns
variable. And in one case, rather than using a custom namespaced field there is a perfectly good ECS field for the job -- http.response.body.content.