From ecf269c54aadfb474431a9288ff8e37d42e19d6f Mon Sep 17 00:00:00 2001
From: awstools The note for an item (section or question) in a contact evaluation. Even though a note in an evaluation can have up to 3072 chars, there is also a limit on the
+ * total number of chars for all the notes in the evaluation combined. Assuming there are N
+ * questions in the evaluation being submitted, then the max char limit for all notes combined is N
+ * x 1024. Channels: 3 (VOICE, CHAT, and TASK channels are supported.) RoutingStepExpressions: 50 Metric data is retrieved only for the resources associated with the queues or routing
* profiles, and by any channels included in the filter. (You cannot filter by both queue AND
- * routing profile.) You can include both resource IDs and resource ARNs in the same request.
When using RoutingStepExpression
, you need to pass exactly one
+ * QueueId
.
Currently tagging is only supported on the resources that are passed in the filter.
*/ Filters: Filters | undefined; @@ -2077,6 +2082,10 @@ export interface GetCurrentMetricDataRequest { *If no Grouping
is included in the request, a summary of metrics is
* returned.
When using the RoutingStepExpression
filter, group by
+ * ROUTING_STEP_EXPRESSION
is required.
\{ "Metric": \{ "Name": "OLDEST_CONTACT_AGE", "Unit": "SECONDS" \}, "Value": 24113.0
*
\}
* The actual OLDEST_CONTACT_AGE is 24 seconds.
+ *When the filter RoutingStepExpression
is used, this metric is still
+ * calculated from enqueue time. For example, if a contact that has been queued under
+ *
for 10 seconds has expired and
+ * becomes active, then OLDEST_CONTACT_AGE
for this queue will be counted starting
+ * from 10, not 0.
Name in real-time metrics report: Oldest *
* @@ -2873,6 +2887,8 @@ export interface GetMetricDataRequest { *The queues, up to 100, or channels, to use to filter the metrics returned. Metric data is * retrieved only for the resources associated with the queues or channels included in the filter. * You can include both queue IDs and queue ARNs in the same request. VOICE, CHAT, and TASK channels are supported.
+ *RoutingStepExpression is not a valid filter for GetMetricData and we recommend switching to + * GetMetricDataV2 for more up-to-date features.
*To filter by Queues
, enter the queue
* ID/ARN, not the name of the queue.
If no grouping is specified, a summary of metrics for all queues is returned.
+ *RoutingStepExpression is not a valid filter for GetMetricData and we recommend switching to + * GetMetricDataV2 for more up-to-date features.
*/ Groupings?: Grouping[]; @@ -3396,6 +3414,9 @@ export interface GetMetricDataV2Request { *Feature
*Routing step expression
+ *At least one filter must be passed from queues, routing profiles, agents, or user hierarchy * groups.
@@ -3411,7 +3432,8 @@ export interface GetMetricDataV2Request { *AGENT
| CHANNEL
| AGENT_HIERARCHY_LEVEL_ONE
|
* AGENT_HIERARCHY_LEVEL_TWO
| AGENT_HIERARCHY_LEVEL_THREE
|
* AGENT_HIERARCHY_LEVEL_FOUR
| AGENT_HIERARCHY_LEVEL_FIVE
|
- * FEATURE
| contact/segmentAttributes/connect:Subtype
+ * FEATURE
| contact/segmentAttributes/connect:Subtype
|
+ * ROUTING_STEP_EXPRESSION
*
*
* connect:Chat
, connect:SMS
, connect:Telephony
, and
* connect:WebRTC
are valid filterValue
examples (not exhaustive) for
* the contact/segmentAttributes/connect:Subtype filter
key.
+ * ROUTING_STEP_EXPRESSION is a valid filter key with a filter value up to 3000 + * length.
*CHANNEL
| AGENT_HIERARCHY_LEVEL_ONE
|
* AGENT_HIERARCHY_LEVEL_TWO
| AGENT_HIERARCHY_LEVEL_THREE
|
* AGENT_HIERARCHY_LEVEL_FOUR
| AGENT_HIERARCHY_LEVEL_FIVE
,
- * contact/segmentAttributes/connect:Subtype
+ * contact/segmentAttributes/connect:Subtype
|
+ * ROUTING_STEP_EXPRESSION
*
*/
Groupings?: string[];
@@ -3572,7 +3597,7 @@ export interface GetMetricDataV2Request {
* Unit: Seconds
*Valid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy, Feature, - * contact/segmentAttributes/connect:Subtype
+ * contact/segmentAttributes/connect:Subtype, RoutingStepExpression *Feature is a valid filter but not a valid grouping.
*Unit: Count
*Valid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy, - * contact/segmentAttributes/connect:Subtype
+ * contact/segmentAttributes/connect:Subtype, RoutingStepExpression *DISCONNECT_REASON
*
* Valid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy, Feature, - * contact/segmentAttributes/connect:Subtype
+ * contact/segmentAttributes/connect:Subtype, RoutingStepExpression *Feature is a valid filter but not a valid grouping.
*Valid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy, * contact/segmentAttributes/connect:Subtype
*Unit: Percent
+ *Valid groupings and filters: Queue, RoutingStepExpression
+ *Unit: Percent
+ *Valid groupings and filters: Queue, RoutingStepExpression
+ *This metric is available only for contacts analyzed by Contact Lens conversational
@@ -3824,6 +3859,11 @@ export interface GetMetricDataV2Request {
* (inclusive), in seconds. For Comparison
, you must enter LT
(for
* "Less than").
Unit: Count
+ *Valid groupings and filters: Queue, RoutingStepExpression
+ *Unit: Seconds
@@ -8577,7 +8617,7 @@ export interface MonitorContactRequest { /** * @public *Specify which monitoring actions the user is allowed to take. For example, whether the user - * is allowed to escalate from silent monitoring to barge.
+ * is allowed to escalate from silent monitoring to barge. AllowedMonitorCapabilities is required if barge is enabled. */ AllowedMonitorCapabilities?: MonitorCapability[]; diff --git a/codegen/sdk-codegen/aws-models/connect.json b/codegen/sdk-codegen/aws-models/connect.json index 688647850287..16c0c84179e5 100644 --- a/codegen/sdk-codegen/aws-models/connect.json +++ b/codegen/sdk-codegen/aws-models/connect.json @@ -13967,7 +13967,7 @@ "Value": { "target": "com.amazonaws.connect#EvaluationNoteString", "traits": { - "smithy.api#documentation": "The note for an item (section or question) in a contact evaluation.
" + "smithy.api#documentation": "The note for an item (section or question) in a contact evaluation.
\nEven though a note in an evaluation can have up to 3072 chars, there is also a limit on the\n total number of chars for all the notes in the evaluation combined. Assuming there are N\n questions in the evaluation being submitted, then the max char limit for all notes combined is N\n x 1024.
\nThe filters to apply to returned metrics. You can filter up to the following limits:
\nQueues: 100
\nRouting profiles: 100
\nChannels: 3 (VOICE, CHAT, and TASK channels are supported.)
\nMetric data is retrieved only for the resources associated with the queues or routing\n profiles, and by any channels included in the filter. (You cannot filter by both queue AND\n routing profile.) You can include both resource IDs and resource ARNs in the same request.
\nCurrently tagging is only supported on the resources that are passed in the filter.
", + "smithy.api#documentation": "The filters to apply to returned metrics. You can filter up to the following limits:
\nQueues: 100
\nRouting profiles: 100
\nChannels: 3 (VOICE, CHAT, and TASK channels are supported.)
\nRoutingStepExpressions: 50
\nMetric data is retrieved only for the resources associated with the queues or routing\n profiles, and by any channels included in the filter. (You cannot filter by both queue AND\n routing profile.) You can include both resource IDs and resource ARNs in the same request.
\nWhen using RoutingStepExpression
, you need to pass exactly one\n QueueId
.
Currently tagging is only supported on the resources that are passed in the filter.
", "smithy.api#required": {} } }, "Groupings": { "target": "com.amazonaws.connect#Groupings", "traits": { - "smithy.api#documentation": "The grouping applied to the metrics returned. For example, when grouped by\n QUEUE
, the metrics returned apply to each queue rather than aggregated for all\n queues.
If you group by CHANNEL
, you should include a Channels filter.\n VOICE, CHAT, and TASK channels are supported.
If you group by ROUTING_PROFILE
, you must include either a queue or routing\n profile filter. In addition, a routing profile filter is required for metrics\n CONTACTS_SCHEDULED
, CONTACTS_IN_QUEUE
, and \n OLDEST_CONTACT_AGE
.
If no Grouping
is included in the request, a summary of metrics is\n returned.
The grouping applied to the metrics returned. For example, when grouped by\n QUEUE
, the metrics returned apply to each queue rather than aggregated for all\n queues.
If you group by CHANNEL
, you should include a Channels filter.\n VOICE, CHAT, and TASK channels are supported.
If you group by ROUTING_PROFILE
, you must include either a queue or routing\n profile filter. In addition, a routing profile filter is required for metrics\n CONTACTS_SCHEDULED
, CONTACTS_IN_QUEUE
, and \n OLDEST_CONTACT_AGE
.
If no Grouping
is included in the request, a summary of metrics is\n returned.
When using the RoutingStepExpression
filter, group by\n ROUTING_STEP_EXPRESSION
is required.
The metrics to retrieve. Specify the name and unit for each metric. The following metrics\n are available. For a description of all the metrics, see Real-time Metrics\n Definitions in the Amazon Connect Administrator Guide.
\nUnit: COUNT
\nName in real-time metrics report: ACW\n
\nUnit: COUNT
\nName in real-time metrics report: Available\n
\nUnit: COUNT
\nName in real-time metrics report: Error\n
\nUnit: COUNT
\nName in real-time metrics report: NPT (Non-Productive Time)\n
\nUnit: COUNT
\nName in real-time metrics report: On\n contact\n
\nUnit: COUNT
\nName in real-time metrics report: On\n contact\n
\nUnit: COUNT
\nName in real-time metrics report: Online\n
\nUnit: COUNT
\nName in real-time metrics report: Staffed\n
\nUnit: COUNT
\nName in real-time metrics report: In\n queue\n
\nUnit: COUNT
\nName in real-time metrics report: Scheduled\n
\nUnit: SECONDS
\nWhen you use groupings, Unit says SECONDS and the Value is returned in SECONDS.
\nWhen you do not use groupings, Unit says SECONDS but the Value is returned in\n MILLISECONDS. For example, if you get a response like this:
\n\n { \"Metric\": { \"Name\": \"OLDEST_CONTACT_AGE\", \"Unit\": \"SECONDS\" }, \"Value\": 24113.0\n
}
The actual OLDEST_CONTACT_AGE is 24 seconds.
\nName in real-time metrics report: Oldest\n
\nUnit: COUNT
\nName in real-time metrics report: Active\n
\nUnit: COUNT
\nName in real-time metrics report: Availability\n
\nThe metrics to retrieve. Specify the name and unit for each metric. The following metrics\n are available. For a description of all the metrics, see Real-time Metrics\n Definitions in the Amazon Connect Administrator Guide.
\nUnit: COUNT
\nName in real-time metrics report: ACW\n
\nUnit: COUNT
\nName in real-time metrics report: Available\n
\nUnit: COUNT
\nName in real-time metrics report: Error\n
\nUnit: COUNT
\nName in real-time metrics report: NPT (Non-Productive Time)\n
\nUnit: COUNT
\nName in real-time metrics report: On\n contact\n
\nUnit: COUNT
\nName in real-time metrics report: On\n contact\n
\nUnit: COUNT
\nName in real-time metrics report: Online\n
\nUnit: COUNT
\nName in real-time metrics report: Staffed\n
\nUnit: COUNT
\nName in real-time metrics report: In\n queue\n
\nUnit: COUNT
\nName in real-time metrics report: Scheduled\n
\nUnit: SECONDS
\nWhen you use groupings, Unit says SECONDS and the Value is returned in SECONDS.
\nWhen you do not use groupings, Unit says SECONDS but the Value is returned in\n MILLISECONDS. For example, if you get a response like this:
\n\n { \"Metric\": { \"Name\": \"OLDEST_CONTACT_AGE\", \"Unit\": \"SECONDS\" }, \"Value\": 24113.0\n
}
The actual OLDEST_CONTACT_AGE is 24 seconds.
\nWhen the filter RoutingStepExpression
is used, this metric is still\n calculated from enqueue time. For example, if a contact that has been queued under\n
for 10 seconds has expired and
\n becomes active, then OLDEST_CONTACT_AGE
for this queue will be counted starting\n from 10, not 0.
Name in real-time metrics report: Oldest\n
\nUnit: COUNT
\nName in real-time metrics report: Active\n
\nUnit: COUNT
\nName in real-time metrics report: Availability\n
\nThe queues, up to 100, or channels, to use to filter the metrics returned. Metric data is\n retrieved only for the resources associated with the queues or channels included in the filter.\n You can include both queue IDs and queue ARNs in the same request. VOICE, CHAT, and TASK channels are supported.
\nTo filter by Queues
, enter the queue\n ID/ARN, not the name of the queue.
The queues, up to 100, or channels, to use to filter the metrics returned. Metric data is\n retrieved only for the resources associated with the queues or channels included in the filter.\n You can include both queue IDs and queue ARNs in the same request. VOICE, CHAT, and TASK channels are supported.
\nRoutingStepExpression is not a valid filter for GetMetricData and we recommend switching to\n GetMetricDataV2 for more up-to-date features.
\nTo filter by Queues
, enter the queue\n ID/ARN, not the name of the queue.
The grouping applied to the metrics returned. For example, when results are grouped by\n queue, the metrics returned are grouped by queue. The values returned apply to the metrics for\n each queue rather than aggregated for all queues.
\nIf no grouping is specified, a summary of metrics for all queues is returned.
" + "smithy.api#documentation": "The grouping applied to the metrics returned. For example, when results are grouped by\n queue, the metrics returned are grouped by queue. The values returned apply to the metrics for\n each queue rather than aggregated for all queues.
\nIf no grouping is specified, a summary of metrics for all queues is returned.
\nRoutingStepExpression is not a valid filter for GetMetricData and we recommend switching to\n GetMetricDataV2 for more up-to-date features.
" } }, "HistoricalMetrics": { @@ -15215,20 +15215,20 @@ "Filters": { "target": "com.amazonaws.connect#FiltersV2List", "traits": { - "smithy.api#documentation": "The filters to apply to returned metrics. You can filter on the following resources:
\nQueues
\nRouting profiles
\nAgents
\nChannels
\nUser hierarchy groups
\nFeature
\nAt least one filter must be passed from queues, routing profiles, agents, or user hierarchy\n groups.
\nTo filter by phone number, see Create a historical\n metrics report in the Amazon Connect Administrator's\n Guide.
\nNote the following limits:
\n\n Filter keys: A maximum of 5 filter keys are supported in\n a single request. Valid filter keys: QUEUE
| ROUTING_PROFILE
|\n AGENT
| CHANNEL
| AGENT_HIERARCHY_LEVEL_ONE
|\n AGENT_HIERARCHY_LEVEL_TWO
| AGENT_HIERARCHY_LEVEL_THREE
|\n AGENT_HIERARCHY_LEVEL_FOUR
| AGENT_HIERARCHY_LEVEL_FIVE
|\n FEATURE
| contact/segmentAttributes/connect:Subtype
\n
\n Filter values: A maximum of 100 filter values are\n supported in a single request. VOICE, CHAT, and TASK are valid filterValue
for the\n CHANNEL filter key. They do not count towards limitation of 100 filter values. For example, a\n GetMetricDataV2 request can filter by 50 queues, 35 agents, and 15 routing profiles for a total\n of 100 filter values, along with 3 channel filters.
\n contact_lens_conversational_analytics
is a valid filterValue for the\n FEATURE
filter key. It is available only to contacts analyzed by Contact Lens\n conversational analytics.
\n connect:Chat
, connect:SMS
, connect:Telephony
, and\n connect:WebRTC
are valid filterValue
examples (not exhaustive) for\n the contact/segmentAttributes/connect:Subtype filter
key.
The filters to apply to returned metrics. You can filter on the following resources:
\nQueues
\nRouting profiles
\nAgents
\nChannels
\nUser hierarchy groups
\nFeature
\nRouting step expression
\nAt least one filter must be passed from queues, routing profiles, agents, or user hierarchy\n groups.
\nTo filter by phone number, see Create a historical\n metrics report in the Amazon Connect Administrator's\n Guide.
\nNote the following limits:
\n\n Filter keys: A maximum of 5 filter keys are supported in\n a single request. Valid filter keys: QUEUE
| ROUTING_PROFILE
|\n AGENT
| CHANNEL
| AGENT_HIERARCHY_LEVEL_ONE
|\n AGENT_HIERARCHY_LEVEL_TWO
| AGENT_HIERARCHY_LEVEL_THREE
|\n AGENT_HIERARCHY_LEVEL_FOUR
| AGENT_HIERARCHY_LEVEL_FIVE
|\n FEATURE
| contact/segmentAttributes/connect:Subtype
|\n ROUTING_STEP_EXPRESSION
\n
\n Filter values: A maximum of 100 filter values are\n supported in a single request. VOICE, CHAT, and TASK are valid filterValue
for the\n CHANNEL filter key. They do not count towards limitation of 100 filter values. For example, a\n GetMetricDataV2 request can filter by 50 queues, 35 agents, and 15 routing profiles for a total\n of 100 filter values, along with 3 channel filters.
\n contact_lens_conversational_analytics
is a valid filterValue for the\n FEATURE
filter key. It is available only to contacts analyzed by Contact Lens\n conversational analytics.
\n connect:Chat
, connect:SMS
, connect:Telephony
, and\n connect:WebRTC
are valid filterValue
examples (not exhaustive) for\n the contact/segmentAttributes/connect:Subtype filter
key.
ROUTING_STEP_EXPRESSION is a valid filter key with a filter value up to 3000\n length.
\nThe grouping applied to the metrics that are returned. For example, when results are grouped\n by queue, the metrics returned are grouped by queue. The values that are returned apply to the\n metrics for each queue. They are not aggregated for all queues.
\nIf no grouping is specified, a summary of all metrics is returned.
\nValid grouping keys: QUEUE
| ROUTING_PROFILE
| AGENT
\n | CHANNEL
| AGENT_HIERARCHY_LEVEL_ONE
|\n AGENT_HIERARCHY_LEVEL_TWO
| AGENT_HIERARCHY_LEVEL_THREE
|\n AGENT_HIERARCHY_LEVEL_FOUR
| AGENT_HIERARCHY_LEVEL_FIVE
,\n contact/segmentAttributes/connect:Subtype
\n
The grouping applied to the metrics that are returned. For example, when results are grouped\n by queue, the metrics returned are grouped by queue. The values that are returned apply to the\n metrics for each queue. They are not aggregated for all queues.
\nIf no grouping is specified, a summary of all metrics is returned.
\nValid grouping keys: QUEUE
| ROUTING_PROFILE
| AGENT
\n | CHANNEL
| AGENT_HIERARCHY_LEVEL_ONE
|\n AGENT_HIERARCHY_LEVEL_TWO
| AGENT_HIERARCHY_LEVEL_THREE
|\n AGENT_HIERARCHY_LEVEL_FOUR
| AGENT_HIERARCHY_LEVEL_FIVE
,\n contact/segmentAttributes/connect:Subtype
|\n ROUTING_STEP_EXPRESSION
\n
The metrics to retrieve. Specify the name, groupings, and filters for each metric. The\n following historical metrics are available. For a description of each metric, see Historical metrics definitions in the Amazon Connect Administrator's\n Guide.
\nUnit: Percent
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy, Feature,\n contact/segmentAttributes/connect:Subtype
\nThis metric is available only in Amazon Web Services Regions where Forecasting, capacity planning, and scheduling is available.
\nUnit: Seconds
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy
\nUnit: Percent
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy
\nUnit: Seconds
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy
\nUnit: Count
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy
\nUnit: Count
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy
\nData for this metric is available starting from October 1, 2023 0:00:00 GMT.
\nUnit: Percentage
\nValid groupings and filters: Routing Profile, Agent, Agent Hierarchy
\nThis metric is available only in Amazon Web Services Regions where Forecasting, capacity planning, and scheduling is available.
\nUnit: Percent
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy
\nThis metric is available only in Amazon Web Services Regions where Forecasting, capacity planning, and scheduling is available.
\nUnit: Seconds
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy
\nUnit: Seconds
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy, Feature,\n contact/segmentAttributes/connect:Subtype
\nUnit: Seconds
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy
\nUnit: Seconds
\nValid metric filter key: INITIATION_METHOD
\n
Valid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy, Feature,\n contact/segmentAttributes/connect:Subtype
\nFeature is a valid filter but not a valid grouping.
\nUnit: Seconds
\nValid metric filter key: INITIATION_METHOD
. For now, this metric only\n supports the following as INITIATION_METHOD
: INBOUND
|\n OUTBOUND
| CALLBACK
| API
\n
Valid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy
\nThe Negate
key in Metric Level Filters is not applicable for this\n metric.
Unit: Seconds
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy
\nUnit: Seconds
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy, Feature,\n contact/segmentAttributes/connect:Subtype
\nFeature is a valid filter but not a valid grouping.
\nUnit: Seconds
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy, Feature,\n contact/segmentAttributes/connect:Subtype
\nThis metric is available only for contacts analyzed by Contact Lens conversational\n analytics.
\nUnit: Seconds
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy,\n contact/segmentAttributes/connect:Subtype
\nUnit: Seconds
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy, Feature,\n contact/segmentAttributes/connect:Subtype
\nFeature is a valid filter but not a valid grouping.
\nUnit: Seconds
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy, Feature,\n contact/segmentAttributes/connect:Subtype
\nFeature is a valid filter but not a valid grouping.
\nUnit: Seconds
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy,\n contact/segmentAttributes/connect:Subtype
\nUnit: Count
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy, Feature,\n contact/segmentAttributes/connect:Subtype
\nFeature is a valid filter but not a valid grouping.
\nUnit: Seconds
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy,\n contact/segmentAttributes/connect:Subtype
\nUnit: Seconds
\nValid metric filter key: INITIATION_METHOD
\n
Valid groupings and filters: Queue, Channel, Routing Profile, Feature,\n contact/segmentAttributes/connect:Subtype
\nFeature is a valid filter but not a valid grouping.
\nThis metric is available only for contacts analyzed by Contact Lens conversational\n analytics.
\nUnit: Count
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy,\n contact/segmentAttributes/connect:Subtype
\nThis metric is available only for contacts analyzed by Contact Lens conversational\n analytics.
\nUnit: Seconds
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy,\n contact/segmentAttributes/connect:Subtype
\nThis metric is available only for contacts analyzed by Contact Lens conversational\n analytics.
\nUnit: Seconds
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy,\n contact/segmentAttributes/connect:Subtype
\nUnit: Seconds
\nValid groupings and filters: Queue, Channel, Routing Profile, Feature,\n contact/segmentAttributes/connect:Subtype
\nFeature is a valid filter but not a valid grouping.
\nUnit: Seconds
\nValid groupings and filters: Queue, Channel, Routing Profile,\n contact/segmentAttributes/connect:Subtype
\nThis metric is available only for contacts analyzed by Contact Lens conversational\n analytics.
\nUnit: Seconds
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy,\n contact/segmentAttributes/connect:Subtype
\nThis metric is available only for contacts analyzed by Contact Lens conversational\n analytics.
\nUnit: Seconds
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy,\n contact/segmentAttributes/connect:Subtype
\nThis metric is available only for contacts analyzed by Contact Lens conversational\n analytics.
\nUnit: Seconds
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy,\n contact/segmentAttributes/connect:Subtype
\nUnit: Count
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy,\n contact/segmentAttributes/connect:Subtype
\nUnit: Count
\nValid metric filter key: INITIATION_METHOD
\n
Valid groupings and filters: Queue, Channel, Routing Profile, Feature,\n contact/segmentAttributes/connect:Subtype
\nFeature is a valid filter but not a valid grouping.
\nUnit: Count
\nValid metric filter key: INITIATION_METHOD
,\n DISCONNECT_REASON
\n
Valid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy, Feature,\n contact/segmentAttributes/connect:Subtype
\nFeature is a valid filter but not a valid grouping.
\nUnit: Count
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy,\n contact/segmentAttributes/connect:Subtype
\nUnit: Count
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy
\nUnit: Count
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy
\nUnit: Count
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy
\nUnit: Count
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy
\nUnit: Percent
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy
\nUnit: Count
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy,\n contact/segmentAttributes/connect:Subtype
\nUnit: Count
\nValid groupings and filters: Queue, Channel, Routing Profile,\n contact/segmentAttributes/connect:Subtype
\nThreshold: For ThresholdValue
enter any whole number from 1 to 604800\n (inclusive), in seconds. For Comparison
, you must enter LT
(for\n \"Less than\").
Unit: Count
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy, Feature,\n contact/segmentAttributes/connect:Subtype
\nFeature is a valid filter but not a valid grouping.
\nUnit: Count
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy,\n contact/segmentAttributes/connect:Subtype
\nUnit: Count
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy,\n contact/segmentAttributes/connect:Subtype
\nUnit: Seconds
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy,\n contact/segmentAttributes/connect:Subtype
\nThis metric is available only for contacts analyzed by Contact Lens conversational\n analytics.
\nUnit: Percentage
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy,\n contact/segmentAttributes/connect:Subtype
\nThis metric is available only for contacts analyzed by Contact Lens conversational\n analytics.
\nUnit: Percentage
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy,\n contact/segmentAttributes/connect:Subtype
\nThis metric is available only for contacts analyzed by Contact Lens conversational\n analytics.
\nUnit: Percentage
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy,\n contact/segmentAttributes/connect:Subtype
\nThis metric is available only for contacts analyzed by Contact Lens conversational\n analytics.
\nUnit: Percentage
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy,\n contact/segmentAttributes/connect:Subtype
\nYou can include up to 20 SERVICE_LEVEL metrics in a request.
\nUnit: Percent
\nValid groupings and filters: Queue, Channel, Routing Profile
\nThreshold: For ThresholdValue
, enter any whole number from 1 to 604800\n (inclusive), in seconds. For Comparison
, you must enter LT
(for\n \"Less than\").
Unit: Seconds
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy
\nUnit: Seconds
\nValid metric filter key: INITIATION_METHOD
. This metric only supports the\n following filter keys as INITIATION_METHOD
: INBOUND
|\n OUTBOUND
| CALLBACK
| API
\n
Valid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy
\nThe Negate
key in Metric Level Filters is not applicable for this\n metric.
Unit: Seconds
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy
\nUnit: Seconds
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy
\nUnit: Count
\nValid groupings and filters: Queue, Channel, Routing Profile,\n contact/segmentAttributes/connect:Subtype
\nThreshold: For ThresholdValue
, enter any whole number from 1 to 604800\n (inclusive), in seconds. For Comparison
, you must enter LT
(for\n \"Less than\").
Unit: Count
\nValid groupings and filters: Queue, Channel, Routing Profile,\n contact/segmentAttributes/connect:Subtype
\nThreshold: For ThresholdValue
, enter any whole number from 1 to 604800\n (inclusive), in seconds. For Comparison
, you must enter LT
(for\n \"Less than\").
Valid metric filter key: DISCONNECT_REASON
\n
Unit: Count
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy,\n contact/segmentAttributes/connect:Subtype
\nUnit: Seconds
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy
\nUnit: Seconds
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy
\nUnit: Count
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy
\nUnit: Seconds
\nValid groupings and filters: Routing Profile, Agent, Agent Hierarchy
\nUnit: Seconds
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy
\nUnit: Seconds
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy
\nUnit: Seconds
\nValid groupings and filters: Routing Profile, Agent, Agent Hierarchy
\nUnit: Seconds
\nValid groupings and filters: Routing Profile, Agent, Agent Hierarchy
\nUnit: Count
\nValid groupings and filters: Queue, Channel, Routing Profile,\n contact/segmentAttributes/connect:Subtype
\nThe metrics to retrieve. Specify the name, groupings, and filters for each metric. The\n following historical metrics are available. For a description of each metric, see Historical metrics definitions in the Amazon Connect Administrator's\n Guide.
\nUnit: Percent
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy, Feature,\n contact/segmentAttributes/connect:Subtype
\nThis metric is available only in Amazon Web Services Regions where Forecasting, capacity planning, and scheduling is available.
\nUnit: Seconds
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy
\nUnit: Percent
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy
\nUnit: Seconds
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy
\nUnit: Count
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy
\nUnit: Count
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy
\nData for this metric is available starting from October 1, 2023 0:00:00 GMT.
\nUnit: Percentage
\nValid groupings and filters: Routing Profile, Agent, Agent Hierarchy
\nThis metric is available only in Amazon Web Services Regions where Forecasting, capacity planning, and scheduling is available.
\nUnit: Percent
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy
\nThis metric is available only in Amazon Web Services Regions where Forecasting, capacity planning, and scheduling is available.
\nUnit: Seconds
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy
\nUnit: Seconds
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy, Feature,\n contact/segmentAttributes/connect:Subtype
\nUnit: Seconds
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy
\nUnit: Seconds
\nValid metric filter key: INITIATION_METHOD
\n
Valid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy, Feature,\n contact/segmentAttributes/connect:Subtype
\nFeature is a valid filter but not a valid grouping.
\nUnit: Seconds
\nValid metric filter key: INITIATION_METHOD
. For now, this metric only\n supports the following as INITIATION_METHOD
: INBOUND
|\n OUTBOUND
| CALLBACK
| API
\n
Valid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy
\nThe Negate
key in Metric Level Filters is not applicable for this\n metric.
Unit: Seconds
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy
\nUnit: Seconds
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy, Feature,\n contact/segmentAttributes/connect:Subtype
\nFeature is a valid filter but not a valid grouping.
\nUnit: Seconds
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy, Feature,\n contact/segmentAttributes/connect:Subtype
\nThis metric is available only for contacts analyzed by Contact Lens conversational\n analytics.
\nUnit: Seconds
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy,\n contact/segmentAttributes/connect:Subtype
\nUnit: Seconds
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy, Feature,\n contact/segmentAttributes/connect:Subtype, RoutingStepExpression
\nFeature is a valid filter but not a valid grouping.
\nUnit: Seconds
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy, Feature,\n contact/segmentAttributes/connect:Subtype
\nFeature is a valid filter but not a valid grouping.
\nUnit: Seconds
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy,\n contact/segmentAttributes/connect:Subtype
\nUnit: Count
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy, Feature,\n contact/segmentAttributes/connect:Subtype
\nFeature is a valid filter but not a valid grouping.
\nUnit: Seconds
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy,\n contact/segmentAttributes/connect:Subtype
\nUnit: Seconds
\nValid metric filter key: INITIATION_METHOD
\n
Valid groupings and filters: Queue, Channel, Routing Profile, Feature,\n contact/segmentAttributes/connect:Subtype
\nFeature is a valid filter but not a valid grouping.
\nThis metric is available only for contacts analyzed by Contact Lens conversational\n analytics.
\nUnit: Count
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy,\n contact/segmentAttributes/connect:Subtype
\nThis metric is available only for contacts analyzed by Contact Lens conversational\n analytics.
\nUnit: Seconds
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy,\n contact/segmentAttributes/connect:Subtype
\nThis metric is available only for contacts analyzed by Contact Lens conversational\n analytics.
\nUnit: Seconds
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy,\n contact/segmentAttributes/connect:Subtype
\nUnit: Seconds
\nValid groupings and filters: Queue, Channel, Routing Profile, Feature,\n contact/segmentAttributes/connect:Subtype
\nFeature is a valid filter but not a valid grouping.
\nUnit: Seconds
\nValid groupings and filters: Queue, Channel, Routing Profile,\n contact/segmentAttributes/connect:Subtype
\nThis metric is available only for contacts analyzed by Contact Lens conversational\n analytics.
\nUnit: Seconds
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy,\n contact/segmentAttributes/connect:Subtype
\nThis metric is available only for contacts analyzed by Contact Lens conversational\n analytics.
\nUnit: Seconds
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy,\n contact/segmentAttributes/connect:Subtype
\nThis metric is available only for contacts analyzed by Contact Lens conversational\n analytics.
\nUnit: Seconds
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy,\n contact/segmentAttributes/connect:Subtype
\nUnit: Count
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy,\n contact/segmentAttributes/connect:Subtype, RoutingStepExpression
\nUnit: Count
\nValid metric filter key: INITIATION_METHOD
\n
Valid groupings and filters: Queue, Channel, Routing Profile, Feature,\n contact/segmentAttributes/connect:Subtype
\nFeature is a valid filter but not a valid grouping.
\nUnit: Count
\nValid metric filter key: INITIATION_METHOD
,\n DISCONNECT_REASON
\n
Valid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy, Feature,\n contact/segmentAttributes/connect:Subtype, RoutingStepExpression
\nFeature is a valid filter but not a valid grouping.
\nUnit: Count
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy,\n contact/segmentAttributes/connect:Subtype
\nUnit: Count
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy
\nUnit: Count
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy
\nUnit: Count
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy
\nUnit: Count
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy
\nUnit: Percent
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy
\nUnit: Count
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy,\n contact/segmentAttributes/connect:Subtype
\nUnit: Count
\nValid groupings and filters: Queue, Channel, Routing Profile,\n contact/segmentAttributes/connect:Subtype
\nThreshold: For ThresholdValue
enter any whole number from 1 to 604800\n (inclusive), in seconds. For Comparison
, you must enter LT
(for\n \"Less than\").
Unit: Count
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy, Feature,\n contact/segmentAttributes/connect:Subtype
\nFeature is a valid filter but not a valid grouping.
\nUnit: Count
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy,\n contact/segmentAttributes/connect:Subtype
\nUnit: Count
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy,\n contact/segmentAttributes/connect:Subtype
\nUnit: Seconds
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy,\n contact/segmentAttributes/connect:Subtype
\nUnit: Percent
\nValid groupings and filters: Queue, RoutingStepExpression
\nUnit: Percent
\nValid groupings and filters: Queue, RoutingStepExpression
\nThis metric is available only for contacts analyzed by Contact Lens conversational\n analytics.
\nUnit: Percentage
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy,\n contact/segmentAttributes/connect:Subtype
\nThis metric is available only for contacts analyzed by Contact Lens conversational\n analytics.
\nUnit: Percentage
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy,\n contact/segmentAttributes/connect:Subtype
\nThis metric is available only for contacts analyzed by Contact Lens conversational\n analytics.
\nUnit: Percentage
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy,\n contact/segmentAttributes/connect:Subtype
\nThis metric is available only for contacts analyzed by Contact Lens conversational\n analytics.
\nUnit: Percentage
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy,\n contact/segmentAttributes/connect:Subtype
\nYou can include up to 20 SERVICE_LEVEL metrics in a request.
\nUnit: Percent
\nValid groupings and filters: Queue, Channel, Routing Profile
\nThreshold: For ThresholdValue
, enter any whole number from 1 to 604800\n (inclusive), in seconds. For Comparison
, you must enter LT
(for\n \"Less than\").
Unit: Count
\nValid groupings and filters: Queue, RoutingStepExpression
\nUnit: Seconds
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy
\nUnit: Seconds
\nValid metric filter key: INITIATION_METHOD
. This metric only supports the\n following filter keys as INITIATION_METHOD
: INBOUND
|\n OUTBOUND
| CALLBACK
| API
\n
Valid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy
\nThe Negate
key in Metric Level Filters is not applicable for this\n metric.
Unit: Seconds
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy
\nUnit: Seconds
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy
\nUnit: Count
\nValid groupings and filters: Queue, Channel, Routing Profile,\n contact/segmentAttributes/connect:Subtype
\nThreshold: For ThresholdValue
, enter any whole number from 1 to 604800\n (inclusive), in seconds. For Comparison
, you must enter LT
(for\n \"Less than\").
Unit: Count
\nValid groupings and filters: Queue, Channel, Routing Profile,\n contact/segmentAttributes/connect:Subtype
\nThreshold: For ThresholdValue
, enter any whole number from 1 to 604800\n (inclusive), in seconds. For Comparison
, you must enter LT
(for\n \"Less than\").
Valid metric filter key: DISCONNECT_REASON
\n
Unit: Count
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy,\n contact/segmentAttributes/connect:Subtype
\nUnit: Seconds
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy
\nUnit: Seconds
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy
\nUnit: Count
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy
\nUnit: Seconds
\nValid groupings and filters: Routing Profile, Agent, Agent Hierarchy
\nUnit: Seconds
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy
\nUnit: Seconds
\nValid groupings and filters: Queue, Channel, Routing Profile, Agent, Agent Hierarchy
\nUnit: Seconds
\nValid groupings and filters: Routing Profile, Agent, Agent Hierarchy
\nUnit: Seconds
\nValid groupings and filters: Routing Profile, Agent, Agent Hierarchy
\nUnit: Count
\nValid groupings and filters: Queue, Channel, Routing Profile,\n contact/segmentAttributes/connect:Subtype
\nSpecify which monitoring actions the user is allowed to take. For example, whether the user\n is allowed to escalate from silent monitoring to barge.
" + "smithy.api#documentation": "Specify which monitoring actions the user is allowed to take. For example, whether the user\n is allowed to escalate from silent monitoring to barge. AllowedMonitorCapabilities is required if barge is enabled.
" } }, "ClientToken": { @@ -22830,6 +22836,12 @@ "traits": { "smithy.api#enumValue": "CUSTOM_BOT" } + }, + "SUPERVISOR": { + "target": "smithy.api#Unit", + "traits": { + "smithy.api#enumValue": "SUPERVISOR" + } } } },