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.
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.
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. If you use
PutIndexPolicy
to create a field
index policy for a log group, that log group uses only that policy. The log group ignores any account-wide
field index policy that you might have created.
Request Syntax
{
"logGroupIdentifier": "string
",
"policyDocument": "string
"
}
Request Parameters
For information about the parameters that are common to all actions, see Common Parameters.
The request accepts the following data in JSON format.
- logGroupIdentifier
-
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.
Type: String
Length Constraints: Minimum length of 1. Maximum length of 2048.
Pattern:
[\w#+=/:,.@-]*
Required: Yes
- policyDocument
-
The index policy document, in JSON format. The following is an example of an index policy document that creates two indexes,
RequestId
andTransactionId
."policyDocument": "{ "Fields": [ "RequestId", "TransactionId" ] }"
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.
Type: String
Length Constraints: Minimum length of 1. Maximum length of 5120.
Required: Yes
Response Syntax
{
"indexPolicy": {
"lastUpdateTime": number,
"logGroupIdentifier": "string",
"policyDocument": "string",
"policyName": "string",
"source": "string"
}
}
Response Elements
If the action is successful, the service sends back an HTTP 200 response.
The following data is returned in JSON format by the service.
- indexPolicy
-
The index policy that you just created or updated.
Type: IndexPolicy object
Errors
For information about the errors that are common to all actions, see Common Errors.
- InvalidParameterException
-
A parameter is specified incorrectly.
HTTP Status Code: 400
- LimitExceededException
-
You have reached the maximum number of resources that can be created.
HTTP Status Code: 400
- OperationAbortedException
-
Multiple concurrent requests to update the same resource were in conflict.
HTTP Status Code: 400
- ResourceNotFoundException
-
The specified resource does not exist.
HTTP Status Code: 400
- ServiceUnavailableException
-
The service cannot complete the request.
HTTP Status Code: 500
Examples
Create index policy for a log group
The following example creates an index policy that indexes two fields, RequestId
and TransactionId
.
Sample Request
{
"logGroupIdentifier": "service-logs",
"policyDocument": {
"Fields": ["RequestId", "TransactionId"]
}
}
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the following: