fix(adapter): start pprof server when profiling is enabled#9008
fix(adapter): start pprof server when profiling is enabled#9008theakshaypant wants to merge 1 commit intoknative:mainfrom
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: theakshaypant The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
|
|
Welcome @theakshaypant! It looks like this is your first PR to knative/eventing 🎉 |
|
Hi @theakshaypant. Thanks for your PR. I'm waiting for a knative member to verify that this patch is reasonable to test. If it is, they should reply with Regular contributors should join the org to skip this step. 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. |
|
/ok-to-test |
|
I went through the logs from some of the failed tests and see error messages around TLS which I would guess is more of an infra issue rather than related to the PR changes. 🤔 |
Oh yes. Seems it needs #9009 |
The eventing adapter framework creates and configures a ProfilingServer but never calls ListenAndServe, so the profiling port is never bound even when runtime-profiling is set to enabled in the observability ConfigMap. Start the server conditionally based on the initial config, consistent with the adapter's static observability config model. Fixes knative#9007 Signed-off-by: Akshay Pant <akpant@redhat.com>
cf53275 to
add28c2
Compare
Rebased with 9009 changes. |
|
@theakshaypant: The following test failed, say
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. I understand the commands that are listed here. |
Fixes #9007
Proposed Changes
The eventing adapter framework creates and configures a ProfilingServer but never calls ListenAndServe, so the profiling port is never bound even when runtime-profiling is set to enabled in the observability ConfigMap. Start the server conditionally based on the initial config, consistent with the adapter's static observability config model.
Pre-review Checklist
Release Note
Docs
Testing
My testing might have been limited to the use-case I was trying when I first ran into the original issue.
Covered three test scenarios:
PROFILING_PORT=8090- able to access the profiling endpoints on port 8090.