Server Monitoring - Take Care Of Server Intrusion
Posted by Mike Brunt at 8:29 AM
24 comments - Categories: ColdFusion | JRun-J2EE
I have had several clients recently who have had issues which appear to be related to inopportune use of server monitoring. We were all delighted when Adobe announced their server monitoring capabilities for ColdFusion 8 yet it became apparent that leaving on "memory tracking" in production could cause significant issues, I use this as an example of inopportune use of server monitoring. Recently I had a client who's servers would suddenly go off line once they reached 10 threads in use, even though there appeared to be no great state of distress overall, free memory was fine. This was not related to the server monitor in ColdFusion 8 but to a crash protection capability in another product.The main point of my post here is that in my opinion and experience with many, many clients server monitors should do nothing more than just that, monitor the server. There is no magic bullet in any product that I have ever seen that fixes underlying issues. In fact the more data a product offers often the more obfuscated the actual cause of problems. If we are allowing something to shut-down our servers that is not a solution but a band-aid and I personally would not be trusting something to shut-down my production instances.
The perfect product for me would give me the ability to watch request times, threading and memory use along with SQL passed along the JDBC driver in real-time. Also to have something that allows the setting of warning thresholds to notify me of high thread or low memory situations and also have the capability to save this information along with slow request information with the query string details to a log and database. Lastly, something that gives me a plain, understandable translation of the meaning of critical stack traces.
That is it for me, that is enough to see and analyze any problems I have ever encountered for all the clients I have ever helped.