Add conntrack metrics#3624
Conversation
Codecov Report
@@ Coverage Diff @@
## master #3624 +/- ##
==========================================
- Coverage 85.98% 72.6% -13.39%
==========================================
Files 741 7 -734
Lines 39177 449 -38728
Branches 4712 81 -4631
==========================================
- Hits 33688 326 -33362
+ Misses 4196 100 -4096
+ Partials 1293 23 -1270 |
|
Went through the PR quickly, looks good. Looking forward to testing it on our cluster
Maybe we can reach out to the customer and get more info on their use cases? I'm pretty sure they are mostly interested in stats and just |
|
Thanks @lbernail ! Since For the list of metrics in |
zippolyte
left a comment
There was a problem hiding this comment.
A few comments, looking good otherwise
apigirl
left a comment
There was a problem hiding this comment.
approved grammar/style for docs
What does this PR do?
Add conntrack metrics to the network check.
Some metrics are only available with
sudo conntrack -S, so the check is calling the subprocess to have:system.net.conntrack.dropsystem.net.conntrack.early_dropsystem.net.conntrack.errorsystem.net.conntrack.foundsystem.net.conntrack.ignoresystem.net.conntrack.insertsystem.net.conntrack.insert_failedsystem.net.conntrack.invalidsystem.net.conntrack.search_restartThey are tagged by cpu #.
The rest is available in
{proc_location}/sys/net/netfilter/. The most interesting ones aresystem.net.conntrack.countandsystem.net.conntrack.maxenabled by default.Motivation
Customer and internal request.
Additional Notes
Information available since kernel 3.6
Some documentation still need to be done for the different metrics available.
The documentation in the metadata.csv mainly comes from here
cc @lbernail
Review checklist (to be filled by reviewers)
changelog/andintegration/labels attached