[ Cloudflare Logpush ] Populate event.id from the Ray ID value for Firewall Events and HTTP Requests

[leandrojmp]

• Enhancement

Proposed commit message

This PR adds a set processor on the Firewall Events and HTTP Requests ingest pipelines to populate the field event.id with the value of the fields cloudflare_logpush.http_request.ray.id in the HTTP Requests dataset and cloudflare_logpush.firewall_event.ray.id in the Firewall Events dataset.

This enables the user to filter for events on both datasets by the same event.id.

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

Related issues

• Closes [ Cloudflare Logpush ] Ray ID field should have the same name in all datasets. #12234

[elasticmachine]

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

[chemamartinez]

/test

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: de4c2fa440eb6fc3f523955feee23e331c2d1cd8

[elastic-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

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

See analysis details on SonarQube

[chemamartinez]

LGTM

[elastic-vault-github-plugin-prod]

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