Skip to content

conf: parsers: fix istio-envoy-proxy parser regex #10203

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

Merged

Conversation

cmaddalozzo
Copy link
Contributor

@cmaddalozzo cmaddalozzo commented Apr 11, 2025

Fix the regex for the istio-envoy-proxy parser. Currently it includes a superfluous " character in the authority field and upstream_transport_failure_reason includes both " characters.


Enter [N/A] in the box, if an item is not applicable to your change.

Testing
Before we can approve your change; please submit the following in a comment:

  • [N/A] Example configuration file for the change
  • [N/A] Debug log output from testing the change
  • [N/A] Attached Valgrind output that shows no leaks or memory corruption was found

If this is a change to packaging of containers or native binaries then please confirm it works for all targets.

  • [N/A] Run local packaging test showing all targets (including any new ones) build.
  • [N/A] Set ok-package-test label to test for all targets (requires maintainer to do).

Documentation

  • [N/A] Documentation required for this feature

Backporting

  • [N/A] Backport to latest stable release.

Fluent Bit is licensed under Apache 2.0, by submitting this pull request I understand that this code will be released under the terms of that license.

@cmaddalozzo cmaddalozzo force-pushed the fix-istio-envoy-proxy-parser-regex branch from e073dca to 9119644 Compare April 11, 2025 14:35
@edsiper edsiper merged commit 4d5c62b into fluent:master Apr 23, 2025
39 of 42 checks passed
@edsiper edsiper added this to the Fluent Bit v4.0.1 milestone Apr 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants