> As a side note, I am sure you are aware of this, but by killing the worker every 100,000 calls, out of the 2 million calls > nearly all of the log entries are missed as they are in the queue when the worker is killed. I am getting at most 24,000 > log entries in the text file.
I've lost track, but I think that this was the very thing I was testing - the %/# of lost log lines I would end up getting. The more I think about it, the more I'm convinced that what I'm trying to do simply isn't part of the designed capacity of 4D's system. I can live with that, I'll just move the logging out of 4D. I may lose something that way (a bit of data that would come from a 4D looking that could inject some extra data) and it's a pity, but 4D never promised me a log writer. It's just not sufficient to requirement. So, checking what NGNIX offers. On the log enrichment side, Loggly offers, well, very little but I'll be checking out SumoLogic down the road and that looks a whole lot better. (It's a Splunk clone, as far as I can see, but cheaper.) ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
