-
Notifications
You must be signed in to change notification settings - Fork 444
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
[System] Type Conflict Error for error.code and error.message fields #6766
Comments
It looks like any data stream that has a The data streams with
And the ones missing
|
Thats right, this should be present in all the winlog input datastreams. |
The winlog input can produce error.code under some conditions so make sure their is a mapping present for the field that is aligned to ECS. Relates elastic#6766
The `winlog` input can produce error.code under some conditions so make sure their is a mapping present for the field that is aligned to ECS. Relates elastic#6766
The winlog input can produce error.code under some conditions so make sure their is a mapping present for the field that is aligned to ECS. Relates #6766
Package windows - 1.24.1 containing this change is available at https://epr.elastic.co/search?package=windows |
The `winlog` input can produce error.code under some conditions so make sure their is a mapping present for the field that is aligned to ECS. Relates #6766
Package hid_bravura_monitor - 1.8.1 containing this change is available at https://epr.elastic.co/search?package=hid_bravura_monitor |
In System Integration, the error.code and error.message field mapping is not present explicitly (other than security datastream). Hence, it gets dynamically mapped to long. This throws a type conflict error.
Relates: #4071
The text was updated successfully, but these errors were encountered: