-
Notifications
You must be signed in to change notification settings - Fork 671
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
Contour support for Envoy's stats per route #4637
Comments
Any plan for this feature support? |
Seems reasonable to support with a few considerations:
We would definitely take community contributions to help speed this up, otherwise we've got this prioritized for 1.24.0 currently |
The Contour project currently lacks enough contributors to adequately respond to all Issues. This bot triages Issues according to the following rules:
You can:
Please send feedback to the #contour channel in the Kubernetes Slack |
We are planning to do tests for this feature, update later. |
The Contour project currently lacks enough contributors to adequately respond to all Issues. This bot triages Issues according to the following rules:
You can:
Please send feedback to the #contour channel in the Kubernetes Slack |
Merry Christmas to guys, if any discussion need, let's going on. |
The Contour project currently lacks enough contributors to adequately respond to all Issues. This bot triages Issues according to the following rules:
You can:
Please send feedback to the #contour channel in the Kubernetes Slack |
Sorry for the lack of responses on this one @wilsonwu will try to look at this again soon! |
Thanks Sunjay, if the test result acceptable, we can move on for some design work. |
Hi guys, let's going on, @sunjayBhatia, any update for this. |
@wilsonwu I'm going to add this to the 1.26 milestone for now and will plan to look at it after 1.25 is released at the end of this month. |
Good to hear that, we will starting contribute it. |
Considering this feature has not been implemented yet, I wonder if there's an alternative option to monitor aggregated traffic of a HTTPProxy/Ingress in contour? envoy metrics show the traffic of each backend pod and I can't see an easy way to relate them to a specified HTTPProxy/Ingress object especially if multiple HTTPProxy/Ingress objects point to the same service/pods |
@wilsonwu sorry this is so late but when doing the experiment above, did you use a static stat prefix for all routes associated with a virtualhost or do something similar to what is described here: #5535 (comment) ? Naively I'm thinking a static stat prefix would have less resource impact and also not offer the granularity needed to actually differentiate the stats between different routes on a route/upstream |
Sorry for the late reply, already comment in the PR. |
per the ongoing discussion on the related PR, looks like this will slip to 1.27.0 |
I am running into this issue, I want to map and filter incoming vs. outgoing traffic, potentially by route. I would be up for reviving #5535, extended it for One thing that I am unsure is how to tag the routes in the |
Please describe the problem you have
At envoyproxy/envoy#3351 @stevesloka advise envoy to expose metrics per vhost, now this feature has been released along with envoy v1.23 as route-stat-prefix (the pr is envoyproxy/envoy#21302), shall we want to support it too?
The text was updated successfully, but these errors were encountered: