We’re currently hitting the /resourceTables/analytics endpoint regularly from a cron script to keep our reports up to date. On our current DHIS2 instance this takes around 2 minutes to complete. However, we’re soon planning on migrating to another instance with a LOT more datasets/dataelements e.t.c. where the analytics job takes around 2 hours to run, hence is only done once overnight.
We’d still like to be able to keep the reports which rely on only our dataset/dataelements up to date regularly though. Is there a way of triggering the analytics to run only for a specific dataset and it’s related dataelements?
unfortunately - no there is no way to trigger analytics for specific data sets currently.
By default, the analytics process will generate resource tables, table for aggregate data values, tables for events. By setting “skipEvents=false” in the query, the analytics process will skip the generation of events tables.
We’re currently hitting the /resourceTables/analytics endpoint regularly from a cron script to keep our reports up to date. On our current DHIS2 instance this takes around 2 minutes to complete. However, we’re soon planning on migrating to another instance with a LOT more datasets/dataelements e.t.c. where the analytics job takes around 2 hours to run, hence is only done once overnight.
We’d still like to be able to keep the reports which rely on only our dataset/dataelements up to date regularly though. Is there a way of triggering the analytics to run only for a specific dataset and it’s related dataelements?