ghghgh call me
please specify if you want data collected every 1 s or ever 30 s or anything in between. Max logfile size is 100 MB, but you already know that
I anticipate that you should be able to exclude/delete any events between t1 and t2, where t1 is 11 PM and t2 is like 2 AM, a period of time during which there are some server-side scripts kicking in, events that we probably don't care seeing in stats or studying too much.
I'm not particular about the data collection rate or the log file size, though bigger is better (for my purposes, not necessarily anyone else's), and a shorter sample period will likely generate a larger file faster.
I've done too much work with clients that run three shifts to be able to blanket-ignore any particular time period... but providing that option is a very interesting idea... ;-)
1 of 1 people found this helpful
We can always import the logfile in filemaker, find any records we don't care about and delete them, then export to csv again and feed it to FMPerception, but it's an extra step.
As I said, the max you can get is a 100 MB file. There's much uninteresting data in it, like filemaker 15 doing its cache compare etc.
Of course, my DDRs for the whole system are like usual more than 1 GB...
Oh, come now... At this point, there is no "uninteresting" data.
And I know all about your DDRs, sir. But as you know, that won't slow me down.