[New Package] UDP Input

[P1llus]

What does this PR do?

This package adds the possibility to configure your own custom UDP input, allowing users to add custom integrations that might not already be covered by an existing package.

Tested with 7.16 and 8.0

Checklist

• I have reviewed tips for building integrations and this pull request is aligned with them.
• I have verified that all data streams collect metrics or logs.
• I have added an entry to my package's changelog.yml file.
• If I'm introducing a new feature, I have modified the Kibana version constraint in my package's manifest.yml file to point to the latest Elastic stack release (e.g. ^7.13.0).

[elasticmachine]

Pinging @elastic/integrations (Team:Integrations)

[elasticmachine]

Pinging @elastic/security-external-integrations (Team:Security-External Integrations)

[elasticmachine]

💚 Build Succeeded

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: 2021-11-19T07:18:14.590+0000

• Duration: 12 min 0 sec

• Commit: 43ab5e0

Test stats 🧪

Test	Results
Failed	0
Passed	3
Skipped	0
Total	3

🤖 GitHub comments

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

• /test : Re-trigger the build.

[zez3]

Was there not already decided to include the user selectable option to keep the original message on all integrations?

[P1llus]

Was there not already decided to include the user selectable option to keep the original message on all integrations?

Sure thing @zez3 .

Since these are pure input packages, the incoming data is always the raw format, it is up to the end-user to parse/transform the data in the way that they want, and are then also free to keep the original.

[endorama]

👍 on title and description!

[zez3]

Was there not already decided to include the user selectable option to keep the original message on all integrations?

Sure thing @zez3 .

Since these are pure input packages, the incoming data is always the raw format, it is up to the end-user to parse/transform the data in the way that they want, and are then also free to keep the original.

But the commit 1b5dec1

removes the original message? Or am I missing something here

[P1llus]

Was there not already decided to include the user selectable option to keep the original message on all integrations?

Sure thing @zez3 .
Since these are pure input packages, the incoming data is always the raw format, it is up to the end-user to parse/transform the data in the way that they want, and are then also free to keep the original.

But the commit 1b5dec1

removes the original message? Or am I missing something here

Hello @zez3 . That is because when I make packages I simply copy/paste an existing package usually. The input only packages do not need this part, as it will always come in raw.
That setting is not for the input to keep the original, is for the ingest pipelines to make sure to leave a copy of the original event before it starts modifying it.