PyPI - opentelemetry-instrumentation - Versions diffs - 0.43b0__tar.gz → 0.45b0__tar.gz - Mend

opentelemetry-instrumentation 0.43b0tar.gz → 0.45b0tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (29) hide show

{opentelemetry_instrumentation-0.43b0 → opentelemetry_instrumentation-0.45b0}/PKG-INFO RENAMED Viewed

@@ -1,6 +1,6 @@
-Metadata-Version: 2.1
+Metadata-Version: 2.3
 Name: opentelemetry-instrumentation
-Version: 0.43b0
+Version: 0.45b0
 Summary: Instrumentation Tools & Auto Instrumentation for OpenTelemetry Python
 Project-URL: Homepage, https://github.com/open-telemetry/opentelemetry-python-contrib/tree/main/opentelemetry-instrumentation
 Author-email: OpenTelemetry Authors <cncf-opentelemetry-contributors@lists.cncf.io>
@@ -11,16 +11,14 @@ Classifier: Intended Audience :: Developers
 Classifier: License :: OSI Approved :: Apache Software License
 Classifier: Programming Language :: Python
 Classifier: Programming Language :: Python :: 3
-Classifier: Programming Language :: Python :: 3.7
 Classifier: Programming Language :: Python :: 3.8
 Classifier: Programming Language :: Python :: 3.9
 Classifier: Programming Language :: Python :: 3.10
 Classifier: Programming Language :: Python :: 3.11
-Requires-Python: >=3.7
+Requires-Python: >=3.8
 Requires-Dist: opentelemetry-api~=1.4
 Requires-Dist: setuptools>=16.0
 Requires-Dist: wrapt<2.0.0,>=1.0.0
-Provides-Extra: test
 Description-Content-Type: text/x-rst
 OpenTelemetry Instrumentation
@@ -39,7 +37,7 @@ Installation
     pip install opentelemetry-instrumentation
-This package provides a couple of commands that help automatically instruments a program:
+This package provides commands that help automatically instrument a program:
 .. note::
     You need to install a distro package to get auto instrumentation working. The ``opentelemetry-distro``
@@ -47,7 +45,7 @@ This package provides a couple of commands that help automatically instruments a
     For more info about ``opentelemetry-distro`` check `here <https://opentelemetry-python.readthedocs.io/en/latest/examples/distro/README.html>`__
     ::
-        pip install opentelemetry-distro[otlp]
+        pip install "opentelemetry-distro[otlp]"
     When creating a custom distro and/or configurator, be sure to add entry points for each under `opentelemetry_distro` and `opentelemetry_configurator` respectfully.
     If you have entry points for multiple distros or configurators present in your environment, you should specify the entry point name of the distro and configurator you want to be used via the `OTEL_PYTHON_DISTRO` and `OTEL_PYTHON_CONFIGURATOR` environment variables.
@@ -58,13 +56,14 @@ opentelemetry-bootstrap
 ::
-    opentelemetry-bootstrap --action=install|requirements
+    opentelemetry-bootstrap [-a |--action=][install|requirements]
-This commands inspects the active Python site-packages and figures out which
-instrumentation packages the user might want to install. By default it prints out
-a list of the suggested instrumentation packages which can be added to a requirements.txt
-file. It also supports installing the suggested packages when run with :code:`--action=install`
-flag.
+This command install default instrumentation packages and detects active Python site-packages
+to figure out which instrumentation packages the user might want to install. By default, it
+prints out a list of the default and detected instrumentation packages that can be added to a
+requirements.txt file. It also supports installing the packages when run with
+:code:`--action=install` or :code:`-a install` flag. All default and detectable
+instrumentation packages are defined `here <https://github.com/flands/opentelemetry-python-contrib/blob/main/opentelemetry-instrumentation/src/opentelemetry/instrumentation/bootstrap_gen.py>`.
 opentelemetry-instrument
@@ -76,12 +75,12 @@ opentelemetry-instrument
 The instrument command will try to automatically detect packages used by your python program
 and when possible, apply automatic tracing instrumentation on them. This means your program
-will get automatic distributed tracing for free without having to make any code changes
-at all. This will also configure a global tracer and tracing exporter without you having to
-make any code changes. By default, the instrument command will use the OTLP exporter but
-this can be overridden when needed.
+will get automatic distributed tracing without having to make any code changes. This will
+also configure a global tracer and tracing exporter as well as a meter and meter exporter.
+By default, the instrument command will use the OTLP exporter but this can be overridden.
-The command supports the following configuration options as CLI arguments and environment vars:
+The command supports the following configuration options as CLI arguments and environment
+variables:
 * ``--traces_exporter`` or ``OTEL_TRACES_EXPORTER``
@@ -89,27 +88,32 @@ The command supports the following configuration options as CLI arguments and en
 * ``--distro`` or ``OTEL_PYTHON_DISTRO``
 * ``--configurator`` or ``OTEL_PYTHON_CONFIGURATOR``
-Used to specify which trace exporter to use. Can be set to one or more of the well-known exporter
-names (see below).
+The exporter options define what exporter destination to use and can be set to one or more
+exporter names (see below). You can pass multiple values to configure multiple exporters
+(e.g., ``zipkin_json,otlp``).
     - Defaults to `otlp`.
     - Can be set to `none` to disable automatic tracer initialization.
+    - Can be set to 'console` to display JSON results locally.
-You can pass multiple values to configure multiple exporters e.g, ``zipkin,prometheus``
-Well known trace exporter names:
+Trace exporter names:
     - jaeger_proto
     - jaeger_thrift
     - opencensus
+    - otlp
+    - otlp_proto_grpc (`deprecated`)
+    - otlp_proto_http (`deprecated`)
     - zipkin_json
     - zipkin_proto
+Metric exporter names:
     - otlp
     - otlp_proto_grpc (`deprecated`)
-    - otlp_proto_http (`deprecated`)
+    - prometheus
 Note: The default transport protocol for ``otlp`` is gRPC.
-HTTP is currently supported for traces only, and should be set using ``OTEL_EXPORTER_OTLP_TRACES_PROTOCOL=http/protobuf``
 * ``--id-generator`` or ``OTEL_PYTHON_ID_GENERATOR``
@@ -131,9 +135,9 @@ Examples
 ::
-    opentelemetry-instrument --traces_exporter otlp flask run --port=3000
+    opentelemetry-instrument --traces_exporter console flask run --port=3000
-The above command will pass ``--traces_exporter otlp`` to the instrument command and ``--port=3000`` to ``flask run``.
+The above command will pass ``--traces_exporter console`` to the instrument command and ``--port=3000`` to ``flask run``.
 ::

{opentelemetry_instrumentation-0.43b0 → opentelemetry_instrumentation-0.45b0}/README.rst RENAMED Viewed

@@ -14,7 +14,7 @@ Installation
     pip install opentelemetry-instrumentation
-This package provides a couple of commands that help automatically instruments a program:
+This package provides commands that help automatically instrument a program:
 .. note::
     You need to install a distro package to get auto instrumentation working. The ``opentelemetry-distro``
@@ -22,7 +22,7 @@ This package provides a couple of commands that help automatically instruments a
     For more info about ``opentelemetry-distro`` check `here <https://opentelemetry-python.readthedocs.io/en/latest/examples/distro/README.html>`__
     ::
-        pip install opentelemetry-distro[otlp]
+        pip install "opentelemetry-distro[otlp]"
     When creating a custom distro and/or configurator, be sure to add entry points for each under `opentelemetry_distro` and `opentelemetry_configurator` respectfully.
     If you have entry points for multiple distros or configurators present in your environment, you should specify the entry point name of the distro and configurator you want to be used via the `OTEL_PYTHON_DISTRO` and `OTEL_PYTHON_CONFIGURATOR` environment variables.
@@ -33,13 +33,14 @@ opentelemetry-bootstrap
 ::
-    opentelemetry-bootstrap --action=install|requirements
+    opentelemetry-bootstrap [-a |--action=][install|requirements]
-This commands inspects the active Python site-packages and figures out which
-instrumentation packages the user might want to install. By default it prints out
-a list of the suggested instrumentation packages which can be added to a requirements.txt
-file. It also supports installing the suggested packages when run with :code:`--action=install`
-flag.
+This command install default instrumentation packages and detects active Python site-packages
+to figure out which instrumentation packages the user might want to install. By default, it
+prints out a list of the default and detected instrumentation packages that can be added to a
+requirements.txt file. It also supports installing the packages when run with
+:code:`--action=install` or :code:`-a install` flag. All default and detectable
+instrumentation packages are defined `here <https://github.com/flands/opentelemetry-python-contrib/blob/main/opentelemetry-instrumentation/src/opentelemetry/instrumentation/bootstrap_gen.py>`.
 opentelemetry-instrument
@@ -51,12 +52,12 @@ opentelemetry-instrument
 The instrument command will try to automatically detect packages used by your python program
 and when possible, apply automatic tracing instrumentation on them. This means your program
-will get automatic distributed tracing for free without having to make any code changes
-at all. This will also configure a global tracer and tracing exporter without you having to
-make any code changes. By default, the instrument command will use the OTLP exporter but
-this can be overridden when needed.
+will get automatic distributed tracing without having to make any code changes. This will
+also configure a global tracer and tracing exporter as well as a meter and meter exporter.
+By default, the instrument command will use the OTLP exporter but this can be overridden.
-The command supports the following configuration options as CLI arguments and environment vars:
+The command supports the following configuration options as CLI arguments and environment
+variables:
 * ``--traces_exporter`` or ``OTEL_TRACES_EXPORTER``
@@ -64,27 +65,32 @@ The command supports the following configuration options as CLI arguments and en
 * ``--distro`` or ``OTEL_PYTHON_DISTRO``
 * ``--configurator`` or ``OTEL_PYTHON_CONFIGURATOR``
-Used to specify which trace exporter to use. Can be set to one or more of the well-known exporter
-names (see below).
+The exporter options define what exporter destination to use and can be set to one or more
+exporter names (see below). You can pass multiple values to configure multiple exporters
+(e.g., ``zipkin_json,otlp``).
     - Defaults to `otlp`.
     - Can be set to `none` to disable automatic tracer initialization.
+    - Can be set to 'console` to display JSON results locally.
-You can pass multiple values to configure multiple exporters e.g, ``zipkin,prometheus``
-Well known trace exporter names:
+Trace exporter names:
     - jaeger_proto
     - jaeger_thrift
     - opencensus
+    - otlp
+    - otlp_proto_grpc (`deprecated`)
+    - otlp_proto_http (`deprecated`)
     - zipkin_json
     - zipkin_proto
+Metric exporter names:
     - otlp
     - otlp_proto_grpc (`deprecated`)
-    - otlp_proto_http (`deprecated`)
+    - prometheus
 Note: The default transport protocol for ``otlp`` is gRPC.
-HTTP is currently supported for traces only, and should be set using ``OTEL_EXPORTER_OTLP_TRACES_PROTOCOL=http/protobuf``
 * ``--id-generator`` or ``OTEL_PYTHON_ID_GENERATOR``
@@ -106,9 +112,9 @@ Examples
 ::
-    opentelemetry-instrument --traces_exporter otlp flask run --port=3000
+    opentelemetry-instrument --traces_exporter console flask run --port=3000
-The above command will pass ``--traces_exporter otlp`` to the instrument command and ``--port=3000`` to ``flask run``.
+The above command will pass ``--traces_exporter console`` to the instrument command and ``--port=3000`` to ``flask run``.
 ::

{opentelemetry_instrumentation-0.43b0 → opentelemetry_instrumentation-0.45b0}/pyproject.toml RENAMED Viewed

@@ -8,7 +8,7 @@ dynamic = ["version"]
 description = "Instrumentation Tools & Auto Instrumentation for OpenTelemetry Python"
 readme = "README.rst"
 license = "Apache-2.0"
-requires-python = ">=3.7"
+requires-python = ">=3.8"
 authors = [
   { name = "OpenTelemetry Authors", email = "cncf-opentelemetry-contributors@lists.cncf.io" },
 ]
@@ -18,7 +18,6 @@ classifiers = [
   "License :: OSI Approved :: Apache Software License",
   "Programming Language :: Python",
   "Programming Language :: Python :: 3",
-  "Programming Language :: Python :: 3.7",
   "Programming Language :: Python :: 3.8",
   "Programming Language :: Python :: 3.9",
   "Programming Language :: Python :: 3.10",
@@ -30,9 +29,6 @@ dependencies = [
   "wrapt >= 1.0.0, < 2.0.0",
 ]
-[project.optional-dependencies]
-test = []
 [project.scripts]
 opentelemetry-bootstrap = "opentelemetry.instrumentation.bootstrap:run"
 opentelemetry-instrument = "opentelemetry.instrumentation.auto_instrumentation:run"

{opentelemetry_instrumentation-0.43b0 → opentelemetry_instrumentation-0.45b0}/src/opentelemetry/instrumentation/auto_instrumentation/__init__.py RENAMED Viewed

@@ -1,5 +1,3 @@
-#!/usr/bin/env python3
 # Copyright The OpenTelemetry Authors
 #
 # Licensed under the Apache License, Version 2.0 (the "License");

{opentelemetry_instrumentation-0.43b0 → opentelemetry_instrumentation-0.45b0}/src/opentelemetry/instrumentation/bootstrap.py RENAMED Viewed

@@ -1,5 +1,3 @@
-#!/usr/bin/env python3
 # Copyright The OpenTelemetry Authors
 #
 # Licensed under the Apache License, Version 2.0 (the "License");

{opentelemetry_instrumentation-0.43b0 → opentelemetry_instrumentation-0.45b0}/src/opentelemetry/instrumentation/bootstrap_gen.py RENAMED Viewed

@@ -18,178 +18,179 @@
 libraries = [
     {
         "library": "aio_pika >= 7.2.0, < 10.0.0",
-        "instrumentation": "opentelemetry-instrumentation-aio-pika==0.43b0",
+        "instrumentation": "opentelemetry-instrumentation-aio-pika==0.45b0",
     },
     {
         "library": "aiohttp ~= 3.0",
-        "instrumentation": "opentelemetry-instrumentation-aiohttp-client==0.43b0",
+        "instrumentation": "opentelemetry-instrumentation-aiohttp-client==0.45b0",
     },
     {
         "library": "aiohttp ~= 3.0",
-        "instrumentation": "opentelemetry-instrumentation-aiohttp-server==0.43b0",
+        "instrumentation": "opentelemetry-instrumentation-aiohttp-server==0.45b0",
     },
     {
         "library": "aiopg >= 0.13.0, < 2.0.0",
-        "instrumentation": "opentelemetry-instrumentation-aiopg==0.43b0",
+        "instrumentation": "opentelemetry-instrumentation-aiopg==0.45b0",
     },
     {
         "library": "asgiref ~= 3.0",
-        "instrumentation": "opentelemetry-instrumentation-asgi==0.43b0",
+        "instrumentation": "opentelemetry-instrumentation-asgi==0.45b0",
     },
     {
         "library": "asyncpg >= 0.12.0",
-        "instrumentation": "opentelemetry-instrumentation-asyncpg==0.43b0",
+        "instrumentation": "opentelemetry-instrumentation-asyncpg==0.45b0",
     },
     {
         "library": "boto~=2.0",
-        "instrumentation": "opentelemetry-instrumentation-boto==0.43b0",
+        "instrumentation": "opentelemetry-instrumentation-boto==0.45b0",
     },
     {
         "library": "boto3 ~= 1.0",
-        "instrumentation": "opentelemetry-instrumentation-boto3sqs==0.43b0",
+        "instrumentation": "opentelemetry-instrumentation-boto3sqs==0.45b0",
     },
     {
         "library": "botocore ~= 1.0",
-        "instrumentation": "opentelemetry-instrumentation-botocore==0.43b0",
+        "instrumentation": "opentelemetry-instrumentation-botocore==0.45b0",
     },
     {
         "library": "cassandra-driver ~= 3.25",
-        "instrumentation": "opentelemetry-instrumentation-cassandra==0.43b0",
+        "instrumentation": "opentelemetry-instrumentation-cassandra==0.45b0",
     },
     {
         "library": "scylla-driver ~= 3.25",
-        "instrumentation": "opentelemetry-instrumentation-cassandra==0.43b0",
+        "instrumentation": "opentelemetry-instrumentation-cassandra==0.45b0",
     },
     {
         "library": "celery >= 4.0, < 6.0",
-        "instrumentation": "opentelemetry-instrumentation-celery==0.43b0",
+        "instrumentation": "opentelemetry-instrumentation-celery==0.45b0",
     },
     {
-        "library": "confluent-kafka >= 1.8.2, <= 2.2.0",
-        "instrumentation": "opentelemetry-instrumentation-confluent-kafka==0.43b0",
+        "library": "confluent-kafka >= 1.8.2, <= 2.3.0",
+        "instrumentation": "opentelemetry-instrumentation-confluent-kafka==0.45b0",
     },
     {
         "library": "django >= 1.10",
-        "instrumentation": "opentelemetry-instrumentation-django==0.43b0",
+        "instrumentation": "opentelemetry-instrumentation-django==0.45b0",
     },
     {
         "library": "elasticsearch >= 2.0",
-        "instrumentation": "opentelemetry-instrumentation-elasticsearch==0.43b0",
+        "instrumentation": "opentelemetry-instrumentation-elasticsearch==0.45b0",
     },
     {
         "library": "falcon >= 1.4.1, < 3.1.2",
-        "instrumentation": "opentelemetry-instrumentation-falcon==0.43b0",
+        "instrumentation": "opentelemetry-instrumentation-falcon==0.45b0",
     },
     {
         "library": "fastapi ~= 0.58",
-        "instrumentation": "opentelemetry-instrumentation-fastapi==0.43b0",
+        "instrumentation": "opentelemetry-instrumentation-fastapi==0.45b0",
     },
     {
-        "library": "flask >= 1.0, < 3.0",
-        "instrumentation": "opentelemetry-instrumentation-flask==0.43b0",
-    },
-    {
-        "library": "werkzeug < 3.0.0",
-        "instrumentation": "opentelemetry-instrumentation-flask==0.43b0",
+        "library": "flask >= 1.0",
+        "instrumentation": "opentelemetry-instrumentation-flask==0.45b0",
     },
     {
         "library": "grpcio ~= 1.27",
-        "instrumentation": "opentelemetry-instrumentation-grpc==0.43b0",
+        "instrumentation": "opentelemetry-instrumentation-grpc==0.45b0",
     },
     {
         "library": "httpx >= 0.18.0",
-        "instrumentation": "opentelemetry-instrumentation-httpx==0.43b0",
+        "instrumentation": "opentelemetry-instrumentation-httpx==0.45b0",
     },
     {
         "library": "jinja2 >= 2.7, < 4.0",
-        "instrumentation": "opentelemetry-instrumentation-jinja2==0.43b0",
+        "instrumentation": "opentelemetry-instrumentation-jinja2==0.45b0",
     },
     {
         "library": "kafka-python >= 2.0",
-        "instrumentation": "opentelemetry-instrumentation-kafka-python==0.43b0",
+        "instrumentation": "opentelemetry-instrumentation-kafka-python==0.45b0",
     },
     {
         "library": "mysql-connector-python ~= 8.0",
-        "instrumentation": "opentelemetry-instrumentation-mysql==0.43b0",
+        "instrumentation": "opentelemetry-instrumentation-mysql==0.45b0",
     },
     {
         "library": "mysqlclient < 3",
-        "instrumentation": "opentelemetry-instrumentation-mysqlclient==0.43b0",
+        "instrumentation": "opentelemetry-instrumentation-mysqlclient==0.45b0",
     },
     {
         "library": "pika >= 0.12.0",
-        "instrumentation": "opentelemetry-instrumentation-pika==0.43b0",
+        "instrumentation": "opentelemetry-instrumentation-pika==0.45b0",
+    },
+    {
+        "library": "psycopg >= 3.1.0",
+        "instrumentation": "opentelemetry-instrumentation-psycopg==0.45b0",
     },
     {
         "library": "psycopg2 >= 2.7.3.1",
-        "instrumentation": "opentelemetry-instrumentation-psycopg2==0.43b0",
+        "instrumentation": "opentelemetry-instrumentation-psycopg2==0.45b0",
     },
     {
         "library": "pymemcache >= 1.3.5, < 5",
-        "instrumentation": "opentelemetry-instrumentation-pymemcache==0.43b0",
+        "instrumentation": "opentelemetry-instrumentation-pymemcache==0.45b0",
     },
     {
         "library": "pymongo >= 3.1, < 5.0",
-        "instrumentation": "opentelemetry-instrumentation-pymongo==0.43b0",
+        "instrumentation": "opentelemetry-instrumentation-pymongo==0.45b0",
     },
     {
         "library": "PyMySQL < 2",
-        "instrumentation": "opentelemetry-instrumentation-pymysql==0.43b0",
+        "instrumentation": "opentelemetry-instrumentation-pymysql==0.45b0",
     },
     {
         "library": "pyramid >= 1.7",
-        "instrumentation": "opentelemetry-instrumentation-pyramid==0.43b0",
+        "instrumentation": "opentelemetry-instrumentation-pyramid==0.45b0",
     },
     {
         "library": "redis >= 2.6",
-        "instrumentation": "opentelemetry-instrumentation-redis==0.43b0",
+        "instrumentation": "opentelemetry-instrumentation-redis==0.45b0",
     },
     {
         "library": "remoulade >= 0.50",
-        "instrumentation": "opentelemetry-instrumentation-remoulade==0.43b0",
+        "instrumentation": "opentelemetry-instrumentation-remoulade==0.45b0",
     },
     {
         "library": "requests ~= 2.0",
-        "instrumentation": "opentelemetry-instrumentation-requests==0.43b0",
+        "instrumentation": "opentelemetry-instrumentation-requests==0.45b0",
     },
     {
         "library": "scikit-learn ~= 0.24.0",
-        "instrumentation": "opentelemetry-instrumentation-sklearn==0.43b0",
+        "instrumentation": "opentelemetry-instrumentation-sklearn==0.45b0",
     },
     {
         "library": "sqlalchemy",
-        "instrumentation": "opentelemetry-instrumentation-sqlalchemy==0.43b0",
+        "instrumentation": "opentelemetry-instrumentation-sqlalchemy==0.45b0",
     },
     {
         "library": "starlette ~= 0.13.0",
-        "instrumentation": "opentelemetry-instrumentation-starlette==0.43b0",
+        "instrumentation": "opentelemetry-instrumentation-starlette==0.45b0",
     },
     {
         "library": "psutil >= 5",
-        "instrumentation": "opentelemetry-instrumentation-system-metrics==0.43b0",
+        "instrumentation": "opentelemetry-instrumentation-system-metrics==0.45b0",
     },
     {
         "library": "tornado >= 5.1.1",
-        "instrumentation": "opentelemetry-instrumentation-tornado==0.43b0",
+        "instrumentation": "opentelemetry-instrumentation-tornado==0.45b0",
     },
     {
         "library": "tortoise-orm >= 0.17.0",
-        "instrumentation": "opentelemetry-instrumentation-tortoiseorm==0.43b0",
+        "instrumentation": "opentelemetry-instrumentation-tortoiseorm==0.45b0",
     },
     {
         "library": "pydantic >= 1.10.2",
-        "instrumentation": "opentelemetry-instrumentation-tortoiseorm==0.43b0",
+        "instrumentation": "opentelemetry-instrumentation-tortoiseorm==0.45b0",
     },
     {
         "library": "urllib3 >= 1.0.0, < 3.0.0",
-        "instrumentation": "opentelemetry-instrumentation-urllib3==0.43b0",
+        "instrumentation": "opentelemetry-instrumentation-urllib3==0.45b0",
     },
 ]
 default_instrumentations = [
-    "opentelemetry-instrumentation-aws-lambda==0.43b0",
-    "opentelemetry-instrumentation-dbapi==0.43b0",
-    "opentelemetry-instrumentation-logging==0.43b0",
-    "opentelemetry-instrumentation-sqlite3==0.43b0",
-    "opentelemetry-instrumentation-urllib==0.43b0",
-    "opentelemetry-instrumentation-wsgi==0.43b0",
+    "opentelemetry-instrumentation-asyncio==0.45b0",
+    "opentelemetry-instrumentation-aws-lambda==0.45b0",
+    "opentelemetry-instrumentation-dbapi==0.45b0",
+    "opentelemetry-instrumentation-logging==0.45b0",
+    "opentelemetry-instrumentation-sqlite3==0.45b0",
+    "opentelemetry-instrumentation-urllib==0.45b0",
+    "opentelemetry-instrumentation-wsgi==0.45b0",
 ]

{opentelemetry_instrumentation-0.43b0 → opentelemetry_instrumentation-0.45b0}/src/opentelemetry/instrumentation/utils.py RENAMED Viewed

@@ -13,16 +13,22 @@
 # limitations under the License.
 import urllib.parse
+from contextlib import contextmanager
 from re import escape, sub
-from typing import Dict, Sequence
+from typing import Dict, Iterable, Sequence
 from wrapt import ObjectProxy
 from opentelemetry import context, trace
-# pylint: disable=unused-import
 # pylint: disable=E0611
-from opentelemetry.context import _SUPPRESS_INSTRUMENTATION_KEY  # noqa: F401
+# FIXME: fix the importing of these private attributes when the location of the _SUPPRESS_HTTP_INSTRUMENTATION_KEY is defined.=
+from opentelemetry.context import (
+    _SUPPRESS_HTTP_INSTRUMENTATION_KEY,
+    _SUPPRESS_INSTRUMENTATION_KEY,
+)
+# pylint: disable=E0611
 from opentelemetry.propagate import extract
 from opentelemetry.trace import StatusCode
 from opentelemetry.trace.propagation.tracecontext import (
@@ -152,3 +158,42 @@ def _python_path_without_directory(python_path, directory, path_separator):
         "",
         python_path,
     )
+def is_instrumentation_enabled() -> bool:
+    if context.get_value(_SUPPRESS_INSTRUMENTATION_KEY):
+        return False
+    return True
+def is_http_instrumentation_enabled() -> bool:
+    return is_instrumentation_enabled() and not context.get_value(
+        _SUPPRESS_HTTP_INSTRUMENTATION_KEY
+    )
+@contextmanager
+def _suppress_instrumentation(*keys: str) -> Iterable[None]:
+    """Suppress instrumentation within the context."""
+    ctx = context.get_current()
+    for key in keys:
+        ctx = context.set_value(key, True, ctx)
+    token = context.attach(ctx)
+    try:
+        yield
+    finally:
+        context.detach(token)
+@contextmanager
+def suppress_instrumentation() -> Iterable[None]:
+    """Suppress instrumentation within the context."""
+    with _suppress_instrumentation(_SUPPRESS_INSTRUMENTATION_KEY):
+        yield
+@contextmanager
+def suppress_http_instrumentation() -> Iterable[None]:
+    """Suppress instrumentation within the context."""
+    with _suppress_instrumentation(_SUPPRESS_HTTP_INSTRUMENTATION_KEY):
+        yield

{opentelemetry_instrumentation-0.43b0 → opentelemetry_instrumentation-0.45b0}/src/opentelemetry/instrumentation/version.py RENAMED Viewed

@@ -12,4 +12,4 @@
 # See the License for the specific language governing permissions and
 # limitations under the License.
-__version__ = "0.43b0"
+__version__ = "0.45b0"