Emit metrics on execution time of BBR plugins#2379
Emit metrics on execution time of BBR plugins#2379k8s-ci-robot merged 1 commit intokubernetes-sigs:mainfrom
Conversation
✅ Deploy Preview for gateway-api-inference-extension ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
|
|
Welcome @asaadbalum! |
|
Hi @asaadbalum. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
4b60d55 to
8c15708
Compare
|
/ok-to-test |
| modelHeader = "X-Gateway-Model-Name" | ||
| baseModelHeader = "X-Gateway-Base-Model-Name" | ||
|
|
||
| executeExtensionPoint = "Execute" |
There was a problem hiding this comment.
can we call that "Request"?
we will eventually end up with mirrored picture of plugins, and the extension point marks whether it was executed in the request, or the response.
| executeExtensionPoint = "Execute" | |
| executeExtensionPoint = "Request" |
There was a problem hiding this comment.
Good catch, thanks.
Updated.
8c15708 to
9dcf164
Compare
|
|
||
| "sigs.k8s.io/gateway-api-inference-extension/pkg/bbr/framework" | ||
| "sigs.k8s.io/gateway-api-inference-extension/pkg/bbr/metrics" | ||
| bbrplugins "sigs.k8s.io/gateway-api-inference-extension/pkg/bbr/plugins" |
There was a problem hiding this comment.
nit: can we remove the bbrplugins alias?
plugins in the context of bbr code are always bbr plugins
There was a problem hiding this comment.
@nirrozenbaum
yes, absolutely.
Modified.
|
/lgtm holding in case you want to fix the nit, if not please unhold. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: asaadbalum, nirrozenbaum The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Add plugin processing latency histogram (bbr_plugin_duration_seconds) mirroring the EPP pattern. Instrument executePlugins() to record per-plugin execution time with extension_point, plugin_type, and plugin_name labels. Signed-off-by: asaadbalum <asaad.balum@gmail.com>
9dcf164 to
d48fddb
Compare
|
/retest |
|
/unhold |
|
/lgtm Thanks! 🙏🏼 |
Add plugin processing latency histogram (bbr_plugin_duration_seconds) mirroring the EPP pattern. Instrument executePlugins() to record per-plugin execution time with extension_point, plugin_type, and plugin_name labels. Signed-off-by: asaadbalum <asaad.balum@gmail.com>
Add plugin processing latency histogram (bbr_plugin_duration_seconds) mirroring the EPP pattern. Instrument executePlugins() to record per-plugin execution time with extension_point, plugin_type, and plugin_name labels. Signed-off-by: asaadbalum <asaad.balum@gmail.com>
What type of PR is this?
/kind feature
What this PR does / why we need it:
Adds observability for BBR plugin execution latencies by introducing a
bbr_plugin_duration_secondshistogram metric. This mirrors the existingEPP
inference_extension_plugin_duration_secondsmetric and enablesidentification of performance bottlenecks caused by specific BBR plugins.
Each plugin execution in the request path is timed and recorded with
extension_point,plugin_type, andplugin_namelabels, using thesame bucket boundaries as the EPP equivalent.
Which issue(s) this PR fixes:
Fixes #2355
Does this PR introduce a user-facing change?:
NONE