PUTINDEXPOLICY()`¶

About PutIndexPolicy¶

Creates or updates a field index policy for the specified log group. Only log groups in the Standard log class support field index policies. For more information about log classes, see Log classes.

You can use field index policies to create field indexes on fields found in log events in the log group. Creating field indexes speeds up and lowers the costs for CloudWatch Logs Insights queries that reference those field indexes, because these queries attempt to skip the processing of log events that are known to not match the indexed field. Good fields to index are fields that you often need to query for and fields or values that match only a small fraction of the total log events. Common examples of indexes include request ID, session ID, userID, and instance IDs. For more information, see Create field indexes to improve query performance and reduce costs.

You can configure indexed fields as facets to enable interactive exploration and filtering of your logs in the CloudWatch Logs Insights console. Facets allow you to view value distributions and counts for indexed fields without running queries. When you create a field index, you can optionally set it as a facet to enable this interactive analysis capability. For more information, see Use facets to group and explore logs.

To find the fields that are in your log group events, use the GetLogGroupFields operation.

For example, suppose you have created a field index for requestId. Then, any CloudWatch Logs Insights query on that log group that includes requestId = value or requestId IN [value, value, ...] will process fewer log events to reduce costs, and have improved performance.

CloudWatch Logs provides default field indexes for all log groups in the Standard log class. Default field indexes are automatically available for the following fields:

@logStream
@aws.region
@aws.account
@source.log
traceId

Default field indexes are in addition to any custom field indexes you define within your policy. Default field indexes are not counted towards your field index quota.

Each index policy has the following quotas and restrictions:

As many as 20 fields can be included in the policy.
Each field name can include as many as 100 characters.

Matches of log events to the names of indexed fields are case-sensitive. For example, a field index of RequestId won't match a log event containing requestId.

Log group-level field index policies created with PutIndexPolicy override account-level field index policies created with PutAccountPolicy that apply to log groups. If you use PutIndexPolicy to create a field index policy for a log group, that log group uses only that policy for log group-level indexing, including any facet configurations. The log group ignores any account-wide field index policy that applies to log groups, but data source-based account policies may still apply.

Method Signature¶

METHODS /AWS1/IF_CWL~PUTINDEXPOLICY
  IMPORTING
    !IV_LOGGROUPIDENTIFIER TYPE /AWS1/CWLLOGGROUPIDENTIFIER OPTIONAL
    !IV_POLICYDOCUMENT TYPE /AWS1/CWLPOLICYDOCUMENT OPTIONAL
  RETURNING
    VALUE(OO_OUTPUT) TYPE REF TO /aws1/cl_cwlputindexpolicyrsp
  RAISING
    /AWS1/CX_CWLINVALIDPARAMETEREX
    /AWS1/CX_CWLLIMITEXCEEDEDEX
    /AWS1/CX_CWLOPERATIONABORTEDEX
    /AWS1/CX_CWLRESOURCENOTFOUNDEX
    /AWS1/CX_CWLSERVICEUNAVAILEX
    /AWS1/CX_CWLCLIENTEXC
    /AWS1/CX_CWLSERVEREXC
    /AWS1/CX_RT_TECHNICAL_GENERIC
    /AWS1/CX_RT_SERVICE_GENERIC.

IMPORTING¶

Required arguments:¶

`iv_loggroupidentifier` `TYPE /AWS1/CWLLOGGROUPIDENTIFIER` `/AWS1/CWLLOGGROUPIDENTIFIER`¶

Specify either the log group name or log group ARN to apply this field index policy to. If you specify an ARN, use the format arn:aws:logs:region:account-id:log-group:log_group_name Don't include an * at the end.

`iv_policydocument` `TYPE /AWS1/CWLPOLICYDOCUMENT` `/AWS1/CWLPOLICYDOCUMENT`¶

The index policy document, in JSON format. The following is an example of an index policy document that creates indexes with different types.

"policyDocument": "{"Fields": [ "TransactionId" ], "FieldsV2": {"RequestId": {"type": "FIELD_INDEX"}, "APIName": {"type": "FACET"}, "StatusCode": {"type": "FACET"}}}"

You can use FieldsV2 to specify the type for each field. Supported types are FIELD_INDEX and FACET. Field names within Fields and FieldsV2 must be mutually exclusive.

The policy document must include at least one field index. For more information about the fields that can be included and other restrictions, see Field index syntax and quotas.

RETURNING¶

`oo_output` `TYPE REF TO /aws1/cl_cwlputindexpolicyrsp` `/AWS1/CL_CWLPUTINDEXPOLICYRSP`¶

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->putindexpolicy(
  iv_loggroupidentifier = |string|
  iv_policydocument = |string|
).

This is an example of reading all possible response values

lo_result = lo_result.
IF lo_result IS NOT INITIAL.
  lo_indexpolicy = lo_result->get_indexpolicy( ).
  IF lo_indexpolicy IS NOT INITIAL.
    lv_loggroupidentifier = lo_indexpolicy->get_loggroupidentifier( ).
    lv_timestamp = lo_indexpolicy->get_lastupdatetime( ).
    lv_policydocument = lo_indexpolicy->get_policydocument( ).
    lv_policyname = lo_indexpolicy->get_policyname( ).
    lv_indexsource = lo_indexpolicy->get_source( ).
  ENDIF.
ENDIF.

/AWS1/IF_CWL=>PUTINDEXPOLICY()¶