--
You received this message because you are subscribed to the Google Groups "FusionReactor" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fusionreacto...@googlegroups.com.
To post to this group, send email to fusion...@googlegroups.com.
Visit this group at http://groups.google.com/group/fusionreactor?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
What you’ll find (and I gather David will document) is that there are some aspects of what FREC grabs which they get from the Admin API, and some of specifically which is from the servermonitoring.cfc, which as you note will only work in Enterprise. There are many things that WOULD be reported by that that they are getting anyway in CF Standard, using the various undocumented CF java objects.
But even on Enterprise, some things will only be captured by FREC (just as in the CF Server monitor itself) if the server monitor’s “start monitoring”, “start profiling”, or “start memory tracking” buttons are enabled. So when they say of some things that you need that on, it just means that thing won’t be reported (or will report as 0 or an empty string) if they are not.
Not even adobe does a great job of clarifying what parts of the monitor don’t report if one or more of these options is not enabled. I can understand the challenge for Intergral in clarifying it as well. It’s great to hear that David is considering it. I’m sure many would benefit, and then also the FREC docs (and indeed FusionAnalytics, which also leverages those FREC logs) would be improved.
David, to save you the trouble of doing it all, you may want to consider creating a wiki, google doc, or some other group-updatable resource, where I and others could help you in identifying what in the FREC logs is in Standard vs Enterprise, or what is only enabled depending on those “start” buttons.
/charlie
--