Platform

 View Only

 Azure Consumption Usage Details API only loading 1000 rows

Jump to  Best Answer
  • Datalink
Dawn Kassube's profile image
Dawn Kassube posted Tue January 03, 2023 05:43 PM

The Azure Consumption Usage Details REST API is completing successfully and uploading to the identified table but only 1000 rows are being populated in the table. A nextLink column is being created which appears to provide a Token to access further information. I have searched and cannot find a way to retrieve this data. Please refer to the attached file with screenshots of the Datalink Connector and the uploaded table.


#Datalink
Attachment  View in library
NextLink Datalink Issue.docx 92 KB
Apptio Community Member's profile image
Apptio Community Member posted Tue January 17, 2023 02:10 AM  Best Answer
Hi @Dawn Kassube . I think if Debbie's suggestions don't work, it might be an option to raise a ticket with Microsoft? We had some issues towards the end of last year in Cloudability with missing data and it turned out to be a problem on the Azure side and the API had to be 'refreshed'

Hope you find the root cause soon :-)
Clare​
#Datalink
Debbie Hagen's profile image
Debbie Hagen posted Fri January 06, 2023 06:05 PM
Hello @Dawn Kassube,
Thanks for your question.  I'm looking for someone to help with the answer and we'll follow up next week.  Have a great weekend.

Debbie
​
#Datalink
Debbie Hagen's profile image
Debbie Hagen posted Mon January 16, 2023 01:19 PM
Hi @Dawn Kassube
Maybe give this a try.   A colleague mentioned they've run into a similar issue in the past where an API wasn't pulling back a lot of rows so they added the following to the end of the API URL to pull back more:
&rowCount=1000000000&showRawNumbers=true&rawNumberPrecision=16&omitTotal=true

​
Maybe give that a try and let me know if it works?
Cheers,

Deb

​
#Datalink
Guillermo Cuadrado's profile image
Guillermo Cuadrado posted Tue January 17, 2023 03:52 AM
We had to use the &rowCount parameter in some of our Datalink (Classic) connectors.
@Clare Smit's suggestion to contact MS is also reasonable. We had to do something similar with AWS some years back to tweak the CUR report.​
#Datalink

Related Content