You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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
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?
The text was updated successfully, but these errors were encountered: