Skip to content

[9.0](backport #44342) [filebeat][streaming] - Fixed a websocket panic scenario which would occur after exhausting max retries#44392

Merged
ShourieG merged 1 commit into9.0from
mergify/bp/9.0/pr-44342
May 20, 2025
Merged

[9.0](backport #44342) [filebeat][streaming] - Fixed a websocket panic scenario which would occur after exhausting max retries#44392
ShourieG merged 1 commit into9.0from
mergify/bp/9.0/pr-44342

Conversation

@mergify
Copy link
Contributor

@mergify mergify bot commented May 20, 2025

Type of change

  • Bug

Proposed commit message

In some scenarios the websocket response object can become nil and
cause  certain logging statements to cause an unexpected panic. This PR
fixes once  such identified scenario.

Checklist

  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have made corresponding change to the default configuration files
  • I have added tests that prove my fix is effective or that my feature works
  • I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Disruptive User Impact

None

Author's Checklist

  • [ ]

How to test this PR locally

Related issues

Use cases

Screenshots

Logs

This is an automatic backport of pull request #44342 done by [Mergify](https://mergify.com).
@ShourieG @mergify
[filebeat][streaming] - Fixed a websocket panic scenario which would …
25b64a9 
…occur after exhausting max retries (#44342)

In some scenarios the websocket response object can become nil and
cause  certain logging statements to cause an unexpected panic. This PR
fixes once  such identified scenario.

(cherry picked from commit f6994c0)
@mergify mergify bot added the backport label May 20, 2025
@mergify mergify bot requested a review from a team as a code owner May 20, 2025 07:20
@mergify mergify bot added the backport label May 20, 2025
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label May 20, 2025
@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label May 20, 2025
@elasticmachine
Copy link
Contributor

elasticmachine commented May 20, 2025

Pinging @elastic/security-service-integrations (Team:Security-Service Integrations)
@ShourieG ShourieG merged commit 5558151 into 9.0 May 20, 2025
24 of 27 checks passed
@ShourieG ShourieG deleted the mergify/bp/9.0/pr-44342 branch May 20, 2025 09:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport bugfix Filebeat Filebeat input:streaming Team:Security-Service Integrations Security Service Integrations Team

2 participants

@elasticmachine @ShourieG