Update netflow.yml

[wolfwander]

Adds the hablity to choose a different pipeline to ingest NetFlow logs using the config module file netflow.yml.
Sometimes, you need to choose a different or customized Ingest Pipeline according to the Fileabet instance that is receiving the Netflow data.
I found that, if you costumize the default Netflow Ingest Pipeline, the Filebeat instance overwrites it every week or two with de default configuration for Netflow Ingest Pipeline using the file pipeline.yml and this behavior happens even if you set filebeat.overwrite_pipelines: false in main filebeat.yml.
Setting a different Ingest Pipeline is workaround for that issue.

[cla-checker-service[bot]]

❌ Author of the following commits did not sign a Contributor Agreement: b26727cc97c39998a0ac83d2847cf8db9b12fee3

Please, read and sign the above mentioned agreement if you want to contribute to this project

[botelastic[bot]]

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

[elasticmachine]

:grey_exclamation: Build Aborted

The PR is not allowed to run in the CI yet

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2023-10-19T12:54:48.862+0000

• Duration: 7 min 47 sec

Steps errors

Expand to view the steps failures

Load a resource file from a library

• Took 0 min 0 sec . View more details here
• Description: approval-list/elastic/beats.yml

Error signal

• Took 0 min 0 sec . View more details here
• Description: githubApiCall: The REST API call https://api.github.com/orgs/elastic/members/wolfwander return the message : java.lang.Exception: httpRequest: Failure connecting to the service https://api.github.com/orgs/elastic/members/wolfwander : httpRequest: Failure connecting to the service https://api.github.com/orgs/elastic/members/wolfwander : Code: 404Error: {"message":"User does not exist or is not a member of the organization","documentation_url":"https://docs.github.com/rest/orgs/members#check-organization-membership-for-a-user"}

:robot: 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!)