Skip to Main Content
Spotfire Ideas Portal
Status Implemented
Product Spotfire
Created by Guest
Created on May 11, 2016

Provide Spotfire Library usage logging (was better in v3.1 and earlier)

Many I would like to track the usage of analyses (and other items) in the Spotfire library. Examples of things I would like to analyse:
* Number of I accessing a certain dxp-file
* What I are using a certain file and how often
* General statistics of usage of analyses (create top lists, e.g. for identifying candidate analyses that should be kept pre-loaded by Scheduled Updates, or for identifying reports that are not used at all).

You can think of many things, with regards to library usage, that could be interesting to visualize in TIBCO Spotfire. Should be enough if we logged every time an analysis is opened in any client (including item GUID, username, etc). The library.log file almost provides this kind of information. In v3.2 of the library.log you get an entry "Content loaded" every time a file is opened in a thick client, but in the Web Player you only get it for the first user. Then, if the file is cached you only get a "Metadata loaded" entry for the second user. The problem is that you get tons of "Metadata loaded"-entries for other events too. Example: login to the Web Player and you get one "Metadata loaded"-entry for every file that is displayed on the library start page (My recent files, modified files, and all files in the folders you expand in the library). So, right now, the library.log can't be used for counting how many times a certain file has been opened (and by whom). Furthermore, the statistics logging that was included in Web Player v3.2 is not really suitable for this kind of analysis either, and it does only cover the Web Player. Notice that the library.log file was more useful for this kind of analysis in v3.1 and earlier. In 3.1, two types of entries related to opening DXP files from the library were written to library.log: "[Load item]" and "[Load content]". Using some clever logic, those entries could be used to analyse what files had been opened by whom (in the Web Player or the thick clients). Information about how to do so has been shared with many I.
Implemented in 5.5
  • Attach files