-
Notifications
You must be signed in to change notification settings - Fork 184
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
Install all transitive dependencies for Python instrumentation #1483
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,31 +1,4 @@ | ||
opentelemetry-instrumentation-aiohttp-client==0.47b0 | ||
opentelemetry-util-http==0.47b0 | ||
asgiref~=3.8 | ||
opentelemetry-instrumentation-asgi==0.47b0 | ||
opentelemetry-instrumentation-asyncpg==0.47b0 | ||
opentelemetry-instrumentation-boto==0.47b0 | ||
opentelemetry-instrumentation-boto3sqs==0.47b0 | ||
opentelemetry-instrumentation-botocore==0.47b0 | ||
opentelemetry-instrumentation-celery==0.47b0 | ||
opentelemetry-instrumentation-dbapi==0.47b0 | ||
opentelemetry-instrumentation-django==0.47b0 | ||
opentelemetry-instrumentation-elasticsearch==0.47b0 | ||
opentelemetry-instrumentation-fastapi==0.47b0 | ||
opentelemetry-instrumentation-falcon==0.47b0 | ||
opentelemetry-instrumentation-flask==0.47b0 | ||
opentelemetry-instrumentation-grpc==0.47b0 | ||
opentelemetry-instrumentation-jinja2==0.47b0 | ||
opentelemetry-instrumentation-mysql==0.47b0 | ||
opentelemetry-instrumentation-psycopg2==0.47b0 | ||
opentelemetry-instrumentation-pymemcache==0.47b0 | ||
opentelemetry-instrumentation-pymongo==0.47b0 | ||
opentelemetry-instrumentation-pymysql==0.47b0 | ||
opentelemetry-instrumentation-pyramid==0.47b0 | ||
opentelemetry-instrumentation-redis==0.47b0 | ||
opentelemetry-instrumentation-requests==0.47b0 | ||
opentelemetry-instrumentation-sqlalchemy==0.47b0 | ||
opentelemetry-instrumentation-sqlite3==0.47b0 | ||
opentelemetry-instrumentation-starlette==0.47b0 | ||
opentelemetry-instrumentation-tornado==0.47b0 | ||
opentelemetry-instrumentation-wsgi==0.47b0 | ||
# TODO: move these dependencies to requirements.txt when they stopped relying on a pinned version of | ||
# opentelemetry-propagator-aws-xray | ||
opentelemetry-instrumentation-aws-lambda==0.47b0 | ||
opentelemetry-instrumentation-botocore==0.47b0 |
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -2,5 +2,35 @@ opentelemetry-sdk==1.26.0 | |
opentelemetry-exporter-otlp-proto-http==1.26.0 | ||
opentelemetry-distro==0.47b0 | ||
opentelemetry-instrumentation==0.47b0 | ||
opentelemetry-semantic-conventions == 0.47b0 | ||
opentelemetry-semantic-conventions==0.47b0 | ||
opentelemetry-propagator-aws-xray==1.0.2 | ||
|
||
# Instrumentation dependencies | ||
opentelemetry-instrumentation-aiohttp-client==0.47b0 | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. How much does moving all this to the lambda layer increase the layer size? Is that enough to be concerned about for adding to the cold start time? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I simulated locally to check what is the delta: without installing all dependencies
installing all transitive dependencies
The impact on the cold startup will be negligible. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Looks like the last version was 7.4 MB. We can see where things end up with the next release. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. the data presented before regarding size was just for the dependencies and it was not zipped. Here is the resulting layer for reference:
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. So an added 1mb.... that's not insignificant. 🤷 |
||
opentelemetry-util-http==0.47b0 | ||
opentelemetry-instrumentation-asgi==0.47b0 | ||
opentelemetry-instrumentation-asyncpg==0.47b0 | ||
opentelemetry-instrumentation-boto==0.47b0 | ||
opentelemetry-instrumentation-boto3sqs==0.47b0 | ||
opentelemetry-instrumentation-celery==0.47b0 | ||
opentelemetry-instrumentation-dbapi==0.47b0 | ||
opentelemetry-instrumentation-django==0.47b0 | ||
opentelemetry-instrumentation-elasticsearch==0.47b0 | ||
opentelemetry-instrumentation-fastapi==0.47b0 | ||
opentelemetry-instrumentation-falcon==0.47b0 | ||
opentelemetry-instrumentation-flask==0.47b0 | ||
opentelemetry-instrumentation-grpc==0.47b0 | ||
opentelemetry-instrumentation-jinja2==0.47b0 | ||
opentelemetry-instrumentation-mysql==0.47b0 | ||
opentelemetry-instrumentation-psycopg2==0.47b0 | ||
opentelemetry-instrumentation-pymemcache==0.47b0 | ||
opentelemetry-instrumentation-pymongo==0.47b0 | ||
opentelemetry-instrumentation-pymysql==0.47b0 | ||
opentelemetry-instrumentation-pyramid==0.47b0 | ||
opentelemetry-instrumentation-redis==0.47b0 | ||
opentelemetry-instrumentation-requests==0.47b0 | ||
opentelemetry-instrumentation-sqlalchemy==0.47b0 | ||
opentelemetry-instrumentation-sqlite3==0.47b0 | ||
opentelemetry-instrumentation-starlette==0.47b0 | ||
opentelemetry-instrumentation-tornado==0.47b0 | ||
opentelemetry-instrumentation-wsgi==0.47b0 |
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.
Since this is already merged we can make a new Python release and this won't be necessary.
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.
yes, this will work for v.0.48b0 (which is not released yet.). being merged does not mean that it is released.