Skip to content

Automatically capture common HTTP attributes for Load Balancer/API Gateway events #1087

@ericksoen

Description

@ericksoen

Is your feature request related to a problem?
We invoke our AWS Lambda functions from both an Elastic Load Balancer (ELB) and API Gateway. We perform manual instrumentation to add attributes like http.status_code, http.url, http.method, etc., but do this for every Lambda function that implements OpenTelemetry. This also introduces the possibility that teams deviate from the OpenTelemetry HTTP semantic conventions for attribubutes, e.g., http.statusCode (WRONG) vs. http.status_code (correct).

Describe the solution you'd like
Automatically capture common HTTP attributes for AWS Lambda invocations that originate from a Load Balancer or API Gateway.

Describe alternatives you've considered
Continue manually instrumenting Lambda functions to capture these properties (may be useful to provide more user control over potentially sensitive attributes like http.url and http.target (both of which includes query string params)

Additional context
Add any other context about the feature request here.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions