/AWS1/IF_REH=>LISTMETRICS()¶
About ListMetrics¶
Lists the metrics that can be exported.
Method Signature¶
METHODS /AWS1/IF_REH~LISTMETRICS
IMPORTING
!IV_NEXTTOKEN TYPE /AWS1/REHNEXTTOKEN OPTIONAL
!IV_MAXRESULTS TYPE /AWS1/REHMAXRESULTS OPTIONAL
!IT_FIELDS TYPE /AWS1/CL_REHFIELD=>TT_FIELDLIST OPTIONAL
!IV_DATASOURCE TYPE /AWS1/REHSTRING255 OPTIONAL
!IT_CONDITIONS TYPE /AWS1/CL_REHCONDITION=>TT_CONDITIONLIST OPTIONAL
!IT_SORTS TYPE /AWS1/CL_REHSORT=>TT_SORTLIST OPTIONAL
RETURNING
VALUE(OO_OUTPUT) TYPE REF TO /aws1/cl_rehlistmetricsrsp
RAISING
/AWS1/CX_REHACCESSDENIEDEX
/AWS1/CX_REHINTERNALSERVEREX
/AWS1/CX_REHTHROTTLINGEX
/AWS1/CX_REHVALIDATIONEX
/AWS1/CX_REHCLIENTEXC
/AWS1/CX_REHSERVEREXC
/AWS1/CX_RT_TECHNICAL_GENERIC
/AWS1/CX_RT_SERVICE_GENERIC.
IMPORTING¶
Optional arguments:¶
iv_nexttoken TYPE /AWS1/REHNEXTTOKEN /AWS1/REHNEXTTOKEN¶
Null, or the token from a previous call to get the next set of results.
iv_maxresults TYPE /AWS1/REHMAXRESULTS /AWS1/REHMAXRESULTS¶
Maximum number of results to include in the response. If more results exist than the specified
MaxResultsvalue, a token is included in the response so that the remaining results can be retrieved.
it_fields TYPE /AWS1/CL_REHFIELD=>TT_FIELDLIST TT_FIELDLIST¶
Indicates the list of fields in the data source.
iv_datasource TYPE /AWS1/REHSTRING255 /AWS1/REHSTRING255¶
Indicates the data source of the metrics.
it_conditions TYPE /AWS1/CL_REHCONDITION=>TT_CONDITIONLIST TT_CONDITIONLIST¶
Indicates the list of all the conditions that were applied on the metrics.
it_sorts TYPE /AWS1/CL_REHSORT=>TT_SORTLIST TT_SORTLIST¶
(Optional) Indicates the order in which you want to sort the fields in the metrics. By default, the fields are sorted in the ascending order.
RETURNING¶
oo_output TYPE REF TO /aws1/cl_rehlistmetricsrsp /AWS1/CL_REHLISTMETRICSRSP¶
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->listmetrics(
it_conditions = VALUE /aws1/cl_rehcondition=>tt_conditionlist(
(
new /aws1/cl_rehcondition(
iv_field = |string|
iv_operator = |string|
iv_value = |string|
)
)
)
it_fields = VALUE /aws1/cl_rehfield=>tt_fieldlist(
(
new /aws1/cl_rehfield(
iv_aggregation = |string|
iv_name = |string|
)
)
)
it_sorts = VALUE /aws1/cl_rehsort=>tt_sortlist(
(
new /aws1/cl_rehsort(
iv_ascending = ABAP_TRUE
iv_field = |string|
)
)
)
iv_datasource = |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.
LOOP AT lo_result->get_rows( ) into lt_row.
LOOP AT lt_row into lo_row_1.
lo_row_2 = lo_row_1.
IF lo_row_2 IS NOT INITIAL.
lv_string255 = lo_row_2->get_value( ).
ENDIF.
ENDLOOP.
ENDLOOP.
lv_nexttoken = lo_result->get_nexttoken( ).
ENDIF.