Proactively Monitor your ColdFusion server with FusionReactor

How well do you know your ColdFusion Server?

What’s your average request time?

  • 5 minutes after restarting the application server
  • 5 days after restarting the application server

What is your total request count & total JDBC query count after 24 hours of uptime?

What is the shape of the 6 graphs on the system metrics pages?

  • After 1 minute uptime
  • After 1 hour uptime

The system metrics charts can easily be switched between minute and hour views using the clock icon.

Using the forward arrow icon you can easily access the detailed charts for individual metrics.

Perform periodical analytics on your ColdFusion Server

Periodically reviewing and improving the worst performers on these pages is a sure way to a more stable and better performing server.

Longest Requests displays the longest running requests since the server was last rebooted.

Longest JDBC lists the longest DB calls since the last application server restart.

Slow Requests shows which recent requests have taken longer than the threshold value (default 8s).

Alter the threshold to be more meaningful to your platform – 10% or less of your requests should meet this threshold.

See our Live Demo


Enterprise Dashboard
(Enterprise Edition Only)

Get a 1 stop, easy viewing port into the health of all your servers

Configure the Enterprise Dashboard to monitor all your instances.

Instances can be defined in multiple groups. Group instances by both physical machine AND logical application to make it easier to identify machine or platform specific problems.

See our Live Demo

Enterprise Scripting
(Enterprise Edition Only)

Scripts can do anything you can imagine, call a URL, send an email, SMS a pager, if you can script it, FusionReactor can execute it!

Combine the Enterprise Dashboard configuration with Enterprise Scripts to react to failure conditions.

The FusionReactor installation comes with several basic scripts to restart a failed instance – even if it’s on another machine – for both *nix and Windows environments! Check them out in <FusionReactor installation folder>/etc/cp


Crash Protection

Enable crash protection to automatically react to timeout, memory or request count thresholds.

Restrict heavy-duty pages such as scheduled tasks from triggering the crash protection rules.

  • This means you can write rules to cover your valuable external requests.

Start with notify only rules to monitor the number of alerts you’ll receive.

  • If you don’t receive any alerts your thresholds could be too generous!

Securing FusionReactor

FusionReactor can be accessed through either the external web server (e.g. Apache or IIS) or its built in web-server (on port 8088 by default).

All FusionReactor access is password protected. You can further increase security in one or more ways:

  • Bind FusionReactor’s internal web server to an internal network IP
  • Disable external web-server and firewall the internal web-server port away from public access.
  • Disable the internal web-server and secure external web-server access with your own web-server rules (e.g. IP restrictions, SSL, etc)