[azure logs] Add processor version options to Raw Events integration (v1) #15900
+109
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
zmoog
added
Integration:azure
🚀 Benchmarks reportTo see the full report comment with |
muthu-mps
reviewed
Nov 7, 2025
|
|
||
| # Encoding extension | ||
| - rename: | ||
| field: body.structured |
Contributor
There was a problem hiding this comment.
Why does this field renamed only for activity_logs? Should the body.structured needs to be renamed in other data streams like sign-in logs, graph_activity logs as well?
Contributor
Author
There was a problem hiding this comment.
My bad. I included a couple of things that don't belong here 🤦 I'll clean up the commits.
andrewkroh
added
the
Team:Obs-InfraObs
zmoog
force-pushed
the
integrations-raw-events-v2
branch
from
63f959e to
1bc4092
Compare
zmoog
force-pushed
the
integrations-raw-events-v2
branch
from
1bc4092 to
d5e9f6a
Compare
💚 Build Succeeded
History
cc @zmoog |
kaiyan-sheng
reviewed
Nov 7, 2025
Comment on lines
+78
to
+88
| # | ||
| # Processor v2 only settings | ||
| # | ||
| - name: processor_version | ||
| type: text | ||
| title: Processor version | ||
| multi: false | ||
| required: false | ||
| show_user: false | ||
| default: v1 | ||
| description: "The processor version that the integration should use. Possible values are `v1` and `v2` (preview). \nThe v2 event hub processor is in preview, so using the v1 processor is recommended for typical use cases.\nDefault is `v1`." |
Contributor
There was a problem hiding this comment.
Suggested change
| # | |
| # Processor v2 only settings | |
| # | |
| - name: processor_version | |
| type: text | |
| title: Processor version | |
| multi: false | |
| required: false | |
| show_user: false | |
| default: v1 | |
| description: "The processor version that the integration should use. Possible values are `v1` and `v2` (preview). \nThe v2 event hub processor is in preview, so using the v1 processor is recommended for typical use cases.\nDefault is `v1`." | |
| - name: processor_version | |
| type: text | |
| title: Processor version | |
| multi: false | |
| required: false | |
| show_user: false | |
| default: v1 | |
| description: "The processor version that the integration should use. Possible values are `v1` and `v2` (preview). \nThe v2 event hub processor is in preview, so using the v1 processor is recommended for typical use cases.\nDefault is `v1`." | |
| # | |
| # Processor v2 only settings | |
| # |
Suggested change
| # | |
| # Processor v2 only settings | |
| # | |
| - name: processor_version | |
| type: text | |
| title: Processor version | |
| multi: false | |
| required: false | |
| show_user: false | |
| default: v1 | |
| description: "The processor version that the integration should use. Possible values are `v1` and `v2` (preview). \nThe v2 event hub processor is in preview, so using the v1 processor is recommended for typical use cases.\nDefault is `v1`." | |
| # | |
| # Processor v2 only settings | |
| # | |
| - name: processor_version | |
| type: text | |
| title: Processor version | |
| multi: false | |
| required: false | |
| show_user: false | |
| default: v1 | |
| description: "The processor version that the integration should use. Possible values are `v1` and `v2` (preview). \nThe v2 event hub processor is in preview, so using the v1 processor is recommended for typical use cases.\nDefault is `v1`." |
kaiyan-sheng
reviewed
Nov 7, 2025
Contributor
kaiyan-sheng
left a comment
kaiyan-sheng
left a comment
There was a problem hiding this comment.
It looks good to me! Lets add a changelog and it's good to go!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
Add the processor version option to the Raw Events integration v1. With these new options, users can switch from processor v1 (current default) to the processor v2.
This change anticipate the switch to v2 as default processor.
Checklist
changelog.ymlfile.I have verified that any added dashboard complies with Kibana's Dashboard good practicesHow to test this PR locally
v2Screenshots