-
Notifications
You must be signed in to change notification settings - Fork 360
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
docs: Observability of Envoy Gateway Component (not Envoy) #3404
Comments
Hi @nezdolik The metrics of EG are still work in progress, tracked by #2092, for now, the latest version has support these metrics:
The usage of EG metrics can refer to: https://gateway.envoyproxy.io/latest/tasks/observability/gateway-observability/
These metrics can refer to: gateway/internal/message/metrics.go Lines 15 to 17 in c5ec046
with different runner label, for example, like:
|
converting this into a docs issue, because these metrics exist, but are not documented |
Done some research, couldn't find any tool like that. Since the metrics is not changed very often, maybe we could write a doc on our own. |
sure @shawnh2, lets start with that |
will file a doc after #3393 landed |
Observability of Envoy Gateway Component (not Envoy):
To have full EG system observability and ease troubleshooting of various failure modes, is there is EG native metrics (not Envoy proxy) that helps to have insights into EG subcomponents like:
Introducing such metrics (if they are not yet supported) will ease EG operators to troubleshoot various failure scenarios and increase confidence for prod deployment.
Could not find mentions of EG native metric in user docs.
The text was updated successfully, but these errors were encountered: