Results from /fix:all

Author: opentelemetrybot

content/en/blog/2025/observing-lambdas/index.md

@@ -5,6 +5,7 @@ linkTitle: Observing Lambdas
 date: 2025-01-24
 cSpell:ignore: Dominik
 ---
+
 Getting telemetry data out of modern applications is very straightforward (or at
 least it should be). You set up a collector which either receives data from your
 application or asks it to provide an up-to-date state of various counters. This
@@ -17,13 +18,13 @@ AWS Lambda.
 In this execution model, functions are called directly, and the environment is
 frozen afterward. You’re only billed for actual execution time and no longer
 need a server to wait for incoming requests. This is also where the term
-serverless comes from. Keeping the function alive until metrics can be
-collected isn’t really an option and even if you were willing to pay for that,
-different invocations will have a completely separate context and not
-necessarily know about all the other executions happening simultaneously. You
-might now be saying: "I'll just push all the data at the end of my execution, no
-issues here!", but that doesn’t solve the issue. You’ll still have to pay for
-the time it takes to send the data and with many invocations, this adds up.
+serverless comes from. Keeping the function alive until metrics can be collected
+isn’t really an option and even if you were willing to pay for that, different
+invocations will have a completely separate context and not necessarily know
+about all the other executions happening simultaneously. You might now be
+saying: "I'll just push all the data at the end of my execution, no issues
+here!", but that doesn’t solve the issue. You’ll still have to pay for the time
+it takes to send the data and with many invocations, this adds up.
 
 But there is another way! Lambda extension layers allow you to run any process
 alongside your code, sharing the execution runtime and providing additional
@@ -37,10 +38,12 @@ of the Lambda lifecycle and ensures your telemetry gets to the storage layer.
 When your function is called for the first time, the extension layer starts an
 instance of the OpenTelemetry Collector. The Collector build is a stripped down
 version, providing only components necessary in the context of Lambda. It
-registers with the Lambda [Extensions API](https://docs.aws.amazon.com/lambda/latest/dg/runtimes-extensions-api.html)
-and [Telemetry API](https://docs.aws.amazon.com/lambda/latest/dg/telemetry-api.html). By doing
-this, it receives notifications whenever your function is executed, emits a
-logline, or the execution context is about to be shut down.
+registers with the Lambda
+[Extensions API](https://docs.aws.amazon.com/lambda/latest/dg/runtimes-extensions-api.html)
+and
+[Telemetry API](https://docs.aws.amazon.com/lambda/latest/dg/telemetry-api.html).
+By doing this, it receives notifications whenever your function is executed,
+emits a logline, or the execution context is about to be shut down.
 
 ### This is where the magic happens
 
@@ -54,11 +57,10 @@ its thing.
 
 {{< figure src="diagram-execution-timing.svg" caption="Diagram showcasing how execution timing differs with and without a Collector">}}
 
-
 ## How can I use it?
 
-As of November 2024, the opentelemetry-lambda project publishes [releases of the
-Collector extension layer](https://github.com/open-telemetry/opentelemetry-lambda/releases/tag/layer-collector%2F0.12.0).
+As of November 2024, the opentelemetry-lambda project publishes
+[releases of the Collector extension layer](https://github.com/open-telemetry/opentelemetry-lambda/releases/tag/layer-collector%2F0.12.0).
 It can be configured through a configuration file hosted either in an S3 bucket
 or on an arbitrary HTTP server. It is also possible to bundle the configuration
 file with your Lambda code. In both cases, you have tradeoffs to consider.
@@ -67,8 +69,8 @@ request needs to be made, while bundling the configuration increases the
 management overhead when trying to control the configuration for multiple
 Lambdas.
 
-The simplest way to get started is with an embedded configuration. For this,
-add a file called `collector.yaml` to your function. This is a regular Collector
+The simplest way to get started is with an embedded configuration. For this, add
+a file called `collector.yaml` to your function. This is a regular Collector
 configuration file. To take advantage of the Lambda specific extensions, they
 need to be configured. As an example, the following configuration receives
 traces and logs from the Telemetry API and sends them to another endpoint:

static/refcache.json

@@ -2423,10 +2423,18 @@
     "StatusCode": 206,
     "LastSeen": "2024-07-10T17:01:44.550734457Z"
   },
+  "https://docs.aws.amazon.com/lambda/latest/dg/runtimes-extensions-api.html": {
+    "StatusCode": 206,
+    "LastSeen": "2025-01-24T22:43:02.419614644Z"
+  },
   "https://docs.aws.amazon.com/lambda/latest/dg/services-xray.html": {
     "StatusCode": 206,
     "LastSeen": "2024-01-30T16:14:28.171642-05:00"
   },
+  "https://docs.aws.amazon.com/lambda/latest/dg/telemetry-api.html": {
+    "StatusCode": 206,
+    "LastSeen": "2025-01-24T22:43:04.492478898Z"
+  },
   "https://docs.aws.amazon.com/xray/latest/devguide/aws-xray.html": {
     "StatusCode": 206,
     "LastSeen": "2024-08-02T13:14:36.601347-04:00"
@@ -10179,10 +10187,18 @@
     "StatusCode": 206,
     "LastSeen": "2025-01-13T11:43:25.504793-05:00"
   },
+  "https://github.com/open-telemetry/opentelemetry-lambda/blob/main/collector/README.md": {
+    "StatusCode": 206,
+    "LastSeen": "2025-01-24T22:43:01.001644641Z"
+  },
   "https://github.com/open-telemetry/opentelemetry-lambda/releases": {
     "StatusCode": 200,
     "LastSeen": "2024-08-09T10:44:10.275849-04:00"
   },
+  "https://github.com/open-telemetry/opentelemetry-lambda/releases/tag/layer-collector%2F0.12.0": {
+    "StatusCode": 206,
+    "LastSeen": "2025-01-24T22:43:07.062401954Z"
+  },
   "https://github.com/open-telemetry/opentelemetry-operator": {
     "StatusCode": 206,
     "LastSeen": "2025-01-07T10:31:41.081498-05:00"
@@ -13963,6 +13979,10 @@
     "StatusCode": 200,
     "LastSeen": "2024-08-09T10:45:45.030209-04:00"
   },
+  "https://github.com/theSuess": {
+    "StatusCode": 206,
+    "LastSeen": "2025-01-24T22:42:58.33209764Z"
+  },
   "https://github.com/thegeekyasian/go-chi-otel": {
     "StatusCode": 200,
     "LastSeen": "2024-02-20T05:41:18.324089503Z"