-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Error ingesting Office 365 events due to invalid IP address field #18587
Comments
Pinging @elastic/siem (Team:SIEM) |
adriansr
added a commit
to adriansr/beats
that referenced
this issue
May 15, 2020
The O365 Management API is generating some events that contain a `ClientIP` / `ClientIPAddress` field consisting of an IPv4 address enclosed in square brackets. This is breaking ingestion of those events as the brackets are only stripped for IPv6 addresses. > "ClientIP": "[10.11.12.13]:12345" This patch adds support for IPv4 enclosed in brackets and a few other edge cases. Fixes elastic#18587
6 tasks
adriansr
added a commit
that referenced
this issue
May 16, 2020
The O365 Management API is generating some events that contain a `ClientIP` / `ClientIPAddress` field consisting of an IPv4 address enclosed in square brackets. This is breaking ingestion of those events as the brackets are only stripped for IPv6 addresses. > "ClientIP": "[10.11.12.13]:12345" This patch adds support for IPv4 enclosed in brackets and a few other edge cases. Fixes #18587
adriansr
added a commit
to adriansr/beats
that referenced
this issue
May 16, 2020
The O365 Management API is generating some events that contain a `ClientIP` / `ClientIPAddress` field consisting of an IPv4 address enclosed in square brackets. This is breaking ingestion of those events as the brackets are only stripped for IPv6 addresses. > "ClientIP": "[10.11.12.13]:12345" This patch adds support for IPv4 enclosed in brackets and a few other edge cases. Fixes elastic#18587 (cherry picked from commit eaf196d)
6 tasks
adriansr
added a commit
to adriansr/beats
that referenced
this issue
May 16, 2020
The O365 Management API is generating some events that contain a `ClientIP` / `ClientIPAddress` field consisting of an IPv4 address enclosed in square brackets. This is breaking ingestion of those events as the brackets are only stripped for IPv6 addresses. > "ClientIP": "[10.11.12.13]:12345" This patch adds support for IPv4 enclosed in brackets and a few other edge cases. Fixes elastic#18587 (cherry picked from commit eaf196d)
6 tasks
adriansr
added a commit
to adriansr/beats
that referenced
this issue
May 16, 2020
The O365 Management API is generating some events that contain a `ClientIP` / `ClientIPAddress` field consisting of an IPv4 address enclosed in square brackets. This is breaking ingestion of those events as the brackets are only stripped for IPv6 addresses. > "ClientIP": "[10.11.12.13]:12345" This patch adds support for IPv4 enclosed in brackets and a few other edge cases. Fixes elastic#18587 (cherry picked from commit eaf196d)
6 tasks
adriansr
added a commit
that referenced
this issue
May 18, 2020
…kets (#18601) The O365 Management API is generating some events that contain a `ClientIP` / `ClientIPAddress` field consisting of an IPv4 address enclosed in square brackets. This is breaking ingestion of those events as the brackets are only stripped for IPv6 addresses. > "ClientIP": "[10.11.12.13]:12345" This patch adds support for IPv4 enclosed in brackets and a few other edge cases. Fixes #18587 (cherry picked from commit eaf196d)
adriansr
added a commit
that referenced
this issue
May 18, 2020
…kets (#18603) The O365 Management API is generating some events that contain a `ClientIP` / `ClientIPAddress` field consisting of an IPv4 address enclosed in square brackets. This is breaking ingestion of those events as the brackets are only stripped for IPv6 addresses. > "ClientIP": "[10.11.12.13]:12345" This patch adds support for IPv4 enclosed in brackets and a few other edge cases. Fixes #18587 (cherry picked from commit eaf196d)
adriansr
added a commit
that referenced
this issue
May 18, 2020
…kets (#18602) The O365 Management API is generating some events that contain a `ClientIP` / `ClientIPAddress` field consisting of an IPv4 address enclosed in square brackets. This is breaking ingestion of those events as the brackets are only stripped for IPv6 addresses. > "ClientIP": "[10.11.12.13]:12345" This patch adds support for IPv4 enclosed in brackets and a few other edge cases. Fixes #18587 (cherry picked from commit eaf196d)
leweafan
pushed a commit
to leweafan/beats
that referenced
this issue
Apr 28, 2023
…re brackets (elastic#18603) The O365 Management API is generating some events that contain a `ClientIP` / `ClientIPAddress` field consisting of an IPv4 address enclosed in square brackets. This is breaking ingestion of those events as the brackets are only stripped for IPv6 addresses. > "ClientIP": "[10.11.12.13]:12345" This patch adds support for IPv4 enclosed in brackets and a few other edge cases. Fixes elastic#18587 (cherry picked from commit 6f35860)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For confirmed bugs, please report:
Some (Exchange audit?) events from Office 365 Management API are causing an ingestion error due to an invalid IP address field (
client.ip
, maybe others).The important error messages being:
and
Caused by the following fields in the original O365 event:
The text was updated successfully, but these errors were encountered: