[AWS CloudWatch OTEL Input] Update delay config per Policy - #19551
Conversation
✅ Elastic Docs Style Checker (Vale)No issues found on modified lines! The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale. |
andrewkroh
added
Integration:aws_cloudwatch_input_otel
| delay: {{delay}} | ||
| discovery: | ||
| filters: | ||
| namespace: "{{namespace}}" |
There was a problem hiding this comment.
One thing that I noticed, shared_credential_file and credential_profile_name are present in this file but not in manifest.
There was a problem hiding this comment.
These are planned to go in separate PR.
| type: duration | ||
| title: Statistic Delay | ||
| description: How far back from now each scrape's query window ends. Increase if metrics arrive late from CloudWatch. | ||
| default: 10m |
There was a problem hiding this comment.
Is this the right default value for all these services ?
There was a problem hiding this comment.
EC2 gets the largest (15m) since basic monitoring is 5-min granularity with the most lag; the faster 1-min services (ELB) get 5m. All are user-overridable. Open to adjusting any specific value. The standard aws integration ships no default for the equivalent latency and leaves user to set. we are setting the values for better OOTB behaviour.
|
✅ All changelog entries have the correct PR link. |
💚 Build Succeeded
History
|
|
Package aws_cloudwatch_input_otel - 0.2.1 containing this change is available at https://epr.elastic.co/package/aws_cloudwatch_input_otel/0.2.1/ |
4 participants
Proposed commit message
Apply metrics
delayper service.Checklist
changelog.ymlfile.Author's Checklist
How to test this PR locally
Related issues
Screenshots
Inspect Agent Logs:
AWS EC2 with 15mins and Lambda with 5m delay.
Policy config