We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
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"
The text was updated successfully, but these errors were encountered:
Pinging @elastic/integrations (Team:Integrations)
Sorry, something went wrong.
Suppose new pattern should fix it
UPSTREAM_ADDRESS_LIST: (unix:%{NOTSPACE}|(?:%{IP}(:%{NUMBER})?)("?,?\s*(?:%{IP}(:%{NUMBER})?))*)
Successfully merging a pull request may close this issue.
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:
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"
The text was updated successfully, but these errors were encountered: