1 Reply Latest reply on Jul 20, 2016 11:11 AM by Matt Coles

    How to Track the list of Live connection based Workbooks and their Rendering times over a period of time

    Dinesh Prabu Viswanathan

      Hi Everyone,

       

      Good Morning.

      I have the below requirement.

      1. Dashboard to track the list of Live connection based reports - Site wise and their history information as well.

      I am not sure if this information is available in the PostgreSQL repository.
      Any help on this is much appreciated.

      On a yearly basis, we would like to see usage of live connection based reports and find out who is using Live connections actively.

      We would like to maintain the history information as well.

       

      Month/Year
      Site NameReport NameType of ConnectionsWorkbook/Data SourceOwner Name
      Jan 2016XXXXXXXXXXData Sourceabcde
      Jan 2016
      Feb 2016
      Feb 2016
      Mar 2016
      Mar 2016
        • 1. Re: How to Track the list of Live connection based Workbooks and their Rendering times over a period of time
          Matt Coles

          Yes, the PostgreSQL repository does contain the information. The data_connections table holds information on all the actual connections to data, and defines whether they're extracted or live. The fields owner_type and owner_id are "Workbook" or "Datasource" and the ID of said workbook or datasource from the workbooks or datasources table, respectively. So that will provide you the basic information you need for what content uses live vs extracted connections.

           

          The historical_events table, and the hist_* tables that can be joined to it, describe who has done what, with what content, when. It does not, unfortunately, contain any performance data. But it will give you what you need in terms of how actively each piece of content is being used. Performance information can really only be extracted from the http_requests table, and can be a bit flaky.

           

          You will likely want to export this data incrementally to some other database system, as http_requests is trimmed at 7 days by default, and historical_events at 180 days.