-
Notifications
You must be signed in to change notification settings - Fork 4
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
metrics: Policy Attachment metrics (investigate/proof of concept) #4
Comments
@guicassolato @alexsnaps Would you have an example AuthPolicy and RateLimitPolicy for reference here (v2 I guess)? Thanks, I'd really appreciate it. |
These are the most up-to-date examples of AuthPolicy and RateLimitPolicy v2 I can think of now, @david-martin:
TBH, I'm not sure how helpful the status stanza of these CRs can be as of today. But we do have some work in the roadmap to get them enhanced soon – certainly along the lines of what's proposed in Kuadrant/architecture#9, but also open to suggestions. Meanwhile, and at least for Authorino only, maybe there's sth here that we could use:
While the AuthConfigs and the AuthPolicies relate 1:1 one another, the status of the AuthConfig CRs, as well as their so-called associated "deep metrics", will certainly influence the status and the metrics of the AuthPolicies. Perhaps not so much regarding the Policy Attachment aspect of the AuthPolicies directly, but other observable aspects for sure. And, by transition, even the Policy Attachment part may end up affected, I reckon. E.g.: "HTTPRouteRule X is generating too much latency due to an associated config in the auth policy that make requests to this route to fetch metadata from an external source, without setting proper caching." (If that makes any sense.) |
I don't see metrics related to Kuadrant's AuthPolicy introduced in #36. Do we want to reopen this issue or capture what we missed in a new one? |
Good catch @guicassolato |
How can/Does it make sense to support state metrics for Policies that have been attached via https://gateway-api.sigs.k8s.io/references/policy-attachment/?
What's the impact on:
Would an example or 'how-to' make more sense if it's not reasonable to solve this in a generic way?
The text was updated successfully, but these errors were encountered: