[trend_micro_vision_one] No error for unparsable ...detection.request URI (#16124)

The `trend_micro_vision_one.detection.request` field sometimes has
values with typos in them, which makes the `uri_parts` processor fail.

An error in `error.message` is confusing. That is removed. The original
value will remain in `trend_micro_vision_one.detection.request` and
`url.*` will be populated if the `uri_parts` processor is successful.

An error is kept for the other `uri_parts` processor usage, for
`trend_micro_vision_one.alert.workbench_link`, since that seems to not
be entered by a user and therefore should always be a correct URL.

Author: chrisberkhout

packages/trend_micro_vision_one/changelog.yml

@@ -1,4 +1,9 @@
 # newer versions go on top
+- version: "2.5.0"
+  changes:
+    - description: No error for unparsable `trend_micro_vision_one.detection.request` URI.
+      type: enhancement
+      link: https://github.com/elastic/integrations/pull/16124
 - version: "2.4.0"
   changes:
     - description: >-

packages/trend_micro_vision_one/data_stream/detection/elasticsearch/ingest_pipeline/default.yml

@@ -611,11 +611,8 @@ processors:
             value: 'request string and requests array both present in same document'
   - uri_parts:
       field: trend_micro_vision_one.detection.request
-      if: ctx.trend_micro_vision_one?.detection?.request != null
-      on_failure:
-        - append:
-            field: error.message
-            value: '{{{_ingest.on_failure_message}}}'
+      ignore_missing: true
+      ignore_failure: true
   - rename:
       field: json.productCode
       target_field: trend_micro_vision_one.detection.product.code

packages/trend_micro_vision_one/manifest.yml

@@ -1,7 +1,7 @@
 format_version: "3.0.3"
 name: trend_micro_vision_one
 title: Trend Micro Vision One
-version: "2.4.0"
+version: "2.5.0"
 description: Collect logs from Trend Micro Vision One with Elastic Agent.
 type: integration
 categories: