Forum Discussion

RussGriff's avatar
RussGriff
Frequent Visitor
4 years ago

Gateway logs - refreshid not the same as refreshid in API

I am pulling refresh history from our service using the API. I was expecting that the refresh ids from my api extract should match up with the refreshid shown in the gateway logs- QueryStart and QueryExecution but there is no correlation. The refresh id in the logs is maybe at a different level. Has anyone got any suggestions or explanation of why I can't link these up ? Thanks

Need Help

3 Replies

  • GilbertQ's avatar
    GilbertQ
    Super User
    4 years ago

    Hi RussGriff 

     

    When you say you are pulling the "Service using the API" what are you using to get those details?

     

    And it could possibly be different because you are getting data from different area's in the Power BI Service so each GUID (Refresh ID) will be different?

    • RussGriff's avatar
      RussGriff
      Frequent Visitor
      4 years ago

      Actually I meant RequestId (rather than refreshid).

      I am getting the Refresh History for each dataset using the REST API - passing the datasetid to get the last X refreshes. This gives me the requestid (GUID) and there is one row for a refresh of the entire dataset.

      The Power BI logs (on the gateway machine) also have a requestid - and in the case of 1 dataset only I get a match on requestid - maybe they are a different requestid (perhaps the requestid in the power bi logs are for the individual tables within the dataset) .

      • pbi_champ's avatar
        pbi_champ
        Frequent Visitor
        1 year ago

        Hi RussGriff  were you able to solve this? I'm seeing the same behavior. The RequestId show in the Refresh History in Power BI Service does not seem to match the RequestId in the Gateway logs.  The semantic model in question is refreshed via API, as opposed to scheduled refresh via dataset settings or on demand.  Could that a reason why the RequestId is different?