[azure] update routing for signinlogs and springcloudlogs#15807
[azure] update routing for signinlogs and springcloudlogs#15807
Conversation
🚀 Benchmarks reportPackage
|
| Data stream | Previous EPS | New EPS | Diff (%) | Result |
|---|---|---|---|---|
signinlogs |
2583.98 | 2004.01 | -579.97 (-22.44%) | 💔 |
springcloudlogs |
8064.52 | 5464.48 | -2600.04 (-32.24%) | 💔 |
eventhub |
500000 | 250000 | -250000 (-50%) | 💔 |
identity_protection |
6666.67 | 4784.69 | -1881.98 (-28.23%) | 💔 |
platformlogs |
5263.16 | 4273.5 | -989.66 (-18.8%) | 💔 |
To see the full report comment with /test benchmark fullreport
|
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 But the pipeline for that dataset only keeps two of the values: 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
packages/azure/data_stream/events/elasticsearch/ingest_pipeline/default.yml
Outdated
Show resolved
Hide resolved
|
😅 Another update came in for this integration. Pushing a version bump - should be no other functional changes. |
|
@elastic/obs-ds-hosted-services This is ready for a code owners approval. Thanks in advance! |
|
Any update here guys? My org is the one who reported this and needs it resolved. |
|
Still waiting for this to be merged. |
|
#16538 which I have added adds another source type for a SignInLog. Can modify my PR after this is merged to only add the new fields. |
💚 Build Succeeded
History
cc @mmahacek |
|
Package azure - 1.32.0 containing this change is available at https://epr.elastic.co/package/azure/1.32.0/ |
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