Clicky home »
That's correct. Yes, the new servers are wicked fast. Your user page will load much ...
Sean (Clicky), Jun 14 2016
So, to be clear, when a DB server is being migrated there will not be any data loss ...
Shaun, Jun 14 2016
I forgot to mention in the post, the "Pages" and "Query Parameters" filters were ...
Sean (Clicky), Oct 22 2015
Yes, I've played around with the idea but I haven't come up with a way to put it ...
Sean (Clicky), Oct 22 2015
Have you considered creating a button/link in the app to report spam-referrers?
Jacob, Oct 22 2015
great concept to go with your great product, thanks
Anthony, Oct 21 2015
Excellent work guys! Looks great and it must be rewarding to see this A+ rating for ...
Beuk, Oct 09 2015
Nginx does wonders for you. I am glad you guys managed to move and reduce costs ...
Angelica, Oct 06 2015
Is there a way to do this with Uptime?
Ringo64, Jun 16 2015
Hi Sean, Great, thanks for the heads up I wasn't aware of this option :) This ...
Chris, May 10 2015
Some bugs are so stupid
Note to self: The hour from 2am to 3am is a BAD time for a critical
, because this hour doesn't exist on the day Daylight Savings kicks in. Doh :(
| Mar 10 2008 9:11am
I'd never considered this, assuming crond had some smarts for the situation. Do you think this also means that in the fall (when dst ends) your jobs scheduled for that hour would run twice?
Mar 10 2008 10:35am
I would assume so! I hadn't even thought of that either. DST ended on 2007-11-04, I just went and checked that date for this particular script and it looks like it only ran once. Hmm...If it's smart enough to not run twice when DST ends, you'd think the same would be true the other way around.
Mar 10 2008 10:52am
Speaking of bugs, a random idea I had earlier was perhaps allowing a second level of 'host it yourself' with the tracking code.
The problem with the current method is that even if we host the tracker JS ourself a critical connectivity/outage issue can cause failures, which manifested itself as an example a few weeks ago when something happened causing a morning/night full of stats to be lost (I forget what exactly).
The idea was that you also provide some kind of PHP script that people put onto their site, which serves the image that the JS file normally collects and writes the data to a flat file. Then, using a cron job or something, that data is independently sent to Clicky every 5 minutes or whatever. After a day or so the flat file data could be pruned.
It'd completely seal the deal for those sites that absolutely must ensure they get their stats tracked (even if nothing more than peace of mind), and has the added benefit of making the (perceived) loading time of pages a bit snappier. It may even allow download/outbound tracking to lose the annoying delay. Perhaps only offer it to paying customers due to the work involved.
Food for thought, anyway!
Mar 11 2008 1:56pm
That's an interesting idea. Are there any other solutions you're aware of that offer something like that?
Mar 11 2008 5:50pm
My host just banned my ip from logging into my own servers! But bugs are just as bad, now I gota call them and have them let me back on!
Mar 11 2008 11:58pm
Heh-heh-heh ... having been in software quality for 25 years, I can tell you, your statement is so very true.
And, I do NOT mean that in the way some take it. I have done this job for a very long time, and the smallest of mistakes or oversights just, happen. Really. It's just a matter of what is going on at the same time a snippet is typed, ya know?
And, don't get me wrong, I've written code too. I make mistakes all the time - it happens.
Your product is still AWESOME, so, who cares about a cron job?!
(not me - i never noticed) :)
Mar 13 2008 10:33am
Steve, I know, the most frustrating bugs are the ones that are so stupid you would never even think it could possibly be anything to do with whatever ends up being the problem, and then you want to die. The cron job in questions sums up the unique visitors, average time, bounce rate, and exit pages for each site, since it's not possible to sum that up throughout the day unlike most other numbers we're storing. It wasn't noticable until 2 days had passed because my code will only calculate that data on the fly for "today" and "yesterday", otherwise we display it as empty. By this time I had completely forgotten about DST and spent many hours figuring out why it failed until I finally realized what had happened and smacked my head against the table repeatedly.
Mar 13 2008 4:43pm
and to increase the value of its annual produce. His capital employs, too, present and though this might, no doubt, be a considerable inconveniency to them, it would,
Mar 15 2008 12:51am
Hmm. That's an excellent point.
Mar 15 2008 6:54pm
Mar 16 2008 8:02am
Post a comment
Copyright © 2017, Roxr Software Ltd