You may be trying to query data from the rtr_external_rules_mto table from the STV component using a set of parameters involving dates, rule_id, SRISM statistics etc. You find that when you compare the results of the query with the results obtained by using the same parameters on the MGR GUI, the results obtained are different.
This issue occurs because the MGR GUI converts results to the local time of whatever region you are in, whereas the while the query running on the tables in the stv_statistics DB of the STV Component extracts results in GMT+00. In order to solve the issue, you will have to modify the timestamp parameters (ts column) in a way that the query results are also reported in your local time.
If you are in a timezone which is ahead of GMT (e.g. GMT + X), you will need to constrain the time by subtracting the X from your desired day/date range. Conversely, if you are in a timezone which is behind GMT (GMT - Y), you will have to add Y to your desired day/date range. Please see below for a table of worked examples on how you should modify the query,
|Your Local Timezone||Day/Date range in your local timezone||Parameter to use in Query|
|Central Standard Time (CST: GMT-6:00)||2021-11-19||
start - 2021-11-19 06:00:00
|Central Standard Time (CST: GMT-6:00)||2021-11-16 to 2021-11-19||start - 2021-11-16 06:00:00
end - 2021-11-20 05:59:59
|Jakarta (WIB: GMT+7:00)||2021-11-19||
start - 2021-11-18 17:00:00
|Jakarta (WIB: GMT+7:00)||2021-11-16 to 2021-11-19||start - 2021-11-15 17:00:00
end - 2021-11-19 16:59:59
Note that the third column contains two values - the start of the timestamp constraint and the end of the timestamp constraint; you can use the SQL between operator to constrain the times.
If the fix above does not solve your issue, please contact support.