-
Notifications
You must be signed in to change notification settings - Fork 464
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
microsoft_exchange_online_message_trace - handle SenderAddress of '<>' #12292
microsoft_exchange_online_message_trace - handle SenderAddress of '<>' #12292
Conversation
0cd7fa4
to
3487fb3
Compare
In the microsoft_exchange_online_message_trace integration, JSON events containing "SenderAddress":"<>" caused a pipeline error of Provided Grok expressions do no match field value: [<>] This commit changes the pipeline to treat the value that same as it would an empty string or no SenderAddress field present. Improve the pipeline error.message by including more details about the processor that is failing.
3487fb3
to
e53e49c
Compare
Pinging @elastic/security-service-integrations (Team:Security-Service Integrations) |
🚀 Benchmarks reportTo see the full report comment with |
...soft_exchange_online_message_trace/data_stream/log/elasticsearch/ingest_pipeline/default.yml
Show resolved
Hide resolved
...soft_exchange_online_message_trace/data_stream/log/elasticsearch/ingest_pipeline/default.yml
Show resolved
Hide resolved
...soft_exchange_online_message_trace/data_stream/log/elasticsearch/ingest_pipeline/default.yml
Show resolved
Hide resolved
…nline_message_trace/bugfix/sender-address
💚 Build Succeeded
History
|
Quality Gate passedIssues Measures |
Package microsoft_exchange_online_message_trace - 1.25.2 containing this change is available at https://epr.elastic.co/package/microsoft_exchange_online_message_trace/1.25.2/ |
Proposed commit message
Checklist
changelog.yml
file.