You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
andhttp.target
(both of which includes query string params)Additional context
Add any other context about the feature request here.
The text was updated successfully, but these errors were encountered: