Repository navigation
[fortinet_fortigate] Generate processor tags and normalize error handler - #15540
Conversation
🚀 Benchmarks reportTo see the full report comment with |
|
Pinging @elastic/integration-experience (Team:Integration-Experience) |
| value: "{{{destination.nat.ip}}}" | ||
| if: ctx.destination?.nat?.ip != null | ||
| allow_duplicates: false | ||
| - append: |
There was a problem hiding this comment.
out of curiosity, would this duplication set the field twice? can this trigger an error because of allow_duplicates: false?
There was a problem hiding this comment.
No, because allow_duplicates is false, it won't set it twice. As far as I know, it shouldn't show up as an error (but then again I don't know, as ignore_failure still yields an increase in the error count 🤷♂️)
The issue here is that the processor does have to actually check every element of related.ip, do a string comparison, and fail out when it finds the existing value in there already.
- Generate tags for processors missing tags - Normalize the pipeline error handler
606f678 to
381a7b5
Compare
💚 Build Succeeded
History
|
|
Package fortinet_fortigate - 1.34.1 containing this change is available at https://epr.elastic.co/package/fortinet_fortigate/1.34.1/ |
…ler (elastic#15540) - Generate tags for processors missing tags - Normalize the pipeline error handler
Proposed commit message
Checklist
changelog.ymlfile.- [ ] I have verified that any added dashboard complies with Kibana's Dashboard good practices