-
Notifications
You must be signed in to change notification settings - Fork 508
[azure] update routing for signinlogs and springcloudlogs #15807
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
base: main
Are you sure you want to change the base?
Conversation
🚀 Benchmarks reportTo see the full report comment with |
|
Hey @mmahacek, thanks for contributing this update! I wonder if we should consider sing-in logs all |
|
The signinlogs pipeline does drop any non "*signinlogs" before processing, so this does make some sense. |
|
While I'm updating routing rules, I notice that the router for integrations/packages/azure/data_stream/events/elasticsearch/ingest_pipeline/default.yml Lines 106 to 110 in 80b9687
But the pipeline for that dataset only keeps two of the values: integrations/packages/azure/data_stream/springcloudlogs/elasticsearch/ingest_pipeline/default.yml Lines 53 to 55 in 80b9687
Should this be updated too? |
This brings the event routing in line with the logic within the signinlogs data stream to only keep these documents.
@zmoog Yeah I think that's probably safer for whatever new signin logs Azure is going to add! |
… into mm/azure-aad-signin
💚 Build Succeeded
History
cc @mmahacek |
| if: 'ctx.tmp_json?.category == "SignInLogs" || ctx.tmp_json?.category == "NonInteractiveUserSignInLogs" || ctx.tmp_json?.category == "ServicePrincipalSignInLogs" || ctx.tmp_json?.category == "ManagedIdentitySignInLogs"' | ||
| # Use same logic as the `signinlogs` stream that drops any document that doesn't end with `SignInLogs`. | ||
| if: 'ctx.tmp_json?.category.endsWith("SignInLogs")' | ||
| # if: 'ctx.tmp_json?.category == "SignInLogs" || ctx.tmp_json?.category == "NonInteractiveUserSignInLogs" || ctx.tmp_json?.category == "ServicePrincipalSignInLogs" || ctx.tmp_json?.category == "MicrosoftServicePrincipalSignInLogs" || ctx.tmp_json?.category == "ManagedIdentitySignInLogs"' |
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.
Remove?
Proposed commit message
Fix for routing Azure signinlogs from Azure AD.
The "Windows Azure Active Directory" resource generates logs with the category
MicrosoftServicePrincipalSignInLogs. When using the Azure Events v2 stream, these are handled as platform logs instead of as signinLogs. This PR adds routing to flag these events as the correct dataset.Checklist
I have verified that all data streams collect metrics or logs.changelog.ymlfile.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 practicesAuthor's Checklist
How to test this PR locally
Ingest data with a
{"category":"MicrosoftServicePrincipalSignInLogs"}and verify the document ends up in the signinlogs dataset.Related issues
Screenshots