Skip to Main Content
Spotfire Ideas Portal
Status Future Consideration
Product Spotfire
Created by Guest
Created on Sep 19, 2019

Store execution info of the dxps on the action log for statistics (duration, total rows, data table size)

We need to have a centralized place to gather info about the dxps execution on the spotfire environment.

Today there is not a simple way (and is almost impossible) to gather information like time spent for a dxp to open and load completely on client and web player, what is the volume loaded on the dxp, what is the total size of data tables on the dxps loaded on the environment, what is the average size of memory consumed by these dxps.

 

Some of this info we can collect on the monitoring admin ui, but we need to enter on server by server to collect them.

This is not viable on big cluster deployment (like 50 web players).  The info about duration to load a dxp we don't have it in anywhere to do statistics.

 

Also, having these on action logs would be a centralized place to be able to do analysis with this data and have an understanding of how the analysis created by end users are impacting the environment and what dxps are causing the most impact, are more critical to the environment. It is a better way to identify what dxps needs to be revised for better practice development and resource optimization.

 

And it was very surprising to the customer to open a ticket and discover that there is nowhere on the log files with this info.

  • Attach files
  • Guest
    Reply
    |
    Oct 21, 2019

    Hello, Miguel.

     

    I'm using action_log. Actually I would like those info on the action log.

    For example, we pieces of execution of a dxp on the action log (download from library, load dxp, load ILs...), but we don't have a track of the executions so we could link one to another.

     

    Also, for some entries, like execution ILs, the time stored on the action log is the time for reading the metadata of the action log from the spotfire database, and not the time spent to load all the data from the ILs database, which is what is desired to measure the performance of the dxps on the environment.

     

    So, none of the info we need are on the action logs. 

  • Admin
    Miguel Díez
    Reply
    |
    Oct 14, 2019

    Hi Giuseppe,

    Are you already using action_log ? bit.ly/spot-action-log

    That may provide you some of the information you are looking for.

    Of course, we can always include more information.