Thread Starter
Seath
(@seath)
@rogierlankhorst It is all ranges including custom range.
Ok, I have added more logs to this branch to be able to see what is going on. Can you try the latest, then pick for example the last 30 days range, and post the resulting logs here? It doesn’t seem likely it’s a caching issue, but the logs should confirm that, and I can then also see if there’s anything off with the dates etc.
Thread Starter
Seath
(@seath)
@rogierlankhorst Here it is…
Jan 25, 12:58:46
Array
(
[0] => stdClass Object
(
[hit_count] => 3
[period] => 2023-01-24
)
[1] => stdClass Object
(
[hit_count] => 10
[period] => 2023-01-25
)
)
Mark as fixed | Ignore
Jan 25, 12:58:46
regenerated data:
Jan 25, 12:58:46
cached insights results
[25-Jan-2023 18:58:46 UTC]
Jan 25, 12:58:46
SELECT COUNT(DISTINCT(uid)) as hit_count,
DATE_FORMAT(CONVERT_TZ(FROM_UNIXTIME(time), '+00:00', '-06:00'), '%Y-%m-%d') as period
FROM (SELECT * FROM burst_statistics WHERE session_id NOT IN (select session_id
from burst_statistics
WHERE time > 1674626400 AND time < 1674712799
GROUP BY session_id
having count(*) = 1
and sum(time_on_page) < 5000) and time > 1674626400 AND time < 1674712799) as stats
GROUP BY period order by period
Jan 25, 12:58:46
select SQL
Jan 25, 12:58:46
Array
(
[metric] => visitors
[date_start] => 1674626400
[date_end] => 1674712799
[interval] => day
[date_range] => custom
)
Jan 25, 12:58:46
get insights data args
Jan 25, 12:58:46
Array
(
[date_start] => 1674626400
[date_end] => 1674712799
[date_range] => custom
[metrics] => Array
(
[0] => visitors
)
[interval] => day
)
Jan 25, 12:58:46
insights args
Jan 25, 12:58:43
Array
(
[0] => stdClass Object
(
[hit_count] => 3
[period] => 2023-01-24
)
[1] => stdClass Object
(
[hit_count] => 10
[period] => 2023-01-25
)
)
Jan 25, 12:58:43
regenerated data:
Jan 25, 12:58:43
cached insights results
[25-Jan-2023 18:58:43 UTC]
Jan 25, 12:58:43
SELECT COUNT(DISTINCT(uid)) as hit_count,
DATE_FORMAT(CONVERT_TZ(FROM_UNIXTIME(time), '+00:00', '-06:00'), '%Y-%m-%d') as period
FROM (SELECT * FROM burst_statistics WHERE session_id NOT IN (select session_id
from burst_statistics
WHERE time > 1674626400 AND time < 1674712799
GROUP BY session_id
having count(*) = 1
and sum(time_on_page) < 5000) and time > 1674626400 AND time < 1674712799) as stats
GROUP BY period order by period
Jan 25, 12:58:43
select SQL
Jan 25, 12:58:43
Array
(
[metric] => visitors
[date_start] => 1674626400
[date_end] => 1674712799
[interval] => day
[date_range] => custom
)
Jan 25, 12:58:43
get insights data args
Jan 25, 12:58:43
Array
(
[date_start] => 1674626400
[date_end] => 1674712799
[date_range] => custom
[metrics] => Array
(
[0] => visitors
)
[interval] => day
)
Jan 25, 12:58:43
insights args
Jan 25, 12:58:41
Array
(
[0] => stdClass Object
(
[hit_count] => 3
[period] => 2023-01-24
)
[1] => stdClass Object
(
[hit_count] => 10
[period] => 2023-01-25
)
)
Jan 25, 12:58:41
regenerated data:
What I see in the logs is that a new query runs, but the output of this query on the database returns an empty dataset.
I ran the same query on our own website, and get a valid array of hits back, so the query itself seems good.
I see the selected range for the above is:
from Wed Jan 25 2023 06:00:00 until Thu Jan 26 2023 05:59:59
Does that match with your selection at that time?
Is it possible that burst hits aren’t registering in the database at the moment? Can you share your domain so we can take a look at the track hit? You can also send your domain to support(at)burst-statistics.com if you don’t want to share it here.
Thread Starter
Seath
(@seath)
@rogierlankhorst The hits are being registered, I can see then in the windows next to the graph. They are just not showing up in the graph itself.
It is weird because I have the same problem on my test site where are no hits at all.
I tried bunch of selections including custom ones.
I did emailed you my site “Support ticket 16410485”
