/AWS1/IF_CWO=>CREATETELEMETRYRULE()¶
About CreateTelemetryRule¶
Creates a telemetry rule that defines how telemetry should be configured for Amazon Web Services resources in your account. The rule specifies which resources should have telemetry enabled and how that telemetry data should be collected based on resource type, telemetry type, and selection criteria.
Method Signature¶
METHODS /AWS1/IF_CWO~CREATETELEMETRYRULE
IMPORTING
!IV_RULENAME TYPE /AWS1/CWORULENAME OPTIONAL
!IO_RULE TYPE REF TO /AWS1/CL_CWOTELEMETRYRULE OPTIONAL
!IT_TAGS TYPE /AWS1/CL_CWOTAGMAPINPUT_W=>TT_TAGMAPINPUT OPTIONAL
RETURNING
VALUE(OO_OUTPUT) TYPE REF TO /aws1/cl_cwocreatetelruleout
RAISING
/AWS1/CX_CWOACCESSDENIEDEX
/AWS1/CX_CWOCONFLICTEXCEPTION
/AWS1/CX_CWOINTERNALSERVEREX
/AWS1/CX_CWOSERVICEQUOTAEXCDEX
/AWS1/CX_CWOTOOMANYREQUESTSEX
/AWS1/CX_CWOVALIDATIONEX
/AWS1/CX_CWOCLIENTEXC
/AWS1/CX_CWOSERVEREXC
/AWS1/CX_RT_TECHNICAL_GENERIC
/AWS1/CX_RT_SERVICE_GENERIC.
IMPORTING¶
Required arguments:¶
iv_rulename TYPE /AWS1/CWORULENAME /AWS1/CWORULENAME¶
A unique name for the telemetry rule being created.
io_rule TYPE REF TO /AWS1/CL_CWOTELEMETRYRULE /AWS1/CL_CWOTELEMETRYRULE¶
The configuration details for the telemetry rule, including the resource type, telemetry type, destination configuration, and selection criteria for which resources the rule applies to.
Optional arguments:¶
it_tags TYPE /AWS1/CL_CWOTAGMAPINPUT_W=>TT_TAGMAPINPUT TT_TAGMAPINPUT¶
The key-value pairs to associate with the telemetry rule resource for categorization and management purposes.
RETURNING¶
oo_output TYPE REF TO /aws1/cl_cwocreatetelruleout /AWS1/CL_CWOCREATETELRULEOUT¶
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->createtelemetryrule(
io_rule = new /aws1/cl_cwotelemetryrule(
io_destinationconfiguration = new /aws1/cl_cwotelemetrydstconf(
io_vpcflowlogparameters = new /aws1/cl_cwovpcflowlogparams(
iv_logformat = |string|
iv_maxaggregationinterval = 123
iv_traffictype = |string|
)
iv_destinationpattern = |string|
iv_destinationtype = |string|
iv_retentionindays = 123
)
iv_resourcetype = |string|
iv_scope = |string|
iv_selectioncriteria = |string|
iv_telemetrytype = |string|
)
it_tags = VALUE /aws1/cl_cwotagmapinput_w=>tt_tagmapinput(
(
VALUE /aws1/cl_cwotagmapinput_w=>ts_tagmapinput_maprow(
value = new /aws1/cl_cwotagmapinput_w( |string| )
key = |string|
)
)
)
iv_rulename = |string|
).
This is an example of reading all possible response values
lo_result = lo_result.
IF lo_result IS NOT INITIAL.
lv_resourcearn = lo_result->get_rulearn( ).
ENDIF.