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.

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

[filebeat] add netflow input metrics #38055

Merged

Conversation

pkoutsovasilis
Copy link
Contributor

@pkoutsovasilis pkoutsovasilis commented Feb 19, 2024

Proposed commit message

This PR captures introduces input/netmetrics and extends the netflow input metrics and exposes them per input instance basis

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.

Author's Checklist

How to test this PR locally

Related issues

Use cases

Screenshots

Logs

@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Feb 19, 2024
Copy link
Contributor

mergify bot commented Feb 19, 2024

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @pkoutsovasilis? 🙏.
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-v8./d.0 is the label to automatically backport to the 8./d branch. /d is the digit

@pkoutsovasilis pkoutsovasilis force-pushed the pkoutsovasilis/netflow_metrics branch from cc6073c to fa059a3 Compare February 19, 2024 11:37
@pkoutsovasilis pkoutsovasilis changed the title feat: refactor tcp and udp metrics to allow multiple inputs to incorp… [filebeat] add netflow input metrics Feb 19, 2024
@pkoutsovasilis pkoutsovasilis force-pushed the pkoutsovasilis/netflow_metrics branch 3 times, most recently from 018ad5c to 5068d10 Compare February 19, 2024 21:33
filebeat/input/netmetrics/common.go Outdated Show resolved Hide resolved
filebeat/input/netmetrics/common.go Outdated Show resolved Hide resolved
filebeat/input/netmetrics/procnet.go Outdated Show resolved Hide resolved
filebeat/input/netmetrics/procnet_test.go Outdated Show resolved Hide resolved
filebeat/input/netmetrics/tcp.go Outdated Show resolved Hide resolved
filebeat/input/netmetrics/udp.go Outdated Show resolved Hide resolved
filebeat/input/netmetrics/tcp.go Outdated Show resolved Hide resolved
filebeat/input/netmetrics/udp.go Outdated Show resolved Hide resolved
filebeat/input/tcp/input.go Outdated Show resolved Hide resolved
@pkoutsovasilis pkoutsovasilis force-pushed the pkoutsovasilis/netflow_metrics branch from 5068d10 to 6cf69cb Compare February 20, 2024 09:14
@pkoutsovasilis pkoutsovasilis force-pushed the pkoutsovasilis/netflow_metrics branch from 6cf69cb to 47aea5b Compare February 20, 2024 11:42
@elastic elastic deleted a comment from elasticmachine Feb 20, 2024
@elastic elastic deleted a comment from elasticmachine Feb 20, 2024
@elastic elastic deleted a comment from elasticmachine Feb 20, 2024
@elastic elastic deleted a comment from elasticmachine Feb 20, 2024
@elastic elastic deleted a comment from elasticmachine Feb 20, 2024
@elastic elastic deleted a comment from elasticmachine Feb 20, 2024
@pkoutsovasilis pkoutsovasilis added the Team:Security-Deployment and Devices Deployment and Devices Team in Security Solution label Feb 20, 2024
@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label Feb 20, 2024
@botelastic
Copy link

botelastic bot commented Feb 20, 2024

This pull request doesn't have a Team:<team> label.

@pkoutsovasilis pkoutsovasilis marked this pull request as ready for review February 20, 2024 13:03
@pkoutsovasilis pkoutsovasilis requested review from a team as code owners February 20, 2024 13:03
@elasticmachine
Copy link
Collaborator

Pinging @elastic/sec-deployment-and-devices (Team:Security-Deployment and Devices)

@elasticmachine
Copy link
Collaborator

elasticmachine commented Feb 20, 2024

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview preview

Expand to view the summary

Build stats

  • Start Time: 2024-02-22T14:59:55.857+0000

  • Duration: 138 min 50 sec

Test stats 🧪

Test Results
Failed 0
Passed 8386
Skipped 759
Total 9145

💚 Flaky test report

Tests succeeded.

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

  • /test : Re-trigger the build.

  • /package : Generate the packages and run the E2E tests.

  • /beats-tester : Run the installation tests with beats-tester.

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

filebeat/input/netmetrics/tcp.go Outdated Show resolved Hide resolved
filebeat/input/tcp/input.go Outdated Show resolved Hide resolved
filebeat/input/netmetrics/tcp.go Outdated Show resolved Hide resolved
filebeat/input/netmetrics/udp.go Outdated Show resolved Hide resolved
filebeat/input/netmetrics/udp.go Outdated Show resolved Hide resolved
filebeat/input/netmetrics/tcp.go Outdated Show resolved Hide resolved
Copy link
Member

@andrewkroh andrewkroh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The asciidocs for the netflow input need a new "Metrics" section added. Here's a template you may follow eca6d05

@pkoutsovasilis
Copy link
Contributor Author

The asciidocs for the netflow input need a new "Metrics" section added. Here's a template you may follow eca6d05

Oh nice catch ty @andrewkroh

@pkoutsovasilis
Copy link
Contributor Author

@andrewkroh another question, what do you think should this PR be back-ported? I added backport-skip but I am not entirely sure that was the right choice

@elasticmachine
Copy link
Collaborator

💚 Build Succeeded

History

cc @pkoutsovasilis

@elasticmachine
Copy link
Collaborator

💚 Build Succeeded

History

cc @pkoutsovasilis

@elasticmachine
Copy link
Collaborator

💚 Build Succeeded

History

cc @pkoutsovasilis

@elasticmachine
Copy link
Collaborator

💚 Build Succeeded

History

cc @pkoutsovasilis

@elasticmachine
Copy link
Collaborator

💚 Build Succeeded

History

cc @pkoutsovasilis

@elasticmachine
Copy link
Collaborator

💚 Build Succeeded

History

cc @pkoutsovasilis

@andrewkroh
Copy link
Member

andrewkroh commented Feb 22, 2024

another question, what do you think should this PR be back-ported? I added backport-skip but I am not entirely sure that was the right choice

That's the right choice IMO. This will land in 8.14. It's past the feature freeze for 8.13 so we shouldn't backport unless it's a bugfix or some low-risk, critical feature (like for helping to debug an issue).

@pkoutsovasilis pkoutsovasilis merged commit a0a567c into elastic:main Feb 22, 2024
45 of 48 checks passed
@pkoutsovasilis pkoutsovasilis deleted the pkoutsovasilis/netflow_metrics branch February 22, 2024 22:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport-skip Skip notification from the automated backport with mergify enhancement Filebeat Filebeat Team:Security-Deployment and Devices Deployment and Devices Team in Security Solution
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Filebeat] Netflow input - add input metrics
5 participants