AWS prescriptive-guidance documentation change
Summary
Fixed broken links, corrected punctuation, and updated product name capitalization. No functional changes to logging/monitoring guidance.
Security assessment
Changes include URL corrections (removed double slashes), apostrophe standardization, and capitalization fixes ('CloudWatch Metrics' → 'Amazon CloudWatch metrics'). No security vulnerabilities, configurations, or features are mentioned or modified. Changes are purely editorial with no security implications.
Diff
diff --git a/prescriptive-guidance/latest/implementing-logging-monitoring-cloudwatch/lambda-logging-metrics.md b/prescriptive-guidance/latest/implementing-logging-monitoring-cloudwatch/lambda-logging-metrics.md index d426b3b05..bd6b97bf5 100644 --- a//prescriptive-guidance/latest/implementing-logging-monitoring-cloudwatch/lambda-logging-metrics.md +++ b//prescriptive-guidance/latest/implementing-logging-monitoring-cloudwatch/lambda-logging-metrics.md @@ -5 +5 @@ -[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Designing and implementing logging and monitoring with Amazon CloudWatch ](welcome.html) +[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Designing and implementing logging and monitoring with Amazon CloudWatch](introduction.html) @@ -11 +11 @@ Lambda function loggingSending logs to other destinations from CloudWatchLambda -[ Lambda ](https://docs.aws.amazon.com/lambda/latest/dg/welcome.html)removes the need to manage and monitor servers for your workloads and automatically works with CloudWatch Metrics and CloudWatch Logs without further configuration or instrumentation of your application's code. This section helps you understand the performance characteristics of the systems used by Lambda and how your configuration choices influence performance. It also helps you log and monitor your Lambda functions for performance optimization and diagnosing application-level issues. +[Lambda ](https://docs.aws.amazon.com/lambda/latest/dg/welcome.html)removes the need to manage and monitor servers for your workloads and automatically works with Amazon CloudWatch metrics and CloudWatch Logs without further configuration or instrumentation of your application's code. This section helps you understand the performance characteristics of the systems used by Lambda and how your configuration choices influence performance. It also helps you log and monitor your Lambda functions for performance optimization and diagnosing application-level issues. @@ -39 +38 @@ Lambda allows you to set environment variables for your Lambda function runtime -You can send logs to other destinations (for example, Amazon OpenSearch Service or a Lambda function) by using subscription filters. If you don’t use Amazon OpenSearch Service, you can use a Lambda function to process the logs and send them to an AWS service of your choice using the AWS SDKs. +You can send logs to other destinations (for example, Amazon OpenSearch Service or a Lambda function) by using subscription filters. If you don't use Amazon OpenSearch Service, you can use a Lambda function to process the logs and send them to an AWS service of your choice using the AWS SDKs. @@ -49 +48 @@ Lambda lets you run your code without managing or scaling servers and this almos -Lambda automatically integrates with CloudWatch Metrics and provides a set of [standard metrics for your Lambda functions](https://docs.aws.amazon.com//lambda/latest/dg/monitoring-metrics.html). Lambda also provides a separate monitoring dashboard for each Lambda function with these metrics. Two important metrics that you need to monitor are errors and invocation errors. Understanding the differences between invocation errors and other error types helps you diagnose and support Lambda deployments. +Lambda automatically integrates with CloudWatch Metrics and provides a set of [standard metrics for your Lambda functions](https://docs.aws.amazon.com/lambda/latest/dg/monitoring-metrics.html). Lambda also provides a separate monitoring dashboard for each Lambda function with these metrics. Two important metrics that you need to monitor are errors and invocation errors. Understanding the differences between invocation errors and other error types helps you diagnose and support Lambda deployments. @@ -51 +50 @@ Lambda automatically integrates with CloudWatch Metrics and provides a set of [s -[Invocation errors](https://docs.aws.amazon.com/lambda/latest/api/API_Invoke.html) prevent your Lambda function from running. These errors occur before your code is run so you can’t implement error handling within your code to identify them. Instead, you should configure alarms for your Lambda functions that detect these errors and notify the operations and workload owners. These errors are often related to a configuration or permission error and can occur because of a change in your configuration or permissions. Invocation errors might initiate a retry, which causes multiple invocations of your function. +[Invocation errors](https://docs.aws.amazon.com/lambda/latest/api/API_Invoke.html) prevent your Lambda function from running. These errors occur before your code is run so you can't implement error handling within your code to identify them. Instead, you should configure alarms for your Lambda functions that detect these errors and notify the operations and workload owners. These errors are often related to a configuration or permission error and can occur because of a change in your configuration or permissions. Invocation errors might initiate a retry, which causes multiple invocations of your function. @@ -55 +54 @@ A successfully invoked Lambda function returns an HTTP 200 response even if an e -CloudWatch provides [CloudWatch Lambda Insights](https://docs.aws.amazon.com//lambda/latest/dg/monitoring-insights.html) that you can enable for individual Lambda function. Lambda Insights collects, aggregates, and summarizes system-level metrics (for example, CPU time, memory, disk and network usage). Lambda Insights also collects, aggregates, and summarizes diagnostic information (for example, cold starts and Lambda worker shutdowns) to help you isolate and quickly resolve issues. +CloudWatch provides [CloudWatch Lambda Insights](https://docs.aws.amazon.com/lambda/latest/dg/monitoring-insights.html) that you can enable for individual Lambda function. Lambda Insights collects, aggregates, and summarizes system-level metrics (for example, CPU time, memory, disk and network usage). Lambda Insights also collects, aggregates, and summarizes diagnostic information (for example, cold starts and Lambda worker shutdowns) to help you isolate and quickly resolve issues. @@ -61 +60 @@ Lambda Insights uses the embedded metric format to automatically emit performanc -You can also create and capture your own application metrics in CloudWatch using the embedded metric format. You can leverage [AWS provided libraries for embedded metric format](https://docs.aws.amazon.com//AmazonCloudWatch/latest/monitoring/CloudWatch_Embedded_Metric_Format_Libraries.html) to create and emit embedded metric format statements to CloudWatch. The integrated Lambda CloudWatch logging facility is configured to process and extract appropriately formatted embedded metric format statements. +You can also create and capture your own application metrics in CloudWatch using the embedded metric format. You can leverage [AWS provided libraries for embedded metric format](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch_Embedded_Metric_Format_Libraries.html) to create and emit embedded metric format statements to CloudWatch. The integrated Lambda CloudWatch logging facility is configured to process and extract appropriately formatted embedded metric format statements.