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.

Sign up for GitHub

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

Jump to bottom

FIX: Elastic integration field mappings #13725

Closed
weslambert opened this issue Sep 23, 2024 · 2 comments
Closed

FIX: Elastic integration field mappings #13725

weslambert opened this issue Sep 23, 2024 · 2 comments
Assignees
@weslambert
Milestone
2.4.110

Comments

@weslambert
Copy link
Contributor

weslambert commented Sep 23, 2024 •
edited
Loading

During the upgrade to Elastic 8.14.3, integration mappings caused some fields to be dynamically mapped instead of set to the same mapping as other indices.

For example:

  • destination.ip (changed to keyword, now enforcing IP)
  • related.ip (changed to keyword, now enforcing IP)
  • source.ip (changed to keyword, now enforcing IP)
@weslambert weslambert added this to the 2.4.110 milestone Sep 23, 2024
@weslambert weslambert self-assigned this Sep 23, 2024
@weslambert
Copy link
Contributor Author

#13724

@weslambert weslambert reopened this Sep 23, 2024
@weslambert weslambert changed the title FIX: Elastic integration core fields FIX: Elastic integration field mappings Sep 23, 2024
@weslambert weslambert reopened this Sep 23, 2024
@weslambert
Copy link
Contributor Author

#13732
#13736

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 7, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@weslambert weslambert

Labels
None yet
Projects
None yet
Milestone
2.4.110
Development

No branches or pull requests
1 participant
@weslambert