Skip to content
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

Nginx ingress_controller pipeline can not parse domain socket #30702

Closed
leweafan opened this issue Mar 6, 2022 · 2 comments · Fixed by #34732
Closed

Nginx ingress_controller pipeline can not parse domain socket #30702

leweafan opened this issue Mar 6, 2022 · 2 comments · Fixed by #34732
Labels
Team:Integrations Label for the Integrations team

Comments

@leweafan
Copy link
Contributor

leweafan commented Mar 6, 2022

Describe the enhancement:

Nginx ingress_controller pipeline supports only upstream format "IP:port" and doesn't support socket.
According to https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/log-format/ description of variable $upstream_addr:

the IP address and port (or the path to the domain socket) of the upstream server.

Nginx ingress_controller grok for variable nginx.ingress_controller.upstream_address_list:

UPSTREAM_ADDRESS_LIST (?:%{IP}(:%{NUMBER})?)(\"?,?\s*(?:%{IP}(:%{NUMBER})?))*

Describe a specific use case for the enhancement or feature:

$upstream_addr = "unix:/var/run/php5-fpm.sock"

@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Mar 6, 2022
@aspacca aspacca added the Team:Integrations Label for the Integrations team label Mar 7, 2022
@elasticmachine
Copy link
Collaborator

Pinging @elastic/integrations (Team:Integrations)

@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label Mar 7, 2022
@leweafan
Copy link
Contributor Author

leweafan commented Mar 4, 2023

Suppose new pattern should fix it

UPSTREAM_ADDRESS_LIST: (unix:%{NOTSPACE}|(?:%{IP}(:%{NUMBER})?)("?,?\s*(?:%{IP}(:%{NUMBER})?))*)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Team:Integrations Label for the Integrations team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants