-
Notifications
You must be signed in to change notification settings - Fork 24
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
NETOBSERV-691 better document cacheMaxFlows/Timeout (in CRD) #255
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
to be backported in 1.1 |
@skrthomas we should also update the API reference in the documentation; cf the asciidoc file that I regenerated in this PR |
@@ -159,11 +159,11 @@ Type:: | |||
|
|||
| `cacheActiveTimeout` | |||
| `string` | |||
| cacheActiveTimeout is the max period during which the reporter will aggregate flows before sending | |||
| cacheActiveTimeout is the max period during which the reporter will aggregate flows before sending Increasing `cacheMaxFlows` and `cacheActiveTimeout` can decrease the network traffic overhead and the CPU load, however you can expect higher memory consumption and an increased latency in the flow collection. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| cacheActiveTimeout is the max period during which the reporter will aggregate flows before sending Increasing `cacheMaxFlows` and `cacheActiveTimeout` can decrease the network traffic overhead and the CPU load, however you can expect higher memory consumption and an increased latency in the flow collection. | |
| cacheActiveTimeout is the max period during which the reporter will aggregate flows before sending. Increasing `cacheMaxFlows` and `cacheActiveTimeout` can decrease the network traffic overhead and the CPU load, however you can expect higher memory consumption and an increased latency in the flow collection. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just added a period
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thx! I need to amend the PR as there are other files to update
New changes are detected. LGTM label has been removed. |
…rv#255) * NETOBSERV-691 better document cacheMaxFlows/Timeout (in CRD) * Update asciidoc * Fix missing period * fix flaky test
* Add conntrack_memory_connections metric * Add conntrack_input_records operational metric * Add conntrack_output_records operational metric * Refactor
No description provided.