跳到主要内容
跳到主要内容

AWS Lambda

本指南集成以下内容：

✅ 日志✅ 指标✅ 链路追踪

安装 OpenTelemetry Lambda 层​

OpenTelemetry 项目提供了独立的 Lambda 层，用于：

  1. 使用 OpenTelemetry 自动埋点功能自动为你的 Lambda 函数代码进行监测。
  2. 将收集到的日志、指标和链路追踪数据转发到 ClickStack。

添加特定语言的自动埋点层​

特定语言的自动埋点 Lambda layer 会使用适用于该语言的 OpenTelemetry 自动埋点包，自动对你的 Lambda 函数代码进行埋点。

每种语言和每个 Region 都有各自的 layer ARN。

如果你的 Lambda 已经通过 OpenTelemetry SDK 完成埋点，可以跳过此步骤。

开始操作：

  1. 在 Layers 部分点击 “Add a layer”
  2. 选择 “Specify an ARN”，并根据语言选择对应的 ARN，确保将 <region> 替换为你的 Region（例如 us-east-2）：
arn:aws:lambda:<region>:184161586896:layer:opentelemetry-nodejs-0_7_0:1

The latest releases of the layers can be found in the OpenTelemetry Lambda Layers GitHub repository.

  1. Configure the following environment variables in your Lambda function under "Configuration" > "Environment variables".
OTEL_EXPORTER_OTLP_ENDPOINT=http://localhost:4318
AWS_LAMBDA_EXEC_WRAPPER=/opt/otel-handler
OTEL_PROPAGATORS=tracecontext
OTEL_TRACES_SAMPLER=always_on

Installing the OpenTelemetry collector Lambda layer​

The collector Lambda layer allows you to forward logs, metrics, and traces from your Lambda function to ClickStack without impacting response times due to exporter latency.

To install the collector layer:

  1. In the Layers section click "Add a layer"
  2. Select specify an ARN and choose the correct ARN based on architecture, ensure you replace the <region> with your region (ex. us-east-2):
    arn:aws:lambda:<region>:184161586896:layer:opentelemetry-collector-amd64-0_8_0:1
  1. Add the following collector.yaml file to your project to configure the collector to send to ClickStack:
# collector.yaml \{#collectoryaml}
receivers:
  otlp:
    protocols:
      grpc:
        endpoint: 'localhost:4317'
      http:
        endpoint: 'localhost:4318'

processors:
  batch:
  decouple:

exporters:
  otlphttp:
    endpoint: "<YOU_OTEL_COLLECTOR_HTTP_ENDPOINT>
    headers:
      authorization: <YOUR_INGESTION_API_KEY>
    compression: gzip

service:
  pipelines:
    traces:
      receivers: [otlp]
      processors: [batch, decouple]
      exporters: [otlphttp]
    metrics:
      receivers: [otlp]
      processors: [batch, decouple]
      exporters: [otlphttp]
    logs:
      receivers: [otlp]
      processors: [batch, decouple]
      exporters: [otlphttp]
  1. Add the following environment variable:
OPENTELEMETRY_COLLECTOR_CONFIG_FILE=/var/task/collector.yaml

Checking the installation​

After deploying the layers, you should now see traces automatically collected from your Lambda function in HyperDX. The decouple and batching processor may introduce a delay in telemetry collection, so traces may be delayed in showing up. To emit custom logs or metrics, you'll need to instrument your code your language-specific OpenTelemetry SDKs.

Troubleshooting​

Custom instrumentation not sending​

If you're not seeing your manually defined traces or other telemetry, you may be using an incompatible version of the OpenTelemetry API package. Ensure your OpenTelemetry API package is at least the same or lower version than the version included in the AWS lambda.

Enabling SDK debug logs​

Set the OTEL_LOG_LEVEL environment variable to DEBUG to enable debug logs from the OpenTelemetry SDK. This will help ensure that the auto-instrumentation layer is correctly instrumenting your application.

Enabling collector debug logs​

To debug collector issues, you can enable debug logs by modifying your collector configuration file to add the logging exporter and setting the telemetry log level to debug to enable more verbose logging from the collector lambda layer.

# collector.yaml \{#collectoryaml}
receivers:
  otlp:
    protocols:
      grpc:
        endpoint: 'localhost:4317'
      http:
        endpoint: 'localhost:4318'

exporters:
  logging:
    verbosity: detailed
  otlphttp:
    endpoint: "https://in-otel.hyperdx.io"
    headers:
      authorization: <您的摄取_API_密钥>
    compression: gzip

service:
  telemetry:
    logs:
      level: "debug"
  pipelines:
    traces:
      receivers: [otlp]
      processors: [batch, decouple]
      exporters: [otlphttp, logging]
    metrics:
      receivers: [otlp]
      processors: [batch, decouple]
      exporters: [otlphttp, logging]
    logs:
      receivers: [otlp]
      processors: [batch, decouple]
      exporters: [otlphttp, logging]