When sessions are closed, they are moved from the Short-Term Canister to the Long-Term Canister, where they are queued for indexing. If the session indexer is unable to index the queued sessions fast enough, the queue can grow and grow. This unhealthy situation should be investigated.
In the following example, you can configure a canister alert to issue an alert when the number of queued sessions exceeds 1,000.
Note: For testing purposes, you may want to set this to a low value that you know is exceeded. Remember to reset the alert to appropriate threshold values after you tested it.
- In the Event Manager, click the Alerts tab.
- Select New Canister Alert.
- For the Name of the Alert, enter the following:
Alert - Sessions waiting for index > 1000
- Select a group for the alert, as needed. You might create a group such as the following:
Canister - Spooling
- Select Active.
- Click Configuration.
- For Alert Type, select
Count
. - For the Event, click Select.
- Select
Un-indexed Sessions
and click OK. - Do not configure a dimension value.
- Select the server. For this example, select
Sum All Servers
. - For Direction, select
Positive
. - Set the Alert Threshold to
1000
.You can specify the reset interval after the alert fired. If the interval is exceeded again before this time period expired, then another alert is not fired.
- You can configure a warning threshold, which can be designed to fire when the alerting threshold is close to being exceeded. For this example, set the Warning Threshold to
750
. For this example, leave the default value of10
minutes.You can specify the reset interval after the warning alert fired. If the warning interval is exceeded again before this time period expired, then another warning alert is not fired. For this example, leave the default value of
10
minutes.
- For Alert Type, select
- Click Notification and specify where you want the alert delivered and in what format.
For testing purposes, send the alert to your email address.
- Click the Blackout step.
If Canister maintenance is performed every night, you might want to schedule a blackout during the time of maintenance and for some time afterward, so that sessions that were queued during maintenance can be processed without triggering an alert.
- After you specify the alert, click Save Draft.
- To commit the changes to the server, click Save Changes.
- If you entered test values for the thresholds, remember to change the values to appropriate ones after testing is complete.
- You might also want to revisit the Alert Notification properties.