[cisco_ftd] Fix grok failure with username with spaces on ftd messageID. - Githubissues

elastic / integrations

Elastic Integrations

https://www.elastic.co/integrations

Other

196 stars 424 forks source link

[cisco_ftd] Fix grok failure with username with spaces on ftd messageID. #11198

Open aleksmaus opened 1 week ago

aleksmaus commented 1 week ago

Proposed commit message

Fix grok failure with username with spaces on ftd messageID.

Added alternative pattern as suggested in original issue ticket https://github.com/elastic/integrations/issues/10721 It is currently just DATA pattern match, not sure if we should tighten this further.
Improved on failure message.

Checklist

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

Related issues

Closes https://github.com/elastic/integrations/issues/10721

elasticmachine commented 1 week ago

Pinging @elastic/sec-deployment-and-devices (Team:Security-Deployment and Devices)

elasticmachine commented 1 week ago

:green_heart: Build Succeeded

Buildkite Build
Commit: 0331dd1896759074cdbb2c7f17c2784137e0083a

History

:broken_heart: Build #16232 failed 6c9c40b80f2cd6fe41839f4e4b5a140fb4f80cb2

cc @aleksmaus

elastic-sonarqube[bot] commented 1 week ago

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
66.7% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube