「Observing Lambdas using the OpenTelemetry Collector Extension Layer | OpenTelemetry」

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 happens every minute or so, and if it’s a second late or early, no one really bats an eye. But what if the application isn’t around for long? What if every second waiting for the data to be collected is billed? Then you’re most likely thinking of Function-as-a-Service (FaaS) environments, the most well-known being AWS Lambda.

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 happens every minute or so, and if it’s a second late or early, no one really bats an eye. But what if the application isn’t around for long? What if every second waiting for the data to be collected is billed? Then you’re most likely thinking of Function-as-a-Service (FaaS) environments, the most well-known being AWS Lambda.

Webページ

コンテンツ文字数：0 文字

見出し数（H2/H3タグ）：0 個

閲覧数：7 件

2025-03-11 17:08:09

オリジナルページを開く