fix(metricbeat): report correct number of entries in conntrack metricset

[mauri870]

Proposed commit message

The conntrack metricset was summing the entries value across all CPUs, but this field is identical on each line of /proc/net/stat/nf_conntrack. As a result, the reported count was inflated by a factor of the number of CPU cores.

This fixes the issue by reading the entries value only once.

Checklist

• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have made corresponding change to the default configuration files
• I have added tests that prove my fix is effective or that my feature works
• I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Related issues

• Fixes metricbeat: conntrack metricset reports inflated entries count #46138

[github-actions]

🤖 GitHub comments

Expand to view the GitHub comments

Just comment with:

• run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)

[mergify]

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @mauri870? 🙏.
For such, you'll need to label your PR with:

• The upcoming major version of the Elastic Stack
• The upcoming minor version of the Elastic Stack (if you're not pushing a breaking change)

To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-8./d is the label to automatically backport to the 8./d branch. /d is the digit
• backport-active-all is the label that automatically backports to all active branches.
• backport-active-8 is the label that automatically backports to all active minor branches for the 8 major.
• backport-active-9 is the label that automatically backports to all active minor branches for the 9 major.

[elasticmachine]

Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane)

[mergify]

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b conntrack-entries upstream/conntrack-entries
git merge upstream/main
git push upstream conntrack-entries

[mauri870]

@andrzej-stencel @faec Quick reminder for review when you have a moment.

[github-actions]

@Mergifyio backport 8.17 8.18 8.19 9.0 9.1

[mergify]

backport 8.17 8.18 8.19 9.0 9.1

✅ Backports have been created

Details

• #46235 [8.17](backport #46140) fix(metricbeat): report correct number of entries in conntrack metricset has been created for branch 8.17
• #46236 [8.18](backport #46140) fix(metricbeat): report correct number of entries in conntrack metricset has been created for branch 8.18
• #46237 [8.19](backport #46140) fix(metricbeat): report correct number of entries in conntrack metricset has been created for branch 8.19
• #46238 [9.0](backport #46140) fix(metricbeat): report correct number of entries in conntrack metricset has been created for branch 9.0
• #46239 [9.1](backport #46140) fix(metricbeat): report correct number of entries in conntrack metricset has been created for branch 9.1