When the stuff hits the fan:
- you want to know what went wrong and why
- diagnostics to track errors and other info – in CF, web server, DB and whole OS.
- available tools for monitoring CF – free/commercial/cf/generic
- presentations at http://www.carehart.org/presentations
Typical Scenario
CF stops responding
What do you do?
- Restart CF – doesn’t find root cause
- Diagnostics logs – finding the right logs can be valuable
- Monitoring tools – which ones? built in vs add on? check for running requests.
- search google/mailing list/troubleshooting support
Free Tools
CFSTAT – reports high level measures. num of requests running, queued, avg req time, more. sadly not there in the multiserver mode. enabled on the CFAdmin on the Debug Output Settings page.
Gotcha Note: avg req time is only the last 2 requests averaged so that value is not fully reliable.
GetMetricData(“perf_monitor”) – returns same data as a CF structure.
JRun Metrics – enabled in 6 to add a line at regular intervals to track current state (threads, mem usage, j2ee sessions, more)
CF8 Server Monitor – only in Enterprise. Charlie has 4 part blog series (option to turn on url vars ie. fuseaction) on his website.
Admin API – same as monitor
Commercial Tools
FusionReactor and SeeFusion
Both work with 6, 7, 8, 9, OpenBD and Railo.
All three open the blackbox to see currently running requests, view past long running requests, see details of each query as well as stack trace.
Alerts can be setup for certain states to email notifications.
FusionReactor writes more logs that can be very valuable.
Full presentation at http://www.carehart.org/presentations/#cf911
Post a Comment