[azure logs] use one input + routing for all data streams (WIP) #11432
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed commit message
Switch the integration package from the one-input-per-data-stream model to the one-input model.
One input per data stream model:
One input model:
In the one-input model, there is only one azure-eventhub input running and sending events to the
events
data stream. In theevents
data stream, the ingest pipeline performs these tasks:event.dataset
field using thecategory
field in the event.event.dataset
field to reroute the event to the target data stream.The discover process uses the following logic:
event.dataset
toazure.eventhub
(the generic integration)event.dataset
toazure.platformlogs
(it's probably an Azure log)event.dataset
to specific one likeazure.activitylogs
orazure.signinlogs
.After the discovery step, the routing rules use the
event.dataset
value to forward the events to the best available target data stream.Checklist
changelog.yml
file.Author's Checklist
How to test this PR locally
Related issues
Screenshots