{ti_eclectiqiq,ti_opencti,ti_threatconnect}: Update error.message field mapping as per ECS inside Threat Intel destination indices. #14290
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kcreddy
added
Integration:ti_opencti
kcreddy
changed the title
|
Pinging @elastic/security-service-integrations (Team:Security-Service Integrations) |
🚀 Benchmarks reportPackage
|
| Data stream | Previous EPS | New EPS | Diff (%) | Result |
|---|---|---|---|---|
indicator |
902.53 | 497.27 | -405.26 (-44.9%) | 💔 |
To see the full report comment with /test benchmark fullreport
efd6
reviewed
Jun 24, 2025
packages/ti_eclecticiq/changelog.yml
Outdated
| # newer versions go on top | ||
| - version: "1.4.1" | ||
| changes: | ||
| - description: Update error.message field mapping as per ECS inside transform destination indices. |
There was a problem hiding this comment.
Suggested change
| - description: Update error.message field mapping as per ECS inside transform destination indices. | |
| - description: Update `error.message` field mapping as per ECS inside transform destination indices. |
packages/ti_opencti/changelog.yml
Outdated
| # newer versions go on top | ||
| - version: "2.6.1" | ||
| changes: | ||
| - description: Update error.message field mapping as per ECS inside transform destination indices. |
There was a problem hiding this comment.
Suggested change
| - description: Update error.message field mapping as per ECS inside transform destination indices. | |
| - description: Update `error.message` field mapping as per ECS inside transform destination indices. |
| # WARNING: this version number needs to be kept up to date in the transform! | ||
| - version: "1.10.1" | ||
| changes: | ||
| - description: Update error.message field mapping as per ECS inside transform destination indices. |
There was a problem hiding this comment.
Suggested change
| - description: Update error.message field mapping as per ECS inside transform destination indices. | |
| - description: Update `error.message` field mapping as per ECS inside transform destination indices. |
| dest: | ||
| index: "logs-ti_threatconnect_latest.dest_indicator-7" | ||
| index: "logs-ti_threatconnect_latest.dest_indicator-8" | ||
| pipeline: "1.10.0-tactics_compatibility" |
There was a problem hiding this comment.
Suggested change
| pipeline: "1.10.0-tactics_compatibility" | |
| pipeline: "1.10.1-tactics_compatibility" |
?
There was a problem hiding this comment.
Thanks! System tests also failing due to this.
Addressed in e20b1d1
efd6
approved these changes
Jun 24, 2025
💚 Build Succeeded
History
cc @kcreddy |
|
|
Package ti_eclecticiq - 1.4.1 containing this change is available at https://epr.elastic.co/package/ti_eclecticiq/1.4.1/ |
|
Package ti_opencti - 2.6.1 containing this change is available at https://epr.elastic.co/package/ti_opencti/2.6.1/ |
|
Package ti_threatconnect - 1.10.1 containing this change is available at https://epr.elastic.co/package/ti_threatconnect/1.10.1/ |
4 tasks
shmsr
pushed a commit
to shmsr/integrations
that referenced
this pull request
Jun 30, 2025
…ld mapping as per ECS inside Threat Intel destination indices. (elastic#14290) error.message is undefined in some Threat Intel integrations. If the field is undefined, the default keyword mapping is applied. This causes issues when searching on data and also impacts custom rules. Update error.message field mapping as per ECS inside Threat Intel destination indices. The change impacts following integrations: - ti_eclectiqiq - ti_opencti - ti_threatconnect Since the mapping needs to be applied to destination indices, the index version suffix is also incremented along with upgrading transform's fleet version, only then the transform is updated.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed commit message
Checklist
changelog.ymlfile.