Crash Protection (CP)
Our Crash Protector (CP) keeps your servers safe from performance disasters by:
- Proactively monitoring and controlling the total number of requests hitting your system
- Tracking excessively long running requests
- Limiting or restricting requests when the server is low on memory
The Survival Strategy outlines how FusionReactor will respond during a triggered CP event. FusionReactor can be configured to alert you to the problem, kill problem requests and queue new requests until server performance has become stable.
Self-healing – block or even kill a request
FusionReactor automatically notifies you, both visually and/or via email, when a crash protection event is triggered, and what action (if necessary) was taken to protect your server.
Relevant information captured at the time of the event may also be included, allowing for a detailed post-event analysis and aiding corrective intervention.
When should you enable Crash Protection?
There are many cases in which CP can be an invaluable tool. These include:
CP automates the manual process of checking each of your servers and verifying that they are operating within satisfactory parameters. Instead of having to periodically go through each server you can have warnings sent directly to your inbox.
If you have a server which receives bursts of requests all at once, FusionReactor can queue requests to spread the load out over time – protecting your server from becoming overwhelmed.
If you periodically have very resource hungry jobs running then Crash Protection can stop new requests being run which could potentially cause the server to become unstable.
If you need to write a page that cannot use more than a fixed amount of system resources then Crash protection is a good way of tracking where and when you have problems. As well as emails, Crash Protection triggers can be viewed in the log files.