[Fortinet Fortiproxy] handle malformed quotes

[haetamoudi]

Proposed commit message

add support for malformed quotes and log version field

Fix for https://github.com/elastic/sdh-beats/issues/6526

• Add missing log version field logver
• Remove timestamp field as the event already as a eventime which seems more precise
• handle malformed quotes

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

Author's Checklist

• [ ]

How to test this PR locally

Related issues

Screenshots

[elasticmachine]

Pinging @elastic/integration-experience (Team:Integration-Experience)

[elastic-vault-github-plugin-prod]

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: fe222f4

History

• 💔 Build #33332 failed b4b52d5
• 💚 Build #33207 succeeded 1a90836

[elastic-vault-github-plugin-prod]

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