Hey, thank you for your request.

At this point, Harness doesn’t provide built-in resource profiling directly in the pipeline studio. However, you can achieve resource usage monitoring today by adopting a pattern similar to what we outline here: https://developer.harness.io/kb/continuous-integration/articles/parallel-step-for-logging/

The idea is to add lightweight monitoring steps in parallel to your build/test steps that capture CPU, memory, disk, or any other metrics that are relevant for your workload. For example, you can add:

*A 'top' command to sample CPU/memory usage.

* Custom shell commands or agent scripts to collect any specific metrics you care about.

By running these monitors in parallel, you can gather real resource usage during real workloads without impacting execution. Over time, you’ll build a baseline dataset that can guide your resource allocation decisions — helping you optimize resource requests, node sizing, and concurrency.

This gives you flexibility to collect the exact metrics you need for your environment, workload types, and optimization goals.

Would that approach work for you?

Regards,

Nofar Bluestein

CI product team