Skip to content
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

Do we plan to support inbound traffic parsing? #105

Open
wenhuwang opened this issue Jul 5, 2024 · 4 comments
Open

Do we plan to support inbound traffic parsing? #105

wenhuwang opened this issue Jul 5, 2024 · 4 comments

Comments

@wenhuwang
Copy link
Contributor

Currently, coroot-node-agent only parses network packets that the current node service actively requests for other services. However, in many scenarios, coroot-node-agent cannot be deployed to all nodes. Can it support parsing network packets requested by external services to build a more complete service topology?

@def
Copy link
Member

def commented Jul 5, 2024

Yes, we have plans to implement this. Here is a similar issue in the main repo: coroot/coroot#281

@wenhuwang
Copy link
Contributor Author

How is the progress of this feature? I am interested in this feature and would like to contribute if possible.

@gravese
Copy link

gravese commented Aug 15, 2024

Is has any new progress of this feature?

@StLeoX
Copy link

StLeoX commented Jan 17, 2025

StLeoX@667b19c

Here I design l7_event's corresponding in-bound traffic l7_event_ss (ss means server-side, current process working as the server). But I meet the problem, I can't filter l7_event_ss by active TCP connections and FDs correctly.
Anyone could give me some advice? @wenhuwang @gravese

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants