You are viewing documentation for version 2 of the AWS SDK for Ruby. Version 3 documentation can be found here.
Class: Aws::Connect::Types::GetCurrentMetricDataRequest
- Inherits:
-
Struct
- Object
- Struct
- Aws::Connect::Types::GetCurrentMetricDataRequest
- Defined in:
- (unknown)
Overview
When passing GetCurrentMetricDataRequest as input to an Aws::Client method, you can use a vanilla Hash:
{
instance_id: "InstanceId", # required
filters: { # required
queues: ["QueueId"],
channels: ["VOICE"], # accepts VOICE, CHAT
},
groupings: ["QUEUE"], # accepts QUEUE, CHANNEL
current_metrics: [ # required
{
name: "AGENTS_ONLINE", # accepts AGENTS_ONLINE, AGENTS_AVAILABLE, AGENTS_ON_CALL, AGENTS_NON_PRODUCTIVE, AGENTS_AFTER_CONTACT_WORK, AGENTS_ERROR, AGENTS_STAFFED, CONTACTS_IN_QUEUE, OLDEST_CONTACT_AGE, CONTACTS_SCHEDULED, AGENTS_ON_CONTACT, SLOTS_ACTIVE, SLOTS_AVAILABLE
unit: "SECONDS", # accepts SECONDS, COUNT, PERCENT
},
],
next_token: "NextToken",
max_results: 1,
}
Instance Attribute Summary collapse
-
#current_metrics ⇒ Array<Types::CurrentMetric>
The metrics to retrieve.
-
#filters ⇒ Types::Filters
The queues, up to 100, or channels, to use to filter the metrics returned.
-
#groupings ⇒ Array<String>
The grouping applied to the metrics returned.
-
#instance_id ⇒ String
The identifier of the Amazon Connect instance.
-
#max_results ⇒ Integer
The maximimum number of results to return per page.
-
#next_token ⇒ String
The token for the next set of results.
Instance Attribute Details
#current_metrics ⇒ Array<Types::CurrentMetric>
The metrics to retrieve. Specify the name and unit for each metric. The following metrics are available. For a description of all the metrics, see Real-time Metrics Definitions in the Amazon Connect Administrator Guide.
- AGENTS_AFTER_CONTACT_WORK
Unit: COUNT
Name in real-time metrics report: ACW
- AGENTS_AVAILABLE
Unit: COUNT
Name in real-time metrics report: Available
- AGENTS_ERROR
Unit: COUNT
Name in real-time metrics report: Error
- AGENTS_NON_PRODUCTIVE
Unit: COUNT
Name in real-time metrics report: NPT (Non-Productive Time)
- AGENTS_ON_CALL
Unit: COUNT
Name in real-time metrics report: On contact
- AGENTS_ON_CONTACT
Unit: COUNT
Name in real-time metrics report: On contact
- AGENTS_ONLINE
Unit: COUNT
Name in real-time metrics report: Online
- AGENTS_STAFFED
Unit: COUNT
Name in real-time metrics report: Staffed
- CONTACTS_IN_QUEUE
Unit: COUNT
Name in real-time metrics report: In queue
- CONTACTS_SCHEDULED
Unit: COUNT
Name in real-time metrics report: Scheduled
- OLDEST_CONTACT_AGE
Unit: SECONDS
When you use groupings, Unit says SECONDS but the Value is returned in MILLISECONDS. For example, if you get a response like this:
{ "Metric": { "Name": "OLDEST_CONTACT_AGE", "Unit": "SECONDS" }, "Value": 24113.0
}The actual OLDEST_CONTACT_AGE is 24 seconds.
Name in real-time metrics report: Oldest
- SLOTS_ACTIVE
Unit: COUNT
Name in real-time metrics report: Active
- SLOTS_AVAILABLE
Unit: COUNT
Name in real-time metrics report: Availability
#filters ⇒ Types::Filters
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. Both VOICE
and CHAT
channels are supported.
#groupings ⇒ Array<String>
The grouping applied to the metrics returned. For example, when grouped
by QUEUE
, the metrics returned apply to each queue rather than
aggregated for all queues. If you group by CHANNEL
, you should include
a Channels filter. Both VOICE
and CHAT
channels are supported.
If no Grouping
is included in the request, a summary of metrics is
returned.
#instance_id ⇒ String
The identifier of the Amazon Connect instance.
#max_results ⇒ Integer
The maximimum number of results to return per page.
#next_token ⇒ String
The token for the next set of results. Use the value returned in the previous response in the next request to retrieve the next set of results.
The token expires after 5 minutes from the time it is created. Subsequent requests that use the token must use the same request parameters as the request that generated the token.