You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
It removes the option to collect logs using aws-s3 input marked as deprecated.
Behavior on upgrade:
Update integration policy on
The option disappears after the upgrade, the datastream remains but stops collecting data.
Update integration policy off
The option remains, since the policy is unchanged it keeps functioning and ingesting data
Sidenote: This input configuration only included SQS queue ARN input field requiring the whole CloudWatch-S3-SQS chain to be configured i.e. there was no option to provide a standalone S3 bucket.
The "Changelog" modal is available from version 8.8.x, so we would need to bump the Kibana version to be able to see it. It was not possible to backport it (see PR, we are not shipping more minors for 8.7). Should I bump the whole AWS package and ship this from 8.8.0?
Hi! We just realized that we haven't looked into this PR in a while. We're sorry! We're labeling this issue as Stale to make it hit our filters and make sure we get back to it as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1. Thank you for your contribution!
Hi! We just realized that we haven't looked into this PR in a while. We're sorry! We're labeling this issue as Stale to make it hit our filters and make sure we get back to it as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1. Thank you for your contribution!
* Remove AWS CloudWatch logs via S3 option
* Update changelog entry
* Make Changelog more detailed for users that might be using the S3 datastream
---------
Co-authored-by: kaiyan-sheng <kaiyan.sheng@elastic.co>
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do?
It removes the option to collect logs using aws-s3 input marked as deprecated.
Behavior on upgrade:
The option disappears after the upgrade, the datastream remains but stops collecting data.
The option remains, since the policy is unchanged it keeps functioning and ingesting data
Sidenote: This input configuration only included SQS queue ARN input field requiring the whole CloudWatch-S3-SQS chain to be configured i.e. there was no option to provide a standalone S3 bucket.
Checklist
changelog.ymlfile.Author's Checklist
How to test this PR locally
Check that the "Collect Cloudwatch Logs via S3 options" is not shown anymore when the policy is upgraded, and the integration works as expected.
Screenshots