Post by Marcelino Soares

If observability behavior lives in YAML, it belongs in your test strategy. A quiet but important shift landed in OpenTelemetry’s Spring Boot starter this week: version 2.26.0 can define the SDK’s telemetry pipeline directly in application.yaml. That changes the quality conversation. Sampling rules, exporter endpoints, resource attributes, and path exclusions are no longer only runtime wiring hidden in Java configuration. They can now be reviewed, versioned, and tested alongside application configuration. The practical takeaway: add a small configuration contract test to your Spring Boot service. Start it with the intended profile and assert the telemetry behavior that matters: the service identity, the exporter target, and critical exclusions such as health endpoints. Also test the production override path—an environment variable or profile must not silently undo your expected configuration. This is less about testing OpenTelemetry and more about testing a production behavior your reliability decisions depend on. The feature is experimental, which makes early, focused feedback especially valuable. Source: https://lnkd.in/ekBfPbRR Which operational configurations does your team treat as testable contracts? #SoftwareQuality #ReliabilityEngineering #Observability #OpenTelemetry #Testing