-
Notifications
You must be signed in to change notification settings - Fork 7.6k
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
How to Include GRPC Status Codes in Envoy Access Logs? #15358
Comments
@douglas-reid @kyessenov this is related to the grpc resp code metric. |
@mandarjog @douglas-reid @kyessenov How do I use the GRPC response code metric in this particular case? |
Have you asked on the envoyproxy.slack.com channel? |
@hanoisteve I dont have access to it... |
Ok, I asked them. I will see what they say. I agree GRPC support is high priority. |
@hanoisteve @crockeo @junr03 @mattklein123 How do I apply this into my configuration? |
Hello, may be it will help you: My environment: openshift(3.11)+istio(maistra project)+app(front http + backend grpc microservices) I was looking for configuration options to return http response code relative to grpc status code and here that works for me: istio-system project: requestcount manifest: after checking docs i found list of attributes that can produce envoy: i append this field to spec.demensions after that in mixer logs some warning and error logs happend , but after that i also edit one more thing $ oc get handlers -n istio-system oc edit handlers prometheus -n istio-system after that in prometheus server in istio-system project i get new label for metric after that we change metrics response_code demension with this expression and response_code expects int64.. mapping grpc to http we found here this all work for us, hope it help you
|
🚧 This issue or pull request has been closed due to not having had activity from an Istio team member since 2019-07-08. If you feel this issue or pull request deserves attention, please reopen the issue. Please see this wiki page for more information. Thank you for your contributions. Created by the issue and PR lifecycle manager. |
Hello, I'm relatively new to Istio and I would like a feature where the istio-proxy logs are able to show the GRPC status codes.
Now my dilemma here is that Envoy does not make it clear as to how to add the GRPC status codes to the Format String - HTTP and TCP are documented.
https://www.envoyproxy.io/docs/envoy/latest/configuration/access_log#format-rules
In this link ^ format string I want to be able to use GRPC status codes.
https://preliminary.istio.io/docs/tasks/telemetry/logs/access-log/
This link tells me that I need the change the values file but I am unsure of how the values file should be like, and how the config map should be edited.
How to Include GRPC Status Codes in Envoy Access Logs?
Is there a simple way to do this?
The end goal is to use the GRPC status code in the logging and monitoring setup - the requirement from the team is to have the status code displayed in the logs.
Config File included for reference
https://raw.githubusercontent.com/istio/istio/master/install/kubernetes/helm/istio/templates/configmap.yaml
Describe alternatives you've considered
Affected product area (please put an X in all that apply)
[X] Configuration Infrastructure
[X] Docs
[X] Installation
[X] Networking
[X] Performance and Scalability
[X] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Additional context
The text was updated successfully, but these errors were encountered: