Skip to content

Commit 711fe20

Browse files
committed
blog: add ending section
1 parent f8a10e9 commit 711fe20

File tree

1 file changed

+9
-0
lines changed
  • content/en/blog/2025/observing-lambdas

1 file changed

+9
-0
lines changed

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

+9
Original file line numberDiff line numberDiff line change
@@ -105,3 +105,12 @@ function logs appear! You can see this in action in the video below.
105105
<source src="./video-lambda-real-time.webm" />
106106
</video>
107107
</p>
108+
109+
Every log line your Lambda produces will be shipped to the `external-collector`
110+
endpoint specified. You don't need to modify the code at all! From there,
111+
telemetry data flows to your backend as usual. Since the shipping of telemetry
112+
data might be frozen when the lambda is not active, logs can arrive delayed.
113+
They'll either arrive during the next execution or during the shutdown interval.
114+
115+
If you want further insight into your applications, be sure to also check out
116+
the [language specific auto instrumentation layers](https://github.com/open-telemetry/opentelemetry-lambda/?tab=readme-ov-file#extension-layer-language-support).

0 commit comments

Comments
 (0)