Add metric yace_cloudwatch_getmetricdata_metrics_total #939
Conversation
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
Signed-off-by: gavin.jeong <gavin.jeong@sendbird.com>
keyolk
changed the title
|
Is there something missing here? Would be nice to get this merged as currently, there is no way to properly track costs |
|
+1 to this feature. The description in the README.md to track costs is wrong, which we can fix after landing this PR. I'm happy to test and update the docs myself. |
1 task
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.
#339
I saw the issue above but seems that the conclusion is incorrect.
GetMetricData of CloudWatch API costs by the number of its returned metrics.
So it would be worth having how much data is fetched via GetMetricData.