Skip to content
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

Closed
ishleenk17 opened this issue Jun 30, 2023 · 4 comments · Fixed by #6868
Closed

[System] Type Conflict Error for error.code and error.message fields #6766

ishleenk17 opened this issue Jun 30, 2023 · 4 comments · Fixed by #6868

Comments

@ishleenk17
Copy link
Contributor

ishleenk17 commented Jun 30, 2023

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.

Screenshot 2023-06-30 at 2 21 11 PM

Relates: #4071

@andrewkroh
Copy link
Member

andrewkroh commented Jun 30, 2023

It looks like any data stream that has a winlog input should have error.code mapped as per ECS.

https://github.com/elastic/beats/blob/34a87e51a5a30a40f60372acfdae17a14a5faa2c/winlogbeat/eventlog/eventlog.go#L95

The data streams with winlog inputs are:

hid_bravura_monitor/winlog
microsoft_sqlserver/audit
system/application
system/security
system/system
windows/forwarded
windows/powershell
windows/powershell_operational
windows/sysmon_operational
winlog/winlog

And the ones missing error.code are:

@ishleenk17
Copy link
Contributor Author

Thats right, this should be present in all the winlog input datastreams.

andrewkroh added a commit to andrewkroh/integrations that referenced this issue Jul 7, 2023
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
andrewkroh added a commit to andrewkroh/integrations that referenced this issue Jul 7, 2023
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
andrewkroh added a commit that referenced this issue Jul 7, 2023
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
@elasticmachine
Copy link

Package windows - 1.24.1 containing this change is available at https://epr.elastic.co/search?package=windows

andrewkroh added a commit that referenced this issue Jul 7, 2023
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
@elasticmachine
Copy link

Package hid_bravura_monitor - 1.8.1 containing this change is available at https://epr.elastic.co/search?package=hid_bravura_monitor

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants