/AWS1/IF_R5R=>LSTRESOLVERQUERYLOGCFGASSO00()¶
About ListResolverQueryLogConfigAssociations¶
Lists information about associations between Amazon VPCs and query logging configurations.
Method Signature¶
METHODS /AWS1/IF_R5R~LSTRESOLVERQUERYLOGCFGASSO00
IMPORTING
!IV_MAXRESULTS TYPE /AWS1/R5RMAXRESULTS OPTIONAL
!IV_NEXTTOKEN TYPE /AWS1/R5RNEXTTOKEN OPTIONAL
!IT_FILTERS TYPE /AWS1/CL_R5RFILTER=>TT_FILTERS OPTIONAL
!IV_SORTBY TYPE /AWS1/R5RSORTBYKEY OPTIONAL
!IV_SORTORDER TYPE /AWS1/R5RSORTORDER OPTIONAL
RETURNING
VALUE(OO_OUTPUT) TYPE REF TO /aws1/cl_r5rlstresolverquery01
RAISING
/AWS1/CX_R5RACCESSDENIEDEX
/AWS1/CX_R5RINTERNALSVCERROREX
/AWS1/CX_R5RINVALIDPARAMETEREX
/AWS1/CX_R5RINVALIDREQUESTEX
/AWS1/CX_R5RLIMITEXCEEDEDEX
/AWS1/CX_R5RTHROTTLINGEX
/AWS1/CX_R5RCLIENTEXC
/AWS1/CX_R5RSERVEREXC
/AWS1/CX_RT_TECHNICAL_GENERIC
/AWS1/CX_RT_SERVICE_GENERIC.
IMPORTING¶
Optional arguments:¶
iv_maxresults TYPE /AWS1/R5RMAXRESULTS /AWS1/R5RMAXRESULTS¶
The maximum number of query logging associations that you want to return in the response to a
ListResolverQueryLogConfigAssociationsrequest. If you don't specify a value forMaxResults, Resolver returns up to 100 query logging associations.
iv_nexttoken TYPE /AWS1/R5RNEXTTOKEN /AWS1/R5RNEXTTOKEN¶
For the first
ListResolverQueryLogConfigAssociationsrequest, omit this value.If there are more than
MaxResultsquery logging associations that match the values that you specify forFilters, you can submit anotherListResolverQueryLogConfigAssociationsrequest to get the next group of associations. In the next request, specify the value ofNextTokenfrom the previous response.
it_filters TYPE /AWS1/CL_R5RFILTER=>TT_FILTERS TT_FILTERS¶
An optional specification to return a subset of query logging associations.
If you submit a second or subsequent
ListResolverQueryLogConfigAssociationsrequest and specify theNextTokenparameter, you must use the same values forFilters, if any, as in the previous request.
iv_sortby TYPE /AWS1/R5RSORTBYKEY /AWS1/R5RSORTBYKEY¶
The element that you want Resolver to sort query logging associations by.
If you submit a second or subsequent
ListResolverQueryLogConfigAssociationsrequest and specify theNextTokenparameter, you must use the same value forSortBy, if any, as in the previous request.Valid values include the following elements:
CreationTime: The ID of the query logging association.
Error: If the value ofStatusisFAILED, the value ofErrorindicates the cause:
DESTINATION_NOT_FOUND: The specified destination (for example, an Amazon S3 bucket) was deleted.
ACCESS_DENIED: Permissions don't allow sending logs to the destination.If
Statusis a value other thanFAILED,ERRORis null.
Id: The ID of the query logging association
ResolverQueryLogConfigId: The ID of the query logging configuration
ResourceId: The ID of the VPC that is associated with the query logging configuration
Status: The current status of the configuration. Valid values include the following:
CREATING: Resolver is creating an association between an Amazon VPC and a query logging configuration.
CREATED: The association between an Amazon VPC and a query logging configuration was successfully created. Resolver is logging queries that originate in the specified VPC.
DELETING: Resolver is deleting this query logging association.
FAILED: Resolver either couldn't create or couldn't delete the query logging association. Here are two common causes:
The specified destination (for example, an Amazon S3 bucket) was deleted.
Permissions don't allow sending logs to the destination.
iv_sortorder TYPE /AWS1/R5RSORTORDER /AWS1/R5RSORTORDER¶
If you specified a value for
SortBy, the order that you want query logging associations to be listed in,ASCENDINGorDESCENDING.If you submit a second or subsequent
ListResolverQueryLogConfigAssociationsrequest and specify theNextTokenparameter, you must use the same value forSortOrder, if any, as in the previous request.
RETURNING¶
oo_output TYPE REF TO /aws1/cl_r5rlstresolverquery01 /AWS1/CL_R5RLSTRESOLVERQUERY01¶
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->lstresolverquerylogcfgasso00(
it_filters = VALUE /aws1/cl_r5rfilter=>tt_filters(
(
new /aws1/cl_r5rfilter(
it_values = VALUE /aws1/cl_r5rfiltervalues_w=>tt_filtervalues(
( new /aws1/cl_r5rfiltervalues_w( |string| ) )
)
iv_name = |string|
)
)
)
iv_maxresults = 123
iv_nexttoken = |string|
iv_sortby = |string|
iv_sortorder = |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( ).
lv_count = lo_result->get_totalcount( ).
lv_count = lo_result->get_totalfilteredcount( ).
LOOP AT lo_result->get_resolverquerylogcfgass02( ) into lo_row.
lo_row_1 = lo_row.
IF lo_row_1 IS NOT INITIAL.
lv_resourceid = lo_row_1->get_id( ).
lv_resourceid = lo_row_1->get_resolverquerylogconfigid( ).
lv_resourceid = lo_row_1->get_resourceid( ).
lv_resolverquerylogconfiga = lo_row_1->get_status( ).
lv_resolverquerylogconfiga_1 = lo_row_1->get_error( ).
lv_resolverquerylogconfiga_2 = lo_row_1->get_errormessage( ).
lv_rfc3339timestring = lo_row_1->get_creationtime( ).
ENDIF.
ENDLOOP.
ENDIF.