[windows] Fix mapping/pipelines for time_created#5384
[windows] Fix mapping/pipelines for time_created#5384efd6 merged 15 commits intoelastic:mainfrom nicpenning:patch-5
Conversation
|
I got a little wild trying to find a replace all areas where the winlog.time_created existed and accidently removed the target field of event.created that this should go into which is interesting because most places it does not do that. There seems to be more than what meets the eye with this time_created debacle. @efd6 👋 |
| ignore_failure: true | ||
| if: ctx?.winlog?.level != "" | ||
| - date: | ||
| - date: |
There was a problem hiding this comment.
| - date: | |
| - date: |
|
/test |
🌐 Coverage report
|
|
/test |
efd6
left a comment
There was a problem hiding this comment.
I can't see field definitions for winlog.time_created in powershell, powershell_operational or sysmon_operational. It should be there too, no?
|
I can check. In some cases the pipelines remove that field entirely. |
|
Confirmed, each of those remove this field so it should not exist. |
|
Package windows - 1.18.0 containing this change is available at https://epr.elastic.co/search?package=windows |
Fix mapping of winlog.time_created in the forwarded data stream and improve error handling for date processor failures throughout.
Fix mapping of winlog.time_created in the forwarded data stream and improve error handling for date processor failures throughout.

What does this PR do?
Align with other Windows integrations and the winlog.time_created improper mapping and adjusting the error handling for said pipelines.
Checklist
changelog.ymlfile.Related issues
Link related issues below. Insert the issue link or reference after the word "Closes" if merging this should automatically close it.