|
2226 | 2226 | "traits": { |
2227 | 2227 | "smithy.api#length": { |
2228 | 2228 | "min": 1, |
2229 | | - "max": 1 |
| 2229 | + "max": 2 |
2230 | 2230 | } |
2231 | 2231 | } |
2232 | 2232 | }, |
|
4458 | 4458 | } |
4459 | 4459 | ], |
4460 | 4460 | "traits": { |
4461 | | - "smithy.api#documentation": "<p>Lists log events from the specified log group. You can list all the log events or filter the results\n using one or more of the following:</p>\n <ul>\n <li>\n <p>A filter pattern</p>\n </li>\n <li>\n <p>A time range</p>\n </li>\n <li>\n <p>The log stream name, or a log stream name prefix that matches mutltiple log streams</p>\n </li>\n </ul>\n <p>You must have the <code>logs:FilterLogEvents</code> permission to perform this operation.</p>\n <p>You can specify the log group to search by using either <code>logGroupIdentifier</code> or <code>logGroupName</code>.\n You must include one of these two parameters, but you can't include both.\n </p>\n <p>\n <code>FilterLogEvents</code> is a paginated operation. Each page returned can contain up to 1 MB of log events or up to 10,000 log events. A returned page might only be partially full, or even empty. \n For example, if the result of a query would return 15,000 log events, the first page isn't guaranteed to have 10,000 log events even if they all fit into 1 MB.</p>\n <p>Partially full or empty pages\n don't necessarily mean that pagination is finished. If the results include a <code>nextToken</code>, there might be more log events available. You can return these additional log events by providing the nextToken in a subsequent\n <code>FilterLogEvents</code> operation. If the results don't include a <code>nextToken</code>, then pagination is finished. </p>\n <note>\n <p>If you set <code>startFromHead</code> to <code>true</code> and you don’t include <code>endTime</code> in your request, you can end up in a situation where the pagination doesn't terminate. \n This can happen when the new log events are being added to the target log streams\n faster than they are being read. This situation is a good use case for the CloudWatch Logs <a href=\"https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/CloudWatchLogs_LiveTail.html\">Live Tail</a> feature.</p>\n </note>\n <p>The returned log events are sorted by event timestamp, the timestamp when the event was ingested\n by CloudWatch Logs, and the ID of the <code>PutLogEvents</code> request.</p>\n <p>If you are using CloudWatch cross-account observability, you can use this operation in a monitoring account and \n view data from the linked source accounts. For more information, see \n <a href=\"https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch-Unified-Cross-Account.html\">CloudWatch cross-account observability</a>.</p>\n <note>\n <p>If you are using <a href=\"https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/CloudWatch-Logs-Transformation.html\">log transformation</a>, the <code>FilterLogEvents</code> operation returns only the original versions of log events, before they \n were transformed. To view the transformed versions, you must use a <a href=\"https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/AnalyzingLogData.html\">CloudWatch Logs query.</a>\n </p>\n </note>", |
| 4461 | + "smithy.api#documentation": "<p>Lists log events from the specified log group. You can list all the log events or filter the results\n using one or more of the following:</p>\n <ul>\n <li>\n <p>A filter pattern</p>\n </li>\n <li>\n <p>A time range</p>\n </li>\n <li>\n <p>The log stream name, or a log stream name prefix that matches mutltiple log streams</p>\n </li>\n </ul>\n <p>You must have the <code>logs:FilterLogEvents</code> permission to perform this operation.</p>\n <p>You can specify the log group to search by using either <code>logGroupIdentifier</code> or <code>logGroupName</code>.\n You must include one of these two parameters, but you can't include both.\n </p>\n <p>\n <code>FilterLogEvents</code> is a paginated operation. Each page returned can contain up to 1 MB of log events or up to 10,000 log events. A returned page might only be partially full, or even empty. \n For example, if the result of a query would return 15,000 log events, the first page isn't guaranteed to have 10,000 log events even if they all fit into 1 MB.</p>\n <p>Partially full or empty pages\n don't necessarily mean that pagination is finished. If the results include a <code>nextToken</code>, there might be more log events available. You can return these additional log events by providing the nextToken in a subsequent\n <code>FilterLogEvents</code> operation. If the results don't include a <code>nextToken</code>, then pagination is finished. </p>\n <p>Specifying the <code>limit</code> parameter only guarantees that a single page doesn't return more log events than the specified limit, but it might return fewer events than the limit. This is the expected API behavior.</p>\n <p>The returned log events are sorted by event timestamp, the timestamp when the event was ingested\n by CloudWatch Logs, and the ID of the <code>PutLogEvents</code> request.</p>\n <p>If you are using CloudWatch cross-account observability, you can use this operation in a monitoring account and \n view data from the linked source accounts. For more information, see \n <a href=\"https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch-Unified-Cross-Account.html\">CloudWatch cross-account observability</a>.</p>\n <note>\n <p>If you are using <a href=\"https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/CloudWatch-Logs-Transformation.html\">log transformation</a>, the <code>FilterLogEvents</code> operation returns only the original versions of log events, before they \n were transformed. To view the transformed versions, you must use a <a href=\"https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/AnalyzingLogData.html\">CloudWatch Logs query.</a>\n </p>\n </note>", |
4462 | 4462 | "smithy.api#paginated": { |
4463 | 4463 | "inputToken": "nextToken", |
4464 | 4464 | "outputToken": "nextToken", |
|
5564 | 5564 | "match": { |
5565 | 5565 | "target": "com.amazonaws.cloudwatchlogs#GrokMatch", |
5566 | 5566 | "traits": { |
5567 | | - "smithy.api#documentation": "<p>The grok pattern to match against the log event. For a list of \n supported grok patterns, see <a href=\"https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/CloudWatch-Logs-Transformation.html#Grok-Patterns\">Supported grok patterns</a>.</p>", |
| 5567 | + "smithy.api#documentation": "<p>The grok pattern to match against the log event. For a list of \n supported grok patterns, see <a href=\"https://docs.aws.amazon.com/mazonCloudWatch/latest/logs/CloudWatch-Logs-Transformation-Processors.html#Grok-Patterns\">Supported grok patterns</a>.</p>", |
5568 | 5568 | "smithy.api#required": {} |
5569 | 5569 | } |
5570 | 5570 | } |
|
5578 | 5578 | "traits": { |
5579 | 5579 | "smithy.api#length": { |
5580 | 5580 | "min": 1, |
5581 | | - "max": 128 |
| 5581 | + "max": 512 |
5582 | 5582 | } |
5583 | 5583 | } |
5584 | 5584 | }, |
|
6400 | 6400 | } |
6401 | 6401 | }, |
6402 | 6402 | "traits": { |
6403 | | - "smithy.api#documentation": "<p>This processor takes a list of objects that contain key fields, and converts them into a map of target keys.</p>\n <p>For more information about this processor including examples, see <a href=\"https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/CloudWatch-Logs-Transformation.html#CloudWatch-Logs-Transformation-listToMap\">\n listToMap</a> in the <i>CloudWatch Logs User Guide</i>.</p>" |
| 6403 | + "smithy.api#documentation": "<p>This processor takes a list of objects that contain key fields, and converts them into a map of target keys.</p>\n <p>For more information about this processor including examples, see <a href=\"https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/CloudWatch-Logs-Transformation-Processors.html#CloudWatch-Logs-Transformation-listToMap\">\n listToMap</a> in the <i>CloudWatch Logs User Guide</i>.</p>" |
6404 | 6404 | } |
6405 | 6405 | }, |
6406 | 6406 | "com.amazonaws.cloudwatchlogs#LiveTailSessionLogEvent": { |
|
11352 | 11352 | "smithy.api#documentation": "<p>Use this processor to split a field into an array of strings using a delimiting character.</p>\n <p>For more information about this processor including examples, see <a href=\"https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/CloudWatch-Logs-Transformation.html#CloudWatch-Logs-Transformation-splitString\">\n splitString</a> in the <i>CloudWatch Logs User Guide</i>.</p>" |
11353 | 11353 | } |
11354 | 11354 | }, |
| 11355 | + "com.amazonaws.cloudwatchlogs#SplitStringDelimiter": { |
| 11356 | + "type": "string", |
| 11357 | + "traits": { |
| 11358 | + "smithy.api#length": { |
| 11359 | + "min": 1, |
| 11360 | + "max": 128 |
| 11361 | + } |
| 11362 | + } |
| 11363 | + }, |
11355 | 11364 | "com.amazonaws.cloudwatchlogs#SplitStringEntries": { |
11356 | 11365 | "type": "list", |
11357 | 11366 | "member": { |
|
11375 | 11384 | } |
11376 | 11385 | }, |
11377 | 11386 | "delimiter": { |
11378 | | - "target": "com.amazonaws.cloudwatchlogs#Delimiter", |
| 11387 | + "target": "com.amazonaws.cloudwatchlogs#SplitStringDelimiter", |
11379 | 11388 | "traits": { |
11380 | 11389 | "smithy.api#documentation": "<p>The separator characters to split the string entry on.</p>", |
11381 | 11390 | "smithy.api#required": {} |
|
0 commit comments