Improve system test coverage - 1

[moxarth-rathod]

Proposed commit message

improve system test coverage in the following integrations:

add GCS system test:
- akmai
- panw_cortex_xdr

add AWS system test:
- carbon_black_cloud
- f5_bigip
- servicenow
- sublime_security
- tanium
- jamf_protect

add CEL system test:
- cloudflare

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

• Relates [SSI - System test] Improve system test coverage for the SSI integrations #15144

[elasticmachine]

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

[elastic-vault-github-plugin-prod]

🚀 Benchmarks report

Package carbon_black_cloud 👍(3) 💚(1) 💔(1)

Expand to view

Data stream	Previous EPS	New EPS	Diff (%)	Result
asset_vulnerability_summary	14705.88	10526.32	-4179.56 (-28.42%)	💔

Package cloudflare 👍(1) 💚(0) 💔(1)

Expand to view

Data stream	Previous EPS	New EPS	Diff (%)	Result
audit	3759.4	3105.59	-653.81 (-17.39%)	💔

Package sublime_security 👍(1) 💚(1) 💔(1)

Expand to view

Data stream	Previous EPS	New EPS	Diff (%)	Result
email_message	901.71	764.53	-137.18 (-15.21%)	💔

Package tanium 👍(1) 💚(2) 💔(3)

Expand to view

Data stream	Previous EPS	New EPS	Diff (%)	Result
client_status	9345.79	7092.2	-2253.59 (-24.11%)	💔
discover	4484.3	3412.97	-1071.33 (-23.89%)	💔
reporting	21739.13	17543.86	-4195.27 (-19.3%)	💔

To see the full report comment with /test benchmark fullreport

[efd6]

The commit message should explain what the improvements are, and given that there are a number of packages affected, this would likely either be sections in the commit message or splitting the PR into distinct PRs for each package (I don't really think this is necessary since the logic of the integrations does not appear to be changed here, but it is an option).

[efd6]

Final new line (there are others below).

[moxarth-rathod]

The commit message should explain what the improvements are, and given that there are a number of packages affected, this would likely either be sections in the commit message or splitting the PR into distinct PRs for each package (I don't really think this is necessary since the logic of the integrations does not appear to be changed here, but it is an option).

Yes, i can update the commit message but since there are total 30 integrations so i have planned to raise 3 PRs with 9-10 integrations each.

[moxarth-rathod]

/test

[efd6]

/test

[elasticmachine]

💔 Build Failed

• Buildkite Build
• Commit: d445cf8

Failed CI Steps

• Check integrations jamf_protect

History

• 💔 Build #34021 failed d445cf8
• 💔 Build #33959 failed d445cf8
• 💚 Build #33937 succeeded ca0b5ef
• 💚 Build #33908 succeeded a7eb18e

cc @moxarth-rathod

[kcreddy]

Looking at the issue's parent, here we are covering all inputs using multiple service deployers which was not possible earlier.
Adding onto @efd6 point, please update the title and commit message to reflect this.
Also spell check on akamai instead of akmai in commit message.