Unlocking insights: Introducing Step Metrics for Bitbucket Pipelines
We’re excited to announce step metrics – a new capability coming to Bitbucket Pipelines to help you better manage and optimise your CI/CD workflows.
Ever wondered what’s happening under the hood during your pipeline runs? Step metrics provide a window into the resource usage of your build and service containers.
More specifically, step metrics let you monitor CPU and memory usage for each build and service container in your pipeline steps. You can view detailed graphs, filter by service, and get precise data – all to help you optimize the performance of your pipelines.
By tracking CPU and memory consumption, you can:
- Spot bottlenecks before they impact your builds
- Optimize resource allocation for faster, more reliable pipelines
- Troubleshoot issues with data-driven confidence
How to access Step Metrics
- Navigate to the Metrics tab:
For each step in your pipeline, you’ll find a dedicated Metrics tab. This is your dashboard for ‘all things’ resource usage. - Customize your view:
Want to focus on a specific service? Use the checkboxes below each graph to show or hide metrics for individual services. This makes it easy to zero in on what matters most to you. - Get granular data:
Hover over any service in the graph to see the exact timestamp and metric values. This level of detail helps you pinpoint when and where spikes or drops occur and on which command.
Limitations & important info
- 14-day retention:
Metrics are stored for 14 days after a step completes. After that, they’re deleted—so be sure to review or export data if you need it for longer-term analysis. - Post step availability:
Metrics become available only after the step has finished running. You won’t see real-time data during execution. - Sampling frequency:
Data points are collected every 5 seconds, giving you a detailed view without overwhelming you with noise.
Pro tips for getting the most out of step metrics
- Regularly review your metrics to catch trends early.
- Compare resource usage across different builds to identify regressions or improvements.
- Share insights with your team to foster a culture of continuous improvement.
Developer docs
More details can be found in the documentation page.
Feedback
We’re always keen to hear your thoughts and feedback – if you have any questions or suggestions on this feature, feel free to share via the Pipelines Community Space.