AWS AmazonCloudWatch documentation change
Summary
Updated documentation for data format descriptions with punctuation fixes and expanded 'Custom' data format explanation to include log group tags
Security assessment
Changes are grammatical improvements and clarification of log processing mechanics without security-specific context
Diff
diff --git a/AmazonCloudWatch/latest/logs/data-source-discovery-management.md b/AmazonCloudWatch/latest/logs/data-source-discovery-management.md index 8b73ada75..f15aa350a 100644 --- a//AmazonCloudWatch/latest/logs/data-source-discovery-management.md +++ b//AmazonCloudWatch/latest/logs/data-source-discovery-management.md @@ -44 +43,0 @@ Data Sources categorize logs using two key identifiers: -A schema defines the structure of log data, including what fields are present and how information is organized. A single data source can produce multiple types of logs with different schemas and purposes. For example, the AWS CloudTrail data source has two types: management events ( which track control plane operations like creating or deleting resources) and data events (which track data plane operations like S3 object access). Each type has a different schema because they capture different kinds of information. @@ -47,0 +47 @@ A schema defines the structure of log data, including what fields are present an +A schema defines the structure of log data, including what fields are present and how information is organized. A single data source can produce multiple types of logs with different schemas and purposes. For example, the AWS CloudTrail data source has two types: management events (which track control plane operations like creating or deleting resources) and data events (which track data plane operations like S3 object access). Each type has a different schema because they capture different kinds of information. @@ -95 +95 @@ The `@data_format` field can contain one of the following values: - * `Default` \- Logs ingested without modification + * `Default` \- Logs ingested without modification. @@ -97 +97 @@ The `@data_format` field can contain one of the following values: - * `Custom` \- Logs processed through pipeline processors + * `Custom` \- Logs processed through pipeline processors or logs ingested into log group with data source name/type tags. @@ -99 +99 @@ The `@data_format` field can contain one of the following values: - * `OCSF-<version>` \- Logs processed with OCSF (Open Cybersecurity Schema Framework) processors in pipelines + * `OCSF-<version>` \- Logs processed with OCSF (Open Cybersecurity Schema Framework) processors in pipelines. @@ -101 +101 @@ The `@data_format` field can contain one of the following values: - * `AWS-OTEL-LOG-V<version>` \- OpenTelemetry logs ingested through the CloudWatch OTLP endpoint + * `AWS-OTEL-LOG-V<version>` \- OpenTelemetry logs ingested through the CloudWatch OTLP endpoint. @@ -103 +103 @@ The `@data_format` field can contain one of the following values: - * `AWS-OTEL-TRACE-V<version>` \- OpenTelemetry traces ingested through the CloudWatch OTLP endpoint + * `AWS-OTEL-TRACE-V<version>` \- OpenTelemetry traces ingested through the CloudWatch OTLP endpoint.