Missing enum value in Connect Client for GetMetricDataV2 Metrics

[casewalker]

Checkboxes for prior research

• I've gone through Developer Guide and API reference
• I've checked AWS Forums and StackOverflow.
• I've searched for previous similar issues and didn't find any solution.

Describe the bug

All documentation (including here and here) suggests that the GetMetricDataV2 Connect command supports a historical metric named CONTACTS_QUEUED_BY_ENQUEUE, however, the HistoricalMetricName enum does not contain that metric here.

Having this metric name added to the exported enum will help me write cleaner, more robust code in my app.

Regression Issue

• Select this option if this issue appears to be a regression.

SDK version number

@aws-sdk/client-connect@3.717.0

Which JavaScript Runtime is this issue in?

Node.js

Details of the browser/Node.js/ReactNative version

n/a

Reproduction Steps

n/a

Observed Behavior

Supported metric is not present in the enum of metric names

Expected Behavior

Supported metric is present in the enum of metric names

Possible Solution

Add all supported metrics to the enum of metric names

Additional Information/Context

No response

[zshzbh]

Hey @casewalker ,

That Enum comes from service model. I have created a ticket to the service team. I will keep you posted!

Thanks!
Maggie

[zshzbh]

Hey @casewalker ,

Just got back from service team -

In GetMetricDataV2 API: it has this metric: CONTACTS_QUEUED_BY_ENQUEUE and it doesn't use the field HistoricalMetricsName.

In GetMetricData API: It uses HistoricalMetricsName, but it doesn't have the metric CONTACTS_QUEUED_BY_ENQUEUE

I think right now you can manually add the V2 historical metrics or create a enum on your end. You can see the V2 historical here in the model and here on the AWS JS SDK DOC

Thanks!
Maggie

[casewalker]

Hello @zshzbh.

Ok, so it sounds like the HistoricalMetricName enum is being treated sort of as deprecated, same as GetMetricData, and there is no similar enum which currently exists for GetMetricDataV2.

In that case, I would like to request as a feature that the team creates an enum of metric names for GetMetricDataV2. This would be in-keeping with the approach used for similar APIs, such as GetCurrentMetricData (link), where the Metric Names are exported here.

This allows me to write cleaner code on my end by relying on the types exported by the AWS API.

Do you think this feature request would be fulfilled, in an effort to standardize similar APIs in the same product, and to enable cleaner code on the client side?