My project and I are absolutely thrilled with preliminary results and functionality of the Continuous Analytics feature. With a server that took 26+ hours to get data to load initially, we are seeing data visibility in reports and visualizations with a 20-30 minute turnaround time. We didn’t even think the server was going to be able to handle running analytics at all, much less such a speedy turnaround.
Is there a way to see the actual time the Continuous Analytics starts/finishes? I’m used to seeing statistics in system/tasks, however can’t seem to sort information from this view to see it run. Thanks for any assistance!
This is great, many thanks for the feedback and the kind words!
We haven’t added this to the About page yet, but if you are inclined to look at JSON you can use this endpoint:
/api/system/info
And look for the the following properties:
lastAnalyticsTablePartitionSuccess
intervalSinceLastAnalyticsTablePartitionSuccess
lastAnalyticsTablePartitionRuntime
Now you should be able to get task/job information from the tasks/task summaries endpoints. Notice that there is a dedicated job type for continuous analytics with key:
continuousAnalyticsTableJob
We are looking for insights on how this relatively new feature is used so feedback is appreciated!
Appreciate the response. With our Test server this is showing ,“intervalSinceLastAnalyticsTablePartitionSuccess”:“52 s”,“lastAnalyticsTablePartitionRuntime”:“12 s”
, which is pretty incredible considering our Production server (larger by a substantial degree) takes about 40 minutes to run through analytics at the moment.