Threshold Alerts allow you to instruct N|Solid to take certain actions (such as taking heap snapshots or CPU profiles) when one or more processes cross over performance thresholds that you set.
Often, performance problems occur in production code non-deterministically and the only information you have available to diagnose the situation is in an error log or possibly a stack trace. With N|Solid's Threshold Alerts, you can automatically capture more useful information when problems arise in production.
From the main application page, click on an application to enter the cluster view. Click on
Threshold Settings, located near the upper-right corner of the page.
There are two types of thresholds to choose from: Heap Used and CPU Used. You may configure actions independently in both.
To enable a threshold, click the switch immediately below the ENABLE THRESHOLD label.
Depending on the threshold you selected, drag either the maximum heap percentage or maximum CPU percentage slider immediately below the switch. Set this value to the ceiling you do not wish your application's processes to exceed during normal operation. When enabled, there will be a dotted red line in the corresponding graphs that indicates where the threshold is set.
Next, set the threshold delay. This setting allows you to prevent short blips of activity, which do not necessarily indicate an issue, from triggering a threshold.
As threshold actions can themselves be resource intensive, the threshold snooze setting ensures that the performance of your application does not suffer due to excessive profiles or snapshots and that your inbox is not inundated with repeated notifications.
Note: When a threshold is set, a draggable bar for that threshold will appear in the cluster view. To change its value, click and drag the square handle at the center of the bar. To quickly open the Threshold Settings panel, double-click the square handle.
Now that you have configured your threshold parameters, select one or more actions that N|Solid will perform when a threshold is triggered:
Finally, don't forget to click click the Update button to save your settings.
Note: Be careful about setting a very high threshold, such as 99% Heap, and then selecting an action that uses the same resource, such as
Take Heap Snapshot. Taking an intensive action at a very high ceiling is likely to negatively impact your application.