CloudWatchMetricsPublisher: Allow specifying custom, constant value dimensions

[mnylensc]

Describe the feature

Add option in CloudWatchMetricsPublisher to specify a custom dimension with constant value.

Use Case

I would like to record AWS SDK metrics per ECS task ID and per AWS service.

The MetricCollection does not contain ECS task id as a metric, so it can't be used as dimension. Currently there does not seem to be evident way of how to achieve this.

Proposed Solution

Something like this:

CloudWatchMetricsPublisher
  .builder()
  .dimensions(List.of(ConstantMetric.create("TaskId", "constant value"), CoreMetric.SERVICE_ID))

Other Information

No response

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

AWS Java SDK version used

2.17.275

JDK version used

11.0.12

Operating System and version

macOS

[debora-ito]

Hi @mnylensc thank you for reaching out.

You can publish your own custom metrics using CloudWatchMetricPublisher and MetricCollector.

You can see an example in the CloudWatchMetricPublisher javadoc:

https://sdk.amazonaws.com/java/api/latest/software/amazon/awssdk/metrics/publishers/cloudwatch/CloudWatchMetricPublisher.html

Let us know if this helps.

[mnylensc]

@debora-ito Hello, thank you. I'm not sure if that does what I want. Basically what I want is to get metrics from DynamoDbAsyncClient reported with dimensions EcsTaskId (something I can find from ECS metadata service and is always constant for the lifetime of CloudwatchMetricsPublisher instance) and ServiceId (what the AWS SDK includes in the metric collection).

The problem isn't being able to report custom metrics, it's about being able to publish those metrics under dimensions that the SDK doesn't collect metrics from.

[debora-ito]

To see if I understand:

Currently, each client-side metric has 2 dimensions - ServiceId and OperationName
You want the ability to add a custom dimension name/value (EcsTaskId for example) to each metric published.

Is that it?

[github-actions]

It looks like this issue has not been active for more than five days. In the absence of more information, we will be closing this issue soon. If you find that this is still a problem, please add a comment to prevent automatic closure, or if the issue is already closed please feel free to reopen it.

[mnylensc]

Yes, that pretty much sums it up.