5.19.1 — 2026-10-21¶

Tests¶

Elastic APM Server Scenarios - Added scenarios that send telemetry to a real Elastic APM Server and check what Elasticsearch stored.
- Scenario Outlines with a route column run every case twice: the application exports to APM Server directly, and through a collector that forwards to it
- Covered adapters: Redis, Kafka, Elasticsearch, MinIO, SQLAlchemy (PostgreSQL, MySQL, StarRocks, SQLite), ScyllaDB, Vault, Keycloak, httpx2 and Temporal
- Temporal activities are asserted as messaging transactions, Redis and SQLAlchemy calls as db spans, Kafka as messaging
- Temporal SDK metrics, decorator metrics (count_calls, measure_duration), gRPC and FastAPI server metrics and log records correlated with their trace id are checked in Elasticsearch

Elastic APM Test Containers - Added an Elastic APM Server test container with its own Elasticsearch, and a collector container that forwards to it.
- Standalone APM Server runs without Kibana
- Elasticsearch and APM Server test images are 9.5.5
Shared Telemetry Containers - scripts/behave_parallel.py starts the collector and the Elastic APM stack once and shares them with every feature process through ARCHIPY_SHARED_TELEMETRY.
- Each scenario exports under its own service.name, so scenarios sharing the containers do not see each other
- Only the parts the selected features ask for through their tags are started
Elasticsearch Test Container Restart - The Elasticsearch test container builds a fresh container when it is started again after a stop, so features can run back to back in one process.
Image Pre-Pull - Added make pull-test-images, which pulls every image listed in .env.test, four at a time.