[AWS] Improve latency description in integration setup#9346
[AWS] Improve latency description in integration setup#9346lucian-ioan merged 3 commits intoelastic:mainfrom
Conversation
🚀 Benchmarks reportTo see the full report comment with |
|
💚 Build Succeeded
History
cc @lucian-ioan |
zmoog
left a comment
There was a problem hiding this comment.
LGTM.
@alaudazzi, let us know what you think!
|
@muthu-mps thank you for pointing that out. The next step from here would be to add a troubleshooting guide for the user: Meta Issue. Unsure whether that will be an article that we will link to the integration descriptions or we will add it directly in the descriptions. For now, I think just updating the integration setup is fine. |
Thanks for the clarification. Make sense! |
|
Package aws - 2.13.1 containing this change is available at https://epr.elastic.co/search?package=aws |


0.0% Duplication on New Code
Proposed commit message
Improve the description of
latencyparameter in integration setup for integrations using thecloudwatchmetricset.The current description is lacking, especially in warning the user that data points might be missing due to delay in processing metrics in AWS CloudWatch.
In our official aws module docs, the description of latency is more verbose.
Checklist
changelog.ymlfile.How to test this PR locally
elastic-package stack upRelated issues
Screenshots