/AWS1/IF_CNT=>GETCURRENTMETRICDATA()¶
About GetCurrentMetricData¶
Gets the real-time metric data from the specified Amazon Connect instance.
For a description of each metric, see Metrics definitions in the Amazon Connect Administrator Guide.
When you make a successful API request, you can expect the following metric values in the response:
-
Metric value is null: The calculation cannot be performed due to divide by zero or insufficient data
-
Metric value is a number (including 0) of defined type: The number provided is the calculation result
-
MetricResult list is empty: The request cannot find any data in the system
The following guidelines can help you work with the API:
-
Each dimension in the metric response must contain a value
-
Each item in MetricResult must include all requested metrics
-
If the response is slow due to large result sets, try these approaches:
-
Add filters to reduce the amount of data returned
-
Method Signature¶
METHODS /AWS1/IF_CNT~GETCURRENTMETRICDATA
IMPORTING
!IV_INSTANCEID TYPE /AWS1/CNTINSTANCEID OPTIONAL
!IO_FILTERS TYPE REF TO /AWS1/CL_CNTFILTERS OPTIONAL
!IT_GROUPINGS TYPE /AWS1/CL_CNTGROUPINGS_W=>TT_GROUPINGS OPTIONAL
!IT_CURRENTMETRICS TYPE /AWS1/CL_CNTCURRENTMETRIC=>TT_CURRENTMETRICS OPTIONAL
!IV_NEXTTOKEN TYPE /AWS1/CNTNEXTTOKEN OPTIONAL
!IV_MAXRESULTS TYPE /AWS1/CNTMAXRESULT100 OPTIONAL
!IT_SORTCRITERIA TYPE /AWS1/CL_CNTCURRENTMETORTCRIT=>TT_CURRENTMETRICSORTCRITMAXONE OPTIONAL
RETURNING
VALUE(OO_OUTPUT) TYPE REF TO /aws1/cl_cntgetcurrentmetric01
RAISING
/AWS1/CX_CNTINTERNALSERVICEEX
/AWS1/CX_CNTINVALIDPARAMETEREX
/AWS1/CX_CNTINVALIDREQUESTEX
/AWS1/CX_CNTRESOURCENOTFOUNDEX
/AWS1/CX_CNTTHROTTLINGEX
/AWS1/CX_CNTCLIENTEXC
/AWS1/CX_CNTSERVEREXC
/AWS1/CX_RT_TECHNICAL_GENERIC
/AWS1/CX_RT_SERVICE_GENERIC.
IMPORTING¶
Required arguments:¶
iv_instanceid TYPE /AWS1/CNTINSTANCEID /AWS1/CNTINSTANCEID¶
The identifier of the Amazon Connect instance. You can find the instance ID in the Amazon Resource Name (ARN) of the instance.
io_filters TYPE REF TO /AWS1/CL_CNTFILTERS /AWS1/CL_CNTFILTERS¶
The filters to apply to returned metrics. You can filter up to the following limits:
Queues: 100
Routing profiles: 100
Channels: 3 (VOICE, CHAT, and TASK channels are supported.)
RoutingStepExpressions: 50
AgentStatuses: 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
AgentStatusesas filter make sure Queues is added as primary filter.When using the
RoutingStepExpressionfilter, you need to pass exactly oneQueueId. The filter is also case sensitive so when using theRoutingStepExpressionfilter, grouping byROUTING_STEP_EXPRESSIONis required.Currently tagging is only supported on the resources that are passed in the filter.
it_currentmetrics TYPE /AWS1/CL_CNTCURRENTMETRIC=>TT_CURRENTMETRICS TT_CURRENTMETRICS¶
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 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 and the Value is returned in SECONDS.
When you do not 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.
When the filter
RoutingStepExpressionis used, this metric is still calculated from enqueue time. For example, if a contact that has been queued underfor 10 seconds has expired andbecomes active, thenOLDEST_CONTACT_AGEfor this queue will be counted starting from 10, not 0.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
Optional arguments:¶
it_groupings TYPE /AWS1/CL_CNTGROUPINGS_W=>TT_GROUPINGS TT_GROUPINGS¶
Defines the level of aggregation for metrics data by a dimension(s). Its similar to sorting items into buckets based on a common characteristic, then counting or calculating something for each bucket. For example, when grouped by
QUEUE, the metrics returned apply to each queue rather than aggregated for all queues.The grouping list is an ordered list, with the first item in the list defined as the primary grouping. If no grouping is included in the request, the aggregation happens at the instance-level.
If you group by
CHANNEL, you should include a Channels filter. VOICE, CHAT, and TASK channels are supported.If you group by
AGENT_STATUS, you must include theQUEUEas the primary grouping and use queue filter. When you group byAGENT_STATUS, the only metric available is theAGENTS_ONLINEmetric.If you group by
ROUTING_PROFILE, you must include either a queue or routing profile filter. In addition, a routing profile filter is required for metricsCONTACTS_SCHEDULED,CONTACTS_IN_QUEUE, andOLDEST_CONTACT_AGE.When using the
RoutingStepExpressionfilter, group byROUTING_STEP_EXPRESSIONis required.
iv_nexttoken TYPE /AWS1/CNTNEXTTOKEN /AWS1/CNTNEXTTOKEN¶
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.
iv_maxresults TYPE /AWS1/CNTMAXRESULT100 /AWS1/CNTMAXRESULT100¶
The maximum number of results to return per page.
it_sortcriteria TYPE /AWS1/CL_CNTCURRENTMETORTCRIT=>TT_CURRENTMETRICSORTCRITMAXONE TT_CURRENTMETRICSORTCRITMAXONE¶
The way to sort the resulting response based on metrics. You can enter one sort criteria. By default resources are sorted based on
AGENTS_ONLINE,DESCENDING. The metric collection is sorted based on the input metrics.Note the following:
Sorting on
SLOTS_ACTIVEandSLOTS_AVAILABLEis not supported.
RETURNING¶
oo_output TYPE REF TO /aws1/cl_cntgetcurrentmetric01 /AWS1/CL_CNTGETCURRENTMETRIC01¶
Domain /AWS1/RT_ACCOUNT_ID Primitive Type NUMC
Examples¶
Syntax Example¶
This is an example of the syntax for calling the method. It includes every possible argument and initializes every possible value. The data provided is not necessarily semantically accurate (for example the value "string" may be provided for something that is intended to be an instance ID, or in some cases two arguments may be mutually exclusive). The syntax shows the ABAP syntax for creating the various data structures.
DATA(lo_result) = lo_client->getcurrentmetricdata(
io_filters = new /aws1/cl_cntfilters(
it_agentstatuses = VALUE /aws1/cl_cntagentstatuses_w=>tt_agentstatuses(
( new /aws1/cl_cntagentstatuses_w( |string| ) )
)
it_channels = VALUE /aws1/cl_cntchannels_w=>tt_channels(
( new /aws1/cl_cntchannels_w( |string| ) )
)
it_queues = VALUE /aws1/cl_cntqueues_w=>tt_queues(
( new /aws1/cl_cntqueues_w( |string| ) )
)
it_routingprofiles = VALUE /aws1/cl_cntroutingprofiles_w=>tt_routingprofiles(
( new /aws1/cl_cntroutingprofiles_w( |string| ) )
)
it_routingstepexpressions = VALUE /aws1/cl_cntroutingxprsns_w=>tt_routingexpressions(
( new /aws1/cl_cntroutingxprsns_w( |string| ) )
)
)
it_currentmetrics = VALUE /aws1/cl_cntcurrentmetric=>tt_currentmetrics(
(
new /aws1/cl_cntcurrentmetric(
iv_name = |string|
iv_unit = |string|
)
)
)
it_groupings = VALUE /aws1/cl_cntgroupings_w=>tt_groupings(
( new /aws1/cl_cntgroupings_w( |string| ) )
)
it_sortcriteria = VALUE /aws1/cl_cntcurrentmetortcrit=>tt_currentmetricsortcritmaxone(
(
new /aws1/cl_cntcurrentmetortcrit(
iv_sortbymetric = |string|
iv_sortorder = |string|
)
)
)
iv_instanceid = |string|
iv_maxresults = 123
iv_nexttoken = |string|
).
This is an example of reading all possible response values
lo_result = lo_result.
IF lo_result IS NOT INITIAL.
lv_nexttoken = lo_result->get_nexttoken( ).
LOOP AT lo_result->get_metricresults( ) into lo_row.
lo_row_1 = lo_row.
IF lo_row_1 IS NOT INITIAL.
lo_dimensions = lo_row_1->get_dimensions( ).
IF lo_dimensions IS NOT INITIAL.
lo_queuereference = lo_dimensions->get_queue( ).
IF lo_queuereference IS NOT INITIAL.
lv_queueid = lo_queuereference->get_id( ).
lv_arn = lo_queuereference->get_arn( ).
ENDIF.
lv_channel = lo_dimensions->get_channel( ).
lo_routingprofilereference = lo_dimensions->get_routingprofile( ).
IF lo_routingprofilereference IS NOT INITIAL.
lv_routingprofileid = lo_routingprofilereference->get_id( ).
lv_arn = lo_routingprofilereference->get_arn( ).
ENDIF.
lv_routingexpression = lo_dimensions->get_routingstepexpression( ).
lo_agentstatusidentifier = lo_dimensions->get_agentstatus( ).
IF lo_agentstatusidentifier IS NOT INITIAL.
lv_arn = lo_agentstatusidentifier->get_arn( ).
lv_agentstatusid = lo_agentstatusidentifier->get_id( ).
ENDIF.
ENDIF.
LOOP AT lo_row_1->get_collections( ) into lo_row_2.
lo_row_3 = lo_row_2.
IF lo_row_3 IS NOT INITIAL.
lo_currentmetric = lo_row_3->get_metric( ).
IF lo_currentmetric IS NOT INITIAL.
lv_currentmetricname = lo_currentmetric->get_name( ).
lv_unit = lo_currentmetric->get_unit( ).
ENDIF.
lv_value = lo_row_3->get_value( ).
ENDIF.
ENDLOOP.
ENDIF.
ENDLOOP.
lv_timestamp = lo_result->get_datasnapshottime( ).
lv_approximatetotalcount = lo_result->get_approximatetotalcount( ).
ENDIF.