-
Notifications
You must be signed in to change notification settings - Fork 460
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[GCS] Adding new integration for Custom GCS Input #4692
Conversation
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
There is currently a few questions up for discussion here:
|
🌐 Coverage report
|
Integration has not been fully tested yet, but will be soon (before merging) |
Waiting for this to merge to add system tests: elastic/stream#46 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just minor change requested. Rest LGTM 👍🏼
{{#if service_account_file}} | ||
auth.credentials_file.path: {{service_account_file}} | ||
{{/if}} | ||
{{#if buckets}} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Another field parse_json
could be added as per the doc
Hi! We just realized that we haven't looked into this PR in a while. We're sorry! We're labeling this issue as |
@P1llus , can we get this in? |
@narph @P1llus I feel if we could wait till this PR: elastic/beats#34155 is merged, it would be awesome. This contains a lot of significant improvements to the GCS input which makes it more stable and behave better at scale. Having the integration live after the changes have gone through would be ideal. |
This was waiting for elastic/stream#46 and elastic/elastic-package#1073 The reason behind it was so that we could implement the dynamic ECS template already from the initial version. It also seems that we should bump the minimum version as per @ShourieG comment, so we can ensure we have all the features needed for the input to work as intended. |
All blocking features have now been resolved, will just have to update the PR with the system test and add dynamic ECS template before merging: #5055 |
@narph @P1llus PR: elastic/beats#34155 is now merged, hence unblocking this PR. |
This new input needs to be added to the filebeat spec file for elastic-agent first: https://github.com/elastic/elastic-agent/blob/main/specs/filebeat.spec.yml |
Spec file updated as per: elastic/elastic-agent#2149 |
There is currently no possible way to override the URL endpoint for the GCS client, we would need to add a |
Co-authored-by: ShourieG <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Package google_cloud_storage - 0.1.0 containing this change is available at https://epr.elastic.co/search?package=google_cloud_storage |
What does this PR do?
This adds an integration for the new Google Cloud Storage input that was added to filebeat in 8.5.0
Checklist
changelog.yml
file.Author's Checklist
How to test this PR locally
Related issues