You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When ping is enabled, add a flag eg ping_enabled=1 to all other tracking requests. In that case we'd know a ping request will follow to update log_visit.visit_last_action_time and time on site. Therefore, it is not needed to update these fields avoiding potential locks on log_visit, less IO, ...
The text was updated successfully, but these errors were encountered:
Is this a change in behavior for visits that is coming in 4.0 ? I discussed this in #15179 where I expected last_action_time to be updated when using heartbeats.
I'm wondering since I have a plugin that updates a visits visit_last_action_time with the timestamp present in the heartbeat.
tsteur
added
invalid
For issues or pull requests that are no longer relevant to Matomo core.
and removed
c: Performance
For when we could improve the performance / speed of Matomo.
labels
Apr 27, 2020
Good point. Heartbeat is actually indeed not supposed to extend the visit by default and therefore will close the issue. Wasn't remembering that at the moment. It could be done if there was an option that it extends the visit but if it's not the default it wouldn't help too many.
When ping is enabled, add a flag eg
ping_enabled=1
to all other tracking requests. In that case we'd know a ping request will follow to update log_visit.visit_last_action_time and time on site. Therefore, it is not needed to update these fields avoiding potential locks on log_visit, less IO, ...The text was updated successfully, but these errors were encountered: