[Custom AWS Logs] Add latency config parameter into aws-cloudwatch input#4859
Merged
tommyers-elastic merged 2 commits intoelastic:mainfrom Dec 19, 2022
Merged
[Custom AWS Logs] Add latency config parameter into aws-cloudwatch input#4859tommyers-elastic merged 2 commits intoelastic:mainfrom
tommyers-elastic merged 2 commits intoelastic:mainfrom
Conversation
🌐 Coverage report
|
francescayeye
approved these changes
Dec 19, 2022
|
Package aws_logs - 0.3.1 containing this change is available at https://epr.elastic.co/search?package=aws_logs |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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?
This PR is to add
latencyconfig parameter into aws-cloudwatch input. During testing, I found we are also missing thenumber_of_workersparameter too.Here is what the agent policy looks like after installing the integration with specifying
latency:and here is what the agent policy looks like with specifying
number_of_workers:Checklist
changelog.ymlfile.Related issues
Screenshot