Add OpenTelemetry tracing to on_message

 - extract trace context from the AMQP message headers and wrap the handler call in a consumer span, no-op without a configured OpenTelemetry backend
 - new dependency opentelemetry-api, span attributes follow the messaging semantic conventions
 - packaging modernized to pyproject.toml + uv, Debian packaging removed, Python floor now 3.9, pika constrained to >=1.3.2,<1.4

Author: Patrick van der Wal

.gitignore

@@ -35,3 +35,6 @@ nosetests.xml
 .project
 .pydevproject
 .idea
+
+# uv
+.venv/

CHANGELOG.md

@@ -1,6 +1,32 @@
-<h1>Changelog</h1>
-<h2>1.7.1</h2>
-Remove the `stop_ioloop_on_close` argument since this is no longer in `pika>=1.0.0`.
-Since removing this argument will change behaviour on version still using `pika<1.0.0`
-make sure we require at least `pika>1.0.0` in setup.py so people installing this new
-version will not have changed behaviour.
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [1.8.0] - 2026-07-30
+
+### Added
+- OpenTelemetry tracing support: `on_message` extracts trace context from the AMQP message headers and wraps the handler call in a consumer span, so handling continues the publisher's trace (see the eventsender 1.3.0 counterpart). Messages without trace headers start a trace of their own
+- `opentelemetry-api` dependency. Without a configured OpenTelemetry backend all tracing calls are no-ops and behaviour is unchanged
+- First test suite, run with `uv run pytest tests`
+- `pyproject.toml` with uv support, replacing the legacy packaging files
+- Tracing and test-running sections to the README
+
+### Changed
+- pika constraint from `>=1.0.0` to `>=1.3.2,<1.4`
+- Minimum Python version is now 3.9, enforced via `requires-python` so installs on older interpreters keep resolving 1.7.4
+- README usage example to Python 3 syntax
+
+### Removed
+- `setup.py`, `setup.cfg` and `MANIFEST.in`, replaced by `pyproject.toml`
+- Obsolete Python 2 Debian packaging (nothing builds or consumes it anymore)
+
+## [1.7.1] - 2021-04-22
+
+### Removed
+- The `stop_ioloop_on_close` argument since this is no longer in `pika>=1.0.0`
+
+### Changed
+- Require at least `pika>=1.0.0` in setup.py, since removing the `stop_ioloop_on_close` argument would change behaviour on versions still using `pika<1.0.0`

MANIFEST.in

@@ -17,7 +17,7 @@ Example:
 
 
     def handler(event):
-        print "Got event:", event
+        print("Got event:", event)
 
 
     def main():
@@ -35,6 +35,22 @@ Example:
         main()
 
 
+Tracing
+-------
+For every consumed message the consumer extracts OpenTelemetry trace context from the
+AMQP message headers and wraps the handler call in a consumer span, continuing the
+publisher's trace when the message carries one (messages without trace headers simply
+start a trace of their own). This only depends on ``opentelemetry-api``, for applications
+without a configured OpenTelemetry backend all tracing calls are no-ops and the behaviour
+is unchanged. To get the spans into your tracing backend, configure an OpenTelemetry SDK
+in your application (for example by enabling the Sentry SDK's OpenTelemetry support).
+
+
+Running tests
+-------------
+Install `uv <https://docs.astral.sh/uv/>`_ and run ``uv run pytest tests``.
+
+
 =====
 About
 =====
@@ -44,5 +60,3 @@ fast and secure Magento hosting and scalable cluster hosting.
 Check out our `Github page <https://github.com/ByteInternet>`_ for more open source software or `our site <https://www.byte.nl>`_
 to learn about our products and technologies. Look interesting? Reach out about joining `the team <https://www.byte.nl/vacatures>`_.
 Or just drop by for a cup of excellent coffee if you're in town!
-
-[![Scrutinizer Code Quality](https://scrutinizer-ci.com/g/ByteInternet/python-events/badges/quality-score.png?b=master)](https://scrutinizer-ci.com/g/ByteInternet/python-events/?branch=master)

README.rst

@@ -2,8 +2,12 @@
 import pika
 import json
 
+from opentelemetry import propagate, trace
+
 logger = logging.getLogger(__name__)
 
+tracer = trace.get_tracer('amqpconsumer')
+
 
 class EventConsumer(object):
     """Basic consumer with event loop for RabbitMQ events.
@@ -297,7 +301,21 @@ def on_message(self, _, basic_deliver, properties, body):
         except ValueError:
             logger.warning('Discarding message containing invalid json: %s', body)
         else:
-            self._handler(decoded)
+            event_type = decoded.get('type') if isinstance(decoded, dict) else None
+            context = propagate.extract(properties.headers or {})
+            with tracer.start_as_current_span(
+                    'process {}'.format(event_type or self._queue),
+                    kind=trace.SpanKind.CONSUMER,
+                    context=context) as span:
+                span.set_attribute('messaging.system', 'rabbitmq')
+                span.set_attribute('messaging.operation.name', 'process')
+                span.set_attribute('messaging.operation.type', 'process')
+                span.set_attribute('messaging.destination.name', self._queue)
+                if basic_deliver.routing_key:
+                    span.set_attribute('messaging.rabbitmq.destination.routing_key', basic_deliver.routing_key)
+                if event_type:
+                    span.set_attribute('event.type', str(event_type))
+                self._handler(decoded)
 
         self.acknowledge_message(basic_deliver.delivery_tag)