The ColdFusion Server Monitor is an Adobe Flash application that lets you keep track of activities on a ColdFusion Server. You can identify information about the server, including requests, queries, memory usage, and errors. You can start and stop collecting server information and take snapshots of the server.
You can start and stop monitoring, profiling, and memory tracking by clicking the corresponding buttons in the top bar. By default, the ColdFusion Administrator turns off server monitoring; you must explicitly start Server Monitoring. The following table indicates what data the Server Monitor collects when you click the start button:
Button |
Action |
Start Monitoring |
Starts gathering information about all requests, including active requests, slowest requests, active sessions, cumulative server usage, highest hit counts, template cache status, request throttle data, requests that timed out, requests with errors, and server alerts. The Server Monitor does not gather information for requests that are excluded on the Filter Settings page. |
Start Profiling |
Starts gathering tag and function timing information for the Slowest Requests report; the CFML stack trace for the Active Requests report; information about active queries, slowest queries, cached queries, and query cache status; database pool status; and the most frequently run queries. This lets you find bottlenecks in your application. You can view details about each request that is slow or consumes a lot of memory. You can determine which tags and functions cause the request to run slowly and which variables consume the most memory. You can use this information on both development and production servers. To gather the profiling information, turn on monitoring, profiling, and, if needed, memory tracking. |
Start Memory Tracking |
Starts gathering information about memory consumption, including overall memory usage, the queries and sessions that have used the most memory, and the memory usage of all application and server scopes, and profiling information on the largest variables on the Requests by Memory Usage report, if profiling is enabled. You must enable profiling to view query-related reports; you must enable profiling and memory tracking to view the Queries by Memory Usage report. |
Reset All Statistics |
Resets all statistics collected on the server. |
Refresh |
Updates the data for all the graphs, reports and message boxes on the page. |
When you start the Server Monitor, the Overview page appears. To return to the Overview page from any other page, click the Overview button in the top bar. of the Server Monitor.
By default, the Server Monitor retrieves data for graphs every 5 seconds; it retrieves data for reports every thirty seconds. All of the graphs lets you display all the data collected or the data collected for a specified recent period of time.
The Server Monitor lets you control the granularity with which you turn monitoring on and off with the following buttons:
Start Monitoring - Turns on all monitoring.
Start Profiling - Turns on monitoring of individual tags, functions, and query execution times.
Start Memory Tracking - Turns on tracking of memory used by different scopes. If Profiling is also on, the Server Monitor tracks the memory used by individual tags, functions, and queries.
Turning on or off monitoring, profiling, and memory tracking determines which data the Server Monitor gathers. For example, all of the query reports require that you turn on profiling. The performance impact of turning on monitoring and profiling is minimal; however, the performance impact of memory tracking can be significant.
The Server Monitor contains the following sections:
Request Statistics
Settings