is scheduled report task a full analysis ?
i have created a scheduled task to generate a report for every 24 hrs with UEM user action data for my application. The report is getting generated as expected but when I compare a 24hrs report and its contents with 2 half day reports, the count of user actions is different, anyone had similar situation ?
is the report that was generated on dynatarce server a "FULL ANALYSIS" ? since when i generate the same report on my client it pop up's to select full analysis and takes additional time. is this might be reason for getting lesser count on bigger duration report using scheduled task ?
Which measure are you using for counting the user actions? There are different built-in BT result measures for this purpose and they can produce different results when used inconsistently.
If it's a custom BT result measure, what is your filter measure?
If you're filtering by visits perhaps one (hypothetical) reason could be that some user actions are counted twice (once in each half-day report) due to their visit "spanning" both half day time frames.
Im counting the total no of "COUNT" from 2 half day reports and trying to match with whole day count.
I agree if we # of rows for user actions, some occurred during AM and some PM, both of them appear by same name in whole day report but the "COUNT" should be matching.
PS:- What is "BT" abbrevation :)
BT = Business Transaction
"Count" can be an aggregation type or a the name of a default BT result measure (if it was enabled).
For example there is a built-in BT "Real User Actions" which calculates the result measures "Count", "User Action Count", "User Action Duration" etc. It might be helpful to know whether or not you are using any of these in your report. Depending on how your report is created you may have to look at the series used in your chart dashlet.
Perhaps another reason for the mismatch could be that at the time where your scheduled report is triggered there are still User Action Purepaths "underway" which are not yet completely analyzed, e.g. due to some non-zero delay in the realtime path analyzer processing they might not appear in your report even though they would fall into the dashboard/report timeframe. But again this is just a guess....
