o
    Áżi  ă                   @   s   d Z dS )a  Instrument kombu to report AMQP messaging.

ref:`import ddtrace.auto<ddtraceauto>` and `ddtrace-run` will not automatically patch your Kombu client to
make it work, as this would conflict with the
Celery integration. You must specifically request kombu be patched, as in the example below.

Note: To permit distributed tracing for the kombu integration you must enable the tracer with priority
sampling. Refer to the documentation here:
https://ddtrace.readthedocs.io/en/stable/advanced_usage.html#priority-sampling

Without enabling distributed tracing, spans within a trace generated by the kombu integration might be dropped
without the whole trace being dropped.

Run with `DD_PATCH_MODULES=kombu:true`::

    import ddtrace.auto
    import kombu

    # If not patched yet, you can patch kombu specifically
    patch(kombu=True)

    # This will report a span with the default settings
    conn = kombu.Connection("amqp://guest:guest@127.0.0.1:5672//")
    conn.connect()
    task_queue = kombu.Queue('tasks', kombu.Exchange('tasks'), routing_key='tasks')
    to_publish = {'hello': 'world'}
    producer = conn.Producer()
    producer.publish(to_publish,
                     exchange=task_queue.exchange,
                     routing_key=task_queue.routing_key,
                     declare=[task_queue])

Configuration
~~~~~~~~~~~~~

.. py:data:: ddtrace.config.kombu["service"]

   The service name reported by default for kombu spans.

   This option can also be set with the ``DD_KOMBU_SERVICE`` environment
   variable.

   Default: ``"kombu"``
N)Ú__doc__Š r   r   ú[/home/ubuntu/.local/lib/python3.10/site-packages/ddtrace/contrib/internal/kombu/__init__.pyÚ<module>   s    