[Cloudflare Logpush, Akamai] - Fixed variable naming bugs related to the gcs input - #6199
Conversation
…e global queue if provided.
|
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
🌐 Coverage report
|
|
/test |
kcreddy
left a comment
There was a problem hiding this comment.
Change LGTM.
Just a thought,.. instead of changing manifest.yml parameters to number_of_workers, we could have changed input to use max_workers parameter. That maybe slightly cleaner since number_of_workers is already being used by AWS-S3 input in multiple packages.
Using a script on this parameter could be a challenge in the future?
kcreddy
left a comment
There was a problem hiding this comment.
Change LGTM.
Just a thought,.. instead of changing manifest.yml parameters to number_of_workers, we could have changed input to use max_workers parameter. That maybe slightly cleaner since number_of_workers is already being used by AWS-S3 input in multiple packages.
Using a script on this parameter could be a challenge in the future?
|
Package akamai - 2.8.2 containing this change is available at https://epr.elastic.co/search?package=akamai |
|
Package cloudflare_logpush - 1.3.1 containing this change is available at https://epr.elastic.co/search?package=cloudflare_logpush |
* Add gateway_dns data stream for Cloudflare Logpush * Add gateway_http data stream for Cloudflare Logpush * Add gateway_network data stream for Cloudflare Logpush * Add network_session data stream for Cloudflare Logpush * Update new data streams with latest changes from #6164 and #6053 * Add casb_findings data stream for Cloudflare Logpush * Add access_request data stream for Cloudflare Logpush * Rename CASB sample log * Add device_posture data stream for Cloudflare Logpush * Update new data streams with latest changes from #6199 * Add requested changes for data streams * Fix typo in network analytics pipeline * Fix missing field in Device Posture pipeline * Add dashboards for ZT events * Fix the use of event.outcome and event.type * Update Cloudflare Logpush dashboards * Update pipeline and system tests * Update Cloudflare Logpush screenshots * Add screenshots to manifest * Update preference in timestamp formats * Increase Kibana version to 8.7.0 * Update some filters in cloudflare logpush dashboards
…the gcs input (elastic#6199) * added optional local sqs queues per data stream that will override the global queue if provided. * updated changelog * updated docs * updated docs * addressed PR comments and resolved issues * fixed variable name bug for akamai and cf logpush * updated changelog
* Add gateway_dns data stream for Cloudflare Logpush * Add gateway_http data stream for Cloudflare Logpush * Add gateway_network data stream for Cloudflare Logpush * Add network_session data stream for Cloudflare Logpush * Update new data streams with latest changes from elastic#6164 and elastic#6053 * Add casb_findings data stream for Cloudflare Logpush * Add access_request data stream for Cloudflare Logpush * Rename CASB sample log * Add device_posture data stream for Cloudflare Logpush * Update new data streams with latest changes from elastic#6199 * Add requested changes for data streams * Fix typo in network analytics pipeline * Fix missing field in Device Posture pipeline * Add dashboards for ZT events * Fix the use of event.outcome and event.type * Update Cloudflare Logpush dashboards * Update pipeline and system tests * Update Cloudflare Logpush screenshots * Add screenshots to manifest * Update preference in timestamp formats * Increase Kibana version to 8.7.0 * Update some filters in cloudflare logpush dashboards
Type of change
What does this PR do?
This fixes some variable naming bugs for the akamai & cloudflare logpush packages, that could cause potential issues in future.
Checklist
changelog.ymlfile.Related issues