Summary

Enhance Bitbucket Pipelines OpenTelemetry webhooks to support real-time pipeline monitoring and stronger execution context.

Customer impact

OTel traces are currently emitted only after a pipeline completes. For long-running pipelines, this can exceed observability-platform ingestion windows and prevents timely visibility into pipeline progress, failures, and retries.

Requested capabilities

• Pipeline and step lifecycle events while a run is in progress
• Human-readable step names
• Commit SHA, author, and branch/tag context
• Retry attempt and parent-run correlation
• Clear execution and event-emission timestamps

Current workaround

Customers must poll the Pipelines REST API for in-progress status, which requires additional implementation and does not provide equivalent push-based telemetry.