[trend_micro_vision_one] No error for unparsable ...detection.request URI

[chrisberkhout]

Proposed commit message

[trend_micro_vision_one] No error for unparsable `...detection.request` URI

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.

Checklist

• I have reviewed tips for building integrations and this pull request is aligned with them.
• I have verified that all data streams collect metrics or logs.
• I have added an entry to my package's changelog.yml file.
• I have verified that Kibana version constraints are current according to guidelines.
• I have verified that any added dashboard complies with Kibana's Dashboard good practices

[elasticmachine]

Pinging @elastic/security-service-integrations (Team:Security-Service Integrations)

[elastic-vault-github-plugin-prod]

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 076466b

cc @chrisberkhout

[kcreddy]

LGTM. Curious what was the error.message like in such case.

[chrisberkhout]

@kcreddy The message was like this: unable to parse URI [https://pt-br.facebook .com/someuser/]

[elastic-vault-github-plugin-prod]

Package trend_micro_vision_one - 2.5.0 containing this change is available at https://epr.elastic.co/package/trend_micro_vision_one/2.5.0/