The Pool consumption report on ADO only gives hourly analysis for last 1 day. In order to build historical view for more than 1 day, I am trying to access the data via odata v4.0-preview API for TaskAgentRequestSnapshots endpoint.
In order to achieve above requirement, I am able to fetch data however when I am trying to filter on specific date and hour, its not matching to what I see on the ADO report for the last 1 day analysis.
In the below screenshots I am comparing the ADO report hourly view for last 1 day with ODATA feed with applied filters for same view. E.g. for March 8th 2025 12:00AM, the report shows 5 running jobs but the odata feed with filters applied in spreadsheet gives 11 running jobs.
I have tried similar comparison for Azure DevOps managed agent pools as well and it doesn't line up either. Does anyone know what filter or logic is applied to calculate it?
The Pool consumption report on ADO only gives hourly analysis for last 1 day. In order to build historical view for more than 1 day, I am trying to access the data via odata v4.0-preview API for TaskAgentRequestSnapshots endpoint.
In order to achieve above requirement, I am able to fetch data however when I am trying to filter on specific date and hour, its not matching to what I see on the ADO report for the last 1 day analysis.
In the below screenshots I am comparing the ADO report hourly view for last 1 day with ODATA feed with applied filters for same view. E.g. for March 8th 2025 12:00AM, the report shows 5 running jobs but the odata feed with filters applied in spreadsheet gives 11 running jobs.
I have tried similar comparison for Azure DevOps managed agent pools as well and it doesn't line up either. Does anyone know what filter or logic is applied to calculate it?
Share Improve this question asked Mar 9 at 14:51 ankur kapoorankur kapoor 816 bronze badges1 Answer
Reset to default 0Based on the screenshot you provided, it seems that there is some duplicate data.
According to Pool consumption report,
Pool data is aggregated at a granularity of 10 minutes, and the number of running jobs is plotted based on the maximum number of running jobs for the specified interval of time.
Please make sure that the scope you query on the UI is consistent with the scope of the odata query. That means that if you check pool consumption report at anization level (From Organization Settings ->Agent pools ->Azure Pipelines), then you should not include project in your odata query path.