FOG User Tracking -Search
-
@Daniel-Miller said in FOG User Tracking -Search:
@Greg-Plamondon said in FOG User Tracking -Search:
I checked the userTracking table in the fog database and it has 22104 records
You can keep pushing execution time out, but it is quite possible that you may have too many entries for php to handle the data in a reasonable time frame, especially if this instance has been running for a while. If you don’t need the historical data, truncating the userTracking table (
truncate table fog.usertracking
) as suggested in https://forums.fogproject.org/topic/11713/503-service-unavailable-error/54 should get it up and running and will show data going forward until it gets too ungainly again.I was able to truncate the table and then run a report. I wish i was able to store more records.
-
While I have no grounds to substantiate the claim, I really believe 1.6 will handle this kind of thing much better. Sure I don’t have 22k worth of entries (or more depending on the use case) in my userTracking table, but now that we have pagination, things should be a little better here. This, of course, makes reporting for “all” of the rows a little more difficult. But at least it allows searching and viewing information a little simpler without having to go to the extreme of truncating the whole table.
I’m sorry it took so long for us to have this implemented.
-
@Tom-Elliott said in FOG User Tracking -Search:
1.6
I have ## Version: 1.5.7.56 installed…
what repo is 1.6 in? -
@Greg-Plamondon said in FOG User Tracking -Search:
what repo is 1.6 in?
should be able to do a
git checkout working-1.6
, if I recall. -
Of note, I’m calling it 1.6 because when we do release it, that’s what this will become.
It is using the current latest version (1.5.7) and the .XXX after is the number of commits ahead of the master branch the working-1.6 branch is at.