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.

Sign up for GitHub

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

Jump to bottom

Decouple connection polling and conntrack occupancy metrics from the flow exporter implementation #1278

Closed
dreamtalen opened this issue Sep 21, 2020 · 1 comment
Closed

Decouple connection polling and conntrack occupancy metrics from the flow exporter implementation #1278

dreamtalen opened this issue Sep 21, 2020 · 1 comment
Assignees
@heanlan
Labels
area/monitoring/traffic-analysis Issues or PRs related to traffic analysis. good first issue Good for newcomers kind/feature Categorizes issue or PR as related to a new feature. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@dreamtalen
Copy link
Contributor

Describe the problem/challenge you have
As mentioned in PR #1232, we want to decouple the conntrack occupancy metrics and connection polling from the flow exporter implementation. Currently, it is not straightforward to decouple both polling and flow export mechanisms. They are both enabled through FlowExporter feature gate and we expect flowCollectorAddr as a must given parameter.

Describe the solution you'd like
We could finish the decoupling by either moving polling from the FlowExporter feature gate or changing the name of the feature gate to a more appropriate name and removing the dependency on flowCollectorAddr.
@dreamtalen dreamtalen added the kind/feature Categorizes issue or PR as related to a new feature. label Sep 21, 2020
@srikartati srikartati added the area/monitoring/traffic-analysis Issues or PRs related to traffic analysis. label Sep 26, 2020
@antoninbas antoninbas added the good first issue Good for newcomers label Oct 12, 2020
@srikartati srikartati added this to the Antrea v0.14.0 release milestone Feb 12, 2021
@zyiou zyiou removed this from the Antrea v1.0 release milestone Mar 30, 2021
@zyiou zyiou mentioned this issue Mar 31, 2021
Merged
@github-actions
Copy link
Contributor

This issue is stale because it has been open 180 days with no activity. Remove stale label or comment, or this will be closed in 180 days

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 27, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@heanlan heanlan

Labels
area/monitoring/traffic-analysis Issues or PRs related to traffic analysis. good first issue Good for newcomers kind/feature Categorizes issue or PR as related to a new feature. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@antoninbas @dreamtalen @srikartati @zyiou @heanlan