Conversation
kaiyan-sheng
approved these changes
Aug 19, 2025
🚀 Benchmarks reportPackage
|
| Data stream | Previous EPS | New EPS | Diff (%) | Result |
|---|---|---|---|---|
auditlogs |
2053.39 | 1322.75 | -730.64 (-35.58%) | 💔 |
platformlogs |
4524.89 | 3703.7 | -821.19 (-18.15%) | 💔 |
To see the full report comment with /test benchmark fullreport
Contributor
|
@zmoog - Can we add changelog entry? |
packages/azure/data_stream/platformlogs/elasticsearch/ingest_pipeline/default.yml
Outdated
Show resolved
Hide resolved
Contributor
Author
Added. |
# Conflicts: # packages/azure/changelog.yml
d839754 to
6bcdff3
Compare
💚 Build Succeeded
History
cc @zmoog |
|
muthu-mps
approved these changes
Aug 20, 2025
Contributor
muthu-mps
left a comment
There was a problem hiding this comment.
- As we are using sample event from
FunctionappLogscategory for validations. Is there a possibility to get different response format for other categories? - Change looks good to me!
Contributor
Author
I confirm Azure is sending the same invalid field names ( 
|
|
Package azure - 1.28.4 containing this change is available at https://epr.elastic.co/package/azure/1.28.4/ |
tehbooom
pushed a commit
to tehbooom/integrations
that referenced
this pull request
Nov 19, 2025
…e ISV (elastic#14961) Renames the field names coming from the Azure Native ISV from the current names to the expected names: | Current | Expected | |--------|--------| | `dataStream` | `data_stream` | | `azureLogForwarder` | `azure_log_forwarder` | | `timestamp` | `@timestamp` | It seems that Azure updated their Elasticsearch client, but they probably missed mapping the above field to the expected names we were using before. While we wait for a proper fix on the Azure side, we are shipping this workaround.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
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
Renames the field names coming from the Azure Native ISV from the current names to the expected names:
dataStreamdata_streamazureLogForwarderazure_log_forwardertimestamp@timestampIt seems that Azure updated their Elasticsearch client, but they probably missed mapping the above field to the expected names we were using before.
While we wait for a proper fix on the Azure side, we are shipping this workaround.
Checklist
changelog.ymlfile.I have verified that any added dashboard complies with Kibana's Dashboard good practices