ddtrace 3.11.0rc1__cp312-cp312-win_amd64.whl → 3.11.0rc3__cp312-cp312-win_amd64.whl

ddtrace/contrib/_avro.py

@@ -1,17 +0,0 @@
-"""
-The Avro integration will trace all Avro read / write calls made with the ``avro``
-library. This integration is enabled by default.
-
-Enabling
-~~~~~~~~
-
-The avro integration is enabled by default. Use
-:func:`patch()<ddtrace.patch>` to enable the integration::
-
-    from ddtrace import patch
-    patch(avro=True)
-
-Configuration
-~~~~~~~~~~~~~
-
-"""

ddtrace/contrib/_botocore.py

@@ -1,153 +0,0 @@
-"""
-The Botocore integration will trace all AWS calls made with the botocore
-library. Libraries like Boto3 that use Botocore will also be patched.
-
-Enabling
-~~~~~~~~
-
-The botocore integration is enabled automatically when using
-:ref:`ddtrace-run<ddtracerun>` or :ref:`import ddtrace.auto<ddtraceauto>`.
-
-Or use :func:`patch()<ddtrace.patch>` to manually enable the integration::
-
-    from ddtrace import patch
-    patch(botocore=True)
-
-To patch only specific botocore modules, pass a list of the module names instead::
-
-    from ddtrace import patch
-    patch(botocore=['s3', 'sns'])
-
-Configuration
-~~~~~~~~~~~~~
-
-.. py:data:: ddtrace.config.botocore['distributed_tracing']
-
-   Whether to inject distributed tracing data to requests in SQS, SNS, EventBridge, Kinesis Streams and Lambda.
-
-   Can also be enabled with the ``DD_BOTOCORE_DISTRIBUTED_TRACING`` environment variable.
-
-    Example::
-
-        from ddtrace import config
-
-        # Enable distributed tracing
-        config.botocore['distributed_tracing'] = True
-
-
-   Default: ``True``
-
-
-.. py:data:: ddtrace.config.botocore['invoke_with_legacy_context']
-
-    This preserves legacy behavior when tracing directly invoked Python and Node Lambda
-    functions instrumented with datadog-lambda-python < v41 or datadog-lambda-js < v3.58.0.
-
-    Legacy support for older libraries is available with
-    ``ddtrace.config.botocore.invoke_with_legacy_context = True`` or by setting the environment
-    variable ``DD_BOTOCORE_INVOKE_WITH_LEGACY_CONTEXT=true``.
-
-
-    Default: ``False``
-
-
-.. py:data:: ddtrace.config.botocore['operations'][<operation>].error_statuses = "<error statuses>"
-
-    Definition of which HTTP status codes to consider for making a span as an error span.
-
-    By default response status codes of ``'500-599'`` are considered as errors for all endpoints.
-
-    Example marking 404, and 5xx as errors for ``s3.headobject`` API calls::
-
-        from ddtrace import config
-
-        config.botocore['operations']['s3.headobject'].error_statuses = '404,500-599'
-
-
-    See :ref:`HTTP - Custom Error Codes<http-custom-error>` documentation for more examples.
-
-.. py:data:: ddtrace.config.botocore['tag_no_params']
-
-    This opts out of the default behavior of collecting a narrow set of API parameters as span tags.
-
-    To not collect any API parameters, ``ddtrace.config.botocore.tag_no_params = True`` or by setting the environment
-    variable ``DD_AWS_TAG_NO_PARAMS=true``.
-
-
-    Default: ``False``
-
-
-.. py:data:: ddtrace.config.botocore['instrument_internals']
-
-    This opts into collecting spans for some internal functions, including ``parsers.ResponseParser.parse``.
-
-    Can also be enabled with the ``DD_BOTOCORE_INSTRUMENT_INTERNALS`` environment variable.
-
-    Default: ``False``
-
-
-.. py:data:: ddtrace.config.botocore['span_prompt_completion_sample_rate']
-
-   Configure the sample rate for the collection of bedrock prompts and completions as span tags.
-
-   Alternatively, you can set this option with the ``DD_BEDROCK_SPAN_PROMPT_COMPLETION_SAMPLE_RATE`` environment
-   variable.
-
-   Default: ``1.0``
-
-
-.. py:data:: (beta) ddtrace.config.botocore["span_char_limit"]
-
-   Configure the maximum number of characters for bedrock span tags for prompt/response text.
-
-   Text exceeding the maximum number of characters is truncated to the character limit
-   and has ``...`` appended to the end.
-
-   Alternatively, you can set this option with the ``DD_BEDROCK_SPAN_CHAR_LIMIT`` environment
-   variable.
-
-   Default: ``128``
-
-
-.. py:data:: ddtrace.config.botocore['dynamodb_primary_key_names_for_tables']
-
-    This enables DynamoDB API calls to be instrumented with span pointers. Many
-    DynamoDB API calls do not include the Item's Primary Key fields as separate
-    values, so they need to be provided to the tracer separately. This field
-    should be structured as a ``dict`` keyed by the table names as ``str``.
-    Each value should be the ``set`` of primary key field names (as ``str``)
-    for the associated table. The set may have exactly one or two elements,
-    depending on the Table's Primary Key schema.
-
-    In python this would look like::
-
-        ddtrace.config.botocore['dynamodb_primary_key_names_for_tables'] = {
-            'table_name': {'key1', 'key2'},
-            'other_table': {'other_key'},
-        }
-
-    Can also be enabled with the ``DD_BOTOCORE_DYNAMODB_TABLE_PRIMARY_KEYS``
-    environment variable which is parsed as a JSON object with strings for keys
-    and lists of strings for values.
-
-    This would look something like::
-
-        export DD_BOTOCORE_DYNAMODB_TABLE_PRIMARY_KEYS='{
-            "table_name": ["key1", "key2"],
-            "other_table": ["other_key"]
-        }'
-
-    Default: ``{}``
-
-
-.. py:data:: ddtrace.config.botocore['add_span_pointers']
-
-    This enables the addition of span pointers to spans associated with
-    successful AWS API calls.
-
-    Alternatively, you can set this option with the
-    ``DD_BOTOCORE_ADD_SPAN_POINTERS`` environment variable.
-
-    Default: ``True``
-
-"""

ddtrace/contrib/_protobuf.py

@@ -1,17 +0,0 @@
-"""
-The Protobuf integration will trace all Protobuf read / write calls made with the ``google.protobuf``
-library. This integration is enabled by default.
-
-Enabling
-~~~~~~~~
-
-The protobuf integration is enabled by default. Use
-:func:`patch()<ddtrace.patch>` to enable the integration::
-
-    from ddtrace import patch
-    patch(protobuf=True)
-
-Configuration
-~~~~~~~~~~~~~
-
-"""

ddtrace/contrib/_pytest.py

@@ -1,62 +0,0 @@
-"""
-The pytest integration traces test executions.
-
-Enabling
-~~~~~~~~
-
-Enable traced execution of tests using ``pytest`` runner by
-running ``pytest --ddtrace`` or by modifying any configuration
-file read by pytest (``pytest.ini``, ``setup.cfg``, ...)::
-
-    [pytest]
-    ddtrace = 1
-
-
-If you need to disable it, the option ``--no-ddtrace`` will take
-precedence over ``--ddtrace`` and (``pytest.ini``, ``setup.cfg``, ...)
-
-You can enable all integrations by using the ``--ddtrace-patch-all`` option
-alongside ``--ddtrace`` or by adding this to your configuration::
-
-    [pytest]
-    ddtrace = 1
-    ddtrace-patch-all = 1
-
-
-.. note::
-   The ddtrace plugin for pytest has the side effect of importing the ddtrace
-   package and starting a global tracer.
-
-   If this is causing issues for your pytest runs where traced execution of
-   tests is not enabled, you can deactivate the plugin::
-
-     [pytest]
-     addopts = -p no:ddtrace
-
-   See the `pytest documentation
-   <https://docs.pytest.org/en/7.1.x/how-to/plugins.html#deactivating-unregistering-a-plugin-by-name>`_
-   for more details.
-
-
-Global Configuration
-~~~~~~~~~~~~~~~~~~~~
-
-.. py:data:: ddtrace.config.pytest["service"]
-
-   The service name reported by default for pytest traces.
-
-   This option can also be set with the integration specific ``DD_PYTEST_SERVICE`` environment
-   variable, or more generally with the `DD_SERVICE` environment variable.
-
-   Default: Name of the repository being tested, otherwise ``"pytest"`` if the repository name cannot be found.
-
-
-.. py:data:: ddtrace.config.pytest["operation_name"]
-
-   The operation name reported by default for pytest traces.
-
-   This option can also be set with the ``DD_PYTEST_OPERATION_NAME`` environment
-   variable.
-
-   Default: ``"pytest.test"``
-"""

ddtrace/contrib/_pytest_bdd.py

@@ -1,23 +0,0 @@
-"""
-The pytest-bdd integration traces executions of scenarios and steps.
-
-Enabling
-~~~~~~~~
-
-Please follow the instructions for enabling `pytest` integration.
-
-.. note::
-   The ddtrace.pytest_bdd plugin for pytest-bdd has the side effect of importing
-   the ddtrace package and starting a global tracer.
-
-   If this is causing issues for your pytest-bdd runs where traced execution of
-   tests is not enabled, you can deactivate the plugin::
-
-     [pytest]
-     addopts = -p no:ddtrace.pytest_bdd
-
-   See the `pytest documentation
-   <https://docs.pytest.org/en/7.1.x/how-to/plugins.html#deactivating-unregistering-a-plugin-by-name>`_
-   for more details.
-
-"""

ddtrace/contrib/_pytest_benchmark.py

@@ -1,3 +0,0 @@
-"""
-The pytest-benchmark integration traces executions of pytest benchmarks.
-"""

ddtrace/contrib/_unittest.py

@@ -1,36 +0,0 @@
-"""
-The unittest integration traces test executions.
-
-
-Enabling
-~~~~~~~~
-
-The unittest integration is enabled automatically when using
-:ref:`ddtrace-run<ddtracerun>` or :ref:`import ddtrace.auto<ddtraceauto>`.
-
-Alternately, use :func:`patch()<ddtrace.patch>` to manually enable the integration::
-
-    from ddtrace import patch
-    patch(unittest=True)
-
-Global Configuration
-~~~~~~~~~~~~~~~~~~~~
-
-.. py:data:: ddtrace.config.unittest["operation_name"]
-
-   The operation name reported by default for unittest traces.
-
-   This option can also be set with the ``DD_UNITTEST_OPERATION_NAME`` environment
-   variable.
-
-   Default: ``"unittest.test"``
-
-.. py:data:: ddtrace.config.unittest["strict_naming"]
-
-   Requires all ``unittest`` tests to start with ``test`` as stated in the Python documentation
-
-   This option can also be set with the ``DD_CIVISIBILITY_UNITTEST_STRICT_NAMING`` environment
-   variable.
-
-   Default: ``True``
-"""