-
Notifications
You must be signed in to change notification settings - Fork 474
[azure] Standardize the azure.platformlogs.Identity
field to .identity
#11765
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
.Identity
field to .identity
azure.platform.Identity
field to azure.platform.identity
azure.platform.Identity
field to azure.platform.identity
azure.platformlogs.Identity
field to .identity
🚀 Benchmarks reportPackage
|
Data stream | Previous EPS | New EPS | Diff (%) | Result |
---|---|---|---|---|
signinlogs |
2439.02 | 1956.95 | -482.07 (-19.76%) | 💔 |
springcloudlogs |
5208.33 | 4219.41 | -988.92 (-18.99%) | 💔 |
identity_protection |
4464.29 | 3533.57 | -930.72 (-20.85%) | 💔 |
To see the full report comment with /test benchmark fullreport
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
/test |
|
💚 Build Succeeded
History
cc @zmoog |
Package azure - 1.19.3 containing this change is available at https://epr.elastic.co/package/azure/1.19.3/ |
…tity` (#11765) Renames the field `azure.platformlogs.Identity` to `azure.platformlogs.identity` for consistency. Sometimes users send log categories with an `azure.platformlogs.Identity` to platform logs. Some documents contain `azure.platformlogs.Identity` as a string, while others are as an object, causing mapping exceptions. By renaming `azure.platformlogs.Identity` to `azure.platformlogs.identity` the rest of the pipeline will take care of the string and object cases.
…tity` (elastic#11765) Renames the field `azure.platformlogs.Identity` to `azure.platformlogs.identity` for consistency. Sometimes users send log categories with an `azure.platformlogs.Identity` to platform logs. Some documents contain `azure.platformlogs.Identity` as a string, while others are as an object, causing mapping exceptions. By renaming `azure.platformlogs.Identity` to `azure.platformlogs.identity` the rest of the pipeline will take care of the string and object cases.
…tity` (#11765) Renames the field `azure.platformlogs.Identity` to `azure.platformlogs.identity` for consistency. Sometimes users send log categories with an `azure.platformlogs.Identity` to platform logs. Some documents contain `azure.platformlogs.Identity` as a string, while others are as an object, causing mapping exceptions. By renaming `azure.platformlogs.Identity` to `azure.platformlogs.identity` the rest of the pipeline will take care of the string and object cases.
…tity` (elastic#11765) Renames the field `azure.platformlogs.Identity` to `azure.platformlogs.identity` for consistency. Sometimes users send log categories with an `azure.platformlogs.Identity` to platform logs. Some documents contain `azure.platformlogs.Identity` as a string, while others are as an object, causing mapping exceptions. By renaming `azure.platformlogs.Identity` to `azure.platformlogs.identity` the rest of the pipeline will take care of the string and object cases.
Proposed commit message
Renames the field
azure.platformlogs.Identity
toazure.platformlogs.identity
for consistency.Sometimes users send log categories with an
azure.platformlogs.Identity
to platform logs. Some documents containazure.platformlogs.Identity
as a string, while others are as an object, causing mapping exceptions.By renaming
azure.platformlogs.Identity
toazure.platformlogs.identity
the rest of the pipeline will take care of the string and object cases.Checklist
changelog.yml
file.I have verified that Kibana version constraints are current according to guidelines.I have verified that any added dashboard complies with Kibana's Dashboard good practicesRelated issues