Repository navigation
Allow empty fields in the exchange integration redux - #12846
Conversation
|
Pinging @elastic/security-service-integrations (Team:Security-Service Integrations) |
|
Pinging @elastic/sec-windows-platform (Team:Security-Windows Platform) |
| "email": { | ||
| "from": { | ||
| "address": [ | ||
| "" |
There was a problem hiding this comment.
We don't want the empty string being added to the array.
…/elasticsearch/ingest_pipeline/default.yml Co-authored-by: Andrew Kroh <andrew.kroh@elastic.co>
…/elasticsearch/ingest_pipeline/default.yml Co-authored-by: Andrew Kroh <andrew.kroh@elastic.co>
| "address": [ | ||
| "support@example.com" | ||
| ] | ||
| "address": "support@example.com" |
There was a problem hiding this comment.
Is this supposed to be a list?
There was a problem hiding this comment.
I changed this back to a list, let me know if that is wrong.
| "address": [ | ||
| "root@pve-vhost01.my.domain.com" | ||
| ] | ||
| "address": "root@pve-vhost01.my.domain.com" |
There was a problem hiding this comment.
Is this supposed to be a list?
There was a problem hiding this comment.
I changed this back to a list, let me know if that is wrong.
🚀 Benchmarks reportTo see the full report comment with |
|
💚 Build Succeeded
History
|
|
Package microsoft_exchange_server - 1.3.1 containing this change is available at https://epr.elastic.co/package/microsoft_exchange_server/1.3.1/ |
* Updated the yaml and the test log file. The expected output still needs to be generated. * Added ignore field and added new expected output. * Used elastic-package to generate a new changelog entry and manifest file. * Update packages/microsoft_exchange_server/data_stream/messagetracking/elasticsearch/ingest_pipeline/default.yml Co-authored-by: Andrew Kroh <andrew.kroh@elastic.co> * Update packages/microsoft_exchange_server/data_stream/messagetracking/elasticsearch/ingest_pipeline/default.yml Co-authored-by: Andrew Kroh <andrew.kroh@elastic.co> * Updated the expected data. * Changed the sender address back to a list append. * Added a test for missing networkmessageid. --------- Co-authored-by: Andrew Kroh <andrew.kroh@elastic.co>




Proposed commit message
A customer came across a couple log lines with missing networkmessageid and senderaddress fields. This in turn rejected the logs messages. Allowing these two fields to be empty or otherwise missing will allow them to pass the ingest function.
Checklist
changelog.ymlfile.Author's Checklist
How to test this PR locally
Related issues