-
Notifications
You must be signed in to change notification settings - Fork 176
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Lambda exec wrapper calls upstream OTel Python auto instr script #164
Merged
wangzlei
merged 4 commits into
open-telemetry:main
from
NathanielRN:exec-script-calls-upstream-auto-instrument
Oct 28, 2021
Merged
Changes from 1 commit
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
e4276be
Lambda exec wrapper calls upstream OTel Python auto instr script
NathanielRN f5b9cdf
Update testing file to use bash script
NathanielRN a897770
Parse subprocess output to modify environment
NathanielRN 2e3df55
Set OTEL_RESOURCE_ATTRIBUTES without checking for previous value
NathanielRN File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,44 +1,141 @@ | ||
#!/usr/bin/env python3 | ||
# Copyright Amazon.com, Inc. or its affiliates. All Rights Reserved. | ||
# SPDX-License-Identifier: MIT-0 | ||
|
||
from os import environ, system | ||
import sys | ||
|
||
# the path to the interpreter and all of the originally intended arguments | ||
args = sys.argv[1:] | ||
|
||
# enable OTel wrapper | ||
environ["ORIG_HANDLER"] = environ.get("_HANDLER") | ||
environ["_HANDLER"] = "otel_wrapper.lambda_handler" | ||
|
||
# config default traces exporter if missing | ||
environ.setdefault("OTEL_TRACES_EXPORTER", "otlp_proto_grpc_span") | ||
|
||
# set service name | ||
if environ.get("OTEL_RESOURCE_ATTRIBUTES") is None: | ||
environ["OTEL_RESOURCE_ATTRIBUTES"] = "service.name=%s" % ( | ||
environ.get("AWS_LAMBDA_FUNCTION_NAME") | ||
) | ||
elif "service.name=" not in environ.get("OTEL_RESOURCE_ATTRIBUTES"): | ||
environ["OTEL_RESOURCE_ATTRIBUTES"] = "service.name=%s,%s" % ( | ||
environ.get("AWS_LAMBDA_FUNCTION_NAME"), | ||
environ.get("OTEL_RESOURCE_ATTRIBUTES"), | ||
) | ||
|
||
# TODO: Remove if sdk support resource detector env variable configuration. | ||
lambda_resource_attributes = ( | ||
"cloud.region=%s,cloud.provider=aws,faas.name=%s,faas.version=%s" | ||
% ( | ||
environ.get("AWS_REGION"), | ||
environ.get("AWS_LAMBDA_FUNCTION_NAME"), | ||
environ.get("AWS_LAMBDA_FUNCTION_VERSION"), | ||
) | ||
) | ||
environ["OTEL_RESOURCE_ATTRIBUTES"] = "%s,%s" % ( | ||
lambda_resource_attributes, | ||
environ.get("OTEL_RESOURCE_ATTRIBUTES"), | ||
) | ||
|
||
# start the runtime with the extra options | ||
system(" ".join(args)) | ||
#!/usr/bin/env bash | ||
|
||
# Copyright The OpenTelemetry Authors | ||
# | ||
# Licensed under the Apache License, Version 2.0 (the "License"); | ||
# you may not use this file except in compliance with the License. | ||
# You may obtain a copy of the License at | ||
# | ||
# http://www.apache.org/licenses/LICENSE-2.0 | ||
# | ||
# Unless required by applicable law or agreed to in writing, software | ||
# distributed under the License is distributed on an "AS IS" BASIS, | ||
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. | ||
# See the License for the specific language governing permissions and | ||
# limitations under the License. | ||
|
||
: ' | ||
`otel-instrument` | ||
This script configures and sets up OpenTelemetry Python with the values we | ||
expect will be used by the common user. It does this by setting the environment | ||
variables OpenTelemetry uses, and then initializing OpenTelemetry using the | ||
`opentelemetry-instrument` auto instrumentation script from the | ||
`opentelemetry-instrumentation` package. | ||
Additionally, this configuration assumes the user is using packages conforming | ||
to the `opentelemetry-instrumentation` and `opentelemetry-sdk` specifications. | ||
DO NOT use this script for anything else besides SETTING ENVIRONMENT VARIABLES. | ||
See more: | ||
https://docs.aws.amazon.com/lambda/latest/dg/runtimes-modify.html#runtime-wrapper | ||
Usage | ||
----- | ||
We expect this file to be at the root of a Lambda Layer. Having it anywhere else | ||
seems to mean AWS Lambda cannot find it. | ||
In the configuration of an AWS Lambda function with this file at the | ||
root level of a Lambda Layer: | ||
.. code:: | ||
AWS_LAMBDA_EXEC_WRAPPER = /opt/otel-instrument | ||
' | ||
|
||
# Use constants to access the environment variables we want to use in this | ||
# script. | ||
|
||
# See more: | ||
# https://docs.aws.amazon.com/lambda/latest/dg/configuration-envvars.html#configuration-envvars-runtime | ||
|
||
# - Reserved environment variables | ||
|
||
# - - $AWS_LAMBDA_FUNCTION_NAME | ||
# - - $LAMBDA_RUNTIME_DIR | ||
|
||
# - Unreserved environment variables | ||
|
||
# - - $PYTHONPATH | ||
|
||
# Update the python paths for packages with `sys.path` and `PYTHONPATH` | ||
|
||
# - We know that the path to the Lambda Layer OpenTelemetry Python packages are | ||
# well defined, so we can add them to the PYTHONPATH. | ||
# | ||
# See more: | ||
# https://docs.aws.amazon.com/lambda/latest/dg/configuration-layers.html#configuration-layers-path | ||
|
||
export LAMBDA_LAYER_PKGS_DIR="/opt/python" | ||
|
||
# - Set Lambda Layer python packages in PYTHONPATH so `opentelemetry-instrument` | ||
# script can find them (it needs to find `opentelemetry` to find the auto | ||
# instrumentation `run()` method later) | ||
|
||
if [ -z ${PYTHONPATH} ]; then | ||
export PYTHONPATH=$LAMBDA_LAYER_PKGS_DIR; | ||
else | ||
export PYTHONPATH="$LAMBDA_LAYER_PKGS_DIR:$PYTHONPATH"; | ||
fi | ||
|
||
# - Set Lambda runtime python packages in PYTHONPATH so | ||
# `opentelemetry-instrument` script can find them during auto instrumentation | ||
# and instrument them. | ||
|
||
export PYTHONPATH="$LAMBDA_RUNTIME_DIR:$PYTHONPATH"; | ||
|
||
# Configure OpenTelemetry Python with environment variables | ||
|
||
# - Set the default Trace Exporter | ||
|
||
if [ -z ${OTEL_TRACES_EXPORTER} ]; then | ||
export OTEL_TRACES_EXPORTER="otlp_proto_grpc_span"; | ||
NathanielRN marked this conversation as resolved.
Show resolved
Hide resolved
|
||
fi | ||
|
||
# - Set the service name | ||
|
||
if [ -z ${OTEL_SERVICE_NAME} ]; then | ||
export OTEL_SERVICE_NAME=$AWS_LAMBDA_FUNCTION_NAME; | ||
fi | ||
|
||
# - Set the Resource Detectors (Resource Attributes) | ||
# | ||
# TODO: waiting on OTel Python support for configuring Resource Detectors from | ||
# an environment variable. Replace the bottom code with the following when | ||
# this is possible. | ||
# | ||
# export OTEL_RESOURCE_DETECTORS="aws_lambda"; | ||
# | ||
export LAMBDA_RESOURCE_ATTRIBUTES="cloud.region=$AWS_REGION,cloud.provider=aws,faas.name=$AWS_LAMBDA_FUNCTION_NAME,faas.version=$AWS_LAMBDA_FUNCTION_VERSION" | ||
|
||
if [ -z ${OTEL_RESOURCE_ATTRIBUTES} ]; then | ||
export OTEL_RESOURCE_ATTRIBUTES=$LAMBDA_RESOURCE_ATTRIBUTES; | ||
else | ||
export OTEL_RESOURCE_ATTRIBUTES="$LAMBDA_RESOURCE_ATTRIBUTES,$OTEL_RESOURCE_ATTRIBUTES"; | ||
fi | ||
|
||
# - Set the default propagators | ||
|
||
if [ -z ${OTEL_PROPAGATORS} ]; then | ||
export OTEL_PROPAGATORS="tracecontext,b3,xray"; | ||
NathanielRN marked this conversation as resolved.
Show resolved
Hide resolved
|
||
fi | ||
|
||
# - Use a wrapper because AWS Lambda's `python3 /var/runtime/bootstrap.py` will | ||
# use `imp.load_module` to load the function from the `_HANDLER` environment | ||
# variable. This RELOADS the module and REMOVES any instrumentation patching | ||
# done earlier. So we delay instrumentation until `boostrap.py` imports | ||
# `otel_wrapper.py` at which we know the patching will be picked up. | ||
# | ||
# See more: | ||
# https://docs.python.org/3/library/imp.html#imp.load_module | ||
|
||
export ORIG_HANDLER=$_HANDLER; | ||
export _HANDLER="otel_wrapper.lambda_handler"; | ||
|
||
# - Call the upstream auto instrumentation script | ||
|
||
python3 $LAMBDA_LAYER_PKGS_DIR/bin/opentelemetry-instrument "$@" | ||
|
||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For any path type variabe it's conventional to not check for presence, empty strings are fine (they should be made fine for the resource attributes variable in the python SDK separately too at some point)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay sounds good! Yeah I didn't know if user would dislike us modifying a variable they already set, but then again they're probably using this script BECAUSE they want us to handle all these little settings 😛
Changed it to this!
And I guess you mean in the future someone can do this:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks again for the prompt!
I looked into this and am fairly certain OTel Python SDK currently does handle empty Resource Attributes.
They even have a test to protect against this:
So I'll simplify this even further!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I actually was wrong about this... I've made a PR to fix this upstream: open-telemetry/opentelemetry-python#2256
And will follow up with a fix #173