-
Notifications
You must be signed in to change notification settings - Fork 219
CF PCAP #1092
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
base: develop
Are you sure you want to change the base?
CF PCAP #1092
Conversation
f0890f1 to
59ff62d
Compare
|
cloudfoundry/archiver#74 got merged and consumed in diego-release, dropped the commit and force-pushed. Now I only need to fix the BOSH blob. |
|
@maxmoehl , @geofffranks, and I chatted in a zoom. The outcome was...
|
59ff62d to
9eb66ca
Compare
Depends on this being merged.
|
9eb66ca to
490538c
Compare
|
I've adjusted the code to use the libpcap from the bosh blob and rebased on the latest |
Summary
This is the implementation of RFC 0048 / #1076.
In its current state the PR cannot be merged (and will be a draft PR for now) as there are two hacks left which have to be cleaned up:
autogen.shwas causing issues down the line. Either we add the libpcap release tar-ball as a blob or fix the autogen.The PR can be built into a release and deployed. To test the feature you can SSH into an app that was deployed after the change has been deployed and then observe traffic like this:
This will print the HTTP traffic to the app process in plain-text to your terminal (while being safely escaped by tcpdump which is not the case for raw output from cf-pcap).
I'm looking for some early feedback on the changes so feel free to leave a review!
Backward Compatibility
Breaking Change? No
Disclaimer: The development of this PR was supported by Claude Code.