When I view the blocked domains page, I know what domains were blocked for an individual day, but I don't know what time the block occurred. Having access to a timestamp for each block would help us determine who was at the computer at the time.
11 Comments
11 Comments
Who voted for this idea
- pencoyd
- ahoier
- meilleur
- banditz71
- Alejandro Casidsid
- Brian Watters
- coldghost
- dolric
- gamer8519
- dauphin
- vxjasonxv
- rafaelharari
- flatlinebb
- rnebiker
- quaternions
- dcockrell
- os2mac
- war59312
- Elisamuel
- giantsfanatic
- nanabite
- willwill
- Brett
- argus
- jasonward
- Joey
- danbedford
- breakforth
- mkanakos
- dhughes
- nhhcs
- ckoehler
- staticxfl
- Randy
- bdcamp
- mcdave
- K
- neilkelty
- gregoryfenton
- Nick
- skymaster
- statm1
- Michael
- networkjedi
- airboss
- ricky1146
- Bill Palafox
- bushytail
- adbrem
- fmoses
Comments
I tried what nat.woodbridge suggested but was unable to make it work. - but even if I was able to - it still would be nice to see the most recent time / date right on the blocked domains page.
I'm not seeing a date/time stamp, either. I would really like this feature.
Should have made is clear, sorry, they are currently making "performance improvements to top domain statistics and they are currently unavailable."
When its are back, you should be able see when the domain was last accessed using the total requests page.
But I do agree that it would be useful have the most recent time on the blocked domain page - it would give an nice overview.
written by Kyle Hotchkiss 461 days ago
Rating: 1
| Rate Comment:
It'll clog up the databases faster realistically, with 7 billion requests a day, Storing the domain is enough.
written by choppahfowah 288 days ago
Rating: 1
| Rate Comment:
I agree that having a timestamp feature would provide additional useful (and interesting) information about blocked site access attempts. HOWEVER, I am also concerned about what system resources would be required to implement this feature. If it is not too demanding, then I would say add it!
written by argrithmag 261 days ago
Rating: 1
| Rate Comment:
Or if not on the page itself, add additional information to the CSV file downloaded. Then I can sort, filter, etc.
Or allow me to limit the display to within the last hour(s). That at least would then reduce the query result set pulled from the DB.
funny, a DB already has a timestamp for each element in the table for when it was inserted/modified. So it's not like you HAVE to create a new field to store a time stamp. We only need the query result set to include the timestamp of the field with the recorded entry of the domain name. Unless of course the DB is lazy and only modifying the count field for each unique IP/domain in which case the last access is the only timestamp availabe. But still. Even if all we could get asap was the last access timestamp, that timestamp combined with the total count would be very useful info. We use OpenDNS to monitor a single 24/7 computer in a store that many employees and managers use. It would be nice to match the last access time stamp with camera video to see who exactly accessed the logged domain. Helps with employee reviews. I am sure there are many uses for a last access timestamp.
The stats are not as useful without any kind of time stamp. I don't mind if an employee is using facebook, or something similar, at lunch, but I do care if they are using it during work hours. I know I could block it altogether, but if everyone is being responsible, then I wouldn't have to. The only way I will know is if there are time stamps.
Sign in to comment or register here.
If you look at the total request page and "Include only these domains" for the blocked domain you want to find out about. You can find out when the site was accessed.
I cannot get to my stats right now, but when they are back again, It should work.