The EventDaemon allows you to set warning thresholds for event queue alerts issued by the EventDaemon itself. The Queue Warning Message settings determine the level at which the EventDaemon flood condition has started. Corresponding alerts are created in the System Message Channel. There are two ways in which you can modify the threshold:
Note: When you change these values in the EventDaemon GUI or through a telnet to the EventDaemon, the changes made are only temporary. To set the thresholds permanently, you must edit the $PPHOME/bin/EventDaemon script - this is detailed at the end of the article.
1. EventDaemon GUI
Open the BES Console and navigate to Configure > EventDaemon GUI
Connect to the BES Server through the GUI, then Tools > Warning Messages
Enter a value that will, once exceeded by the queue, trigger the first warning message to be sent.
Then enter an escalation threshold that escalates the severity of the original warning message.
2. Command Line
From an SSH session to BES as ppadmin, issue the following command:
telnet localhost 40002
Edit the warning startpoint by selecting option p
Edit the escalation threshold by selecting option x
Permanently modify the thresholds
the changes made above are only temporary and will be reset when the EventDaemon is recycled. To set the thresholds permanently, you must edit the $PPHOME/bin/EventDaemon script as follows:
1. Using a text editor, open the file $PPHOME/bin/EventDaemon
2. Find the line:
exec ./java -Xmx512m -Duser.language=en -Duser.region=GB -DPPHOME=$PPHOME -DPPWORK=$PPWORK -DPPLOG=$PPLOG com.interlink.powerpack.eventdeamon.EventDeamonJM
And update it to:
exec ./java -Xmx512m -Duser.language=en -Duser.region=GB -DPPHOME=$PPHOME -DPPWORK=$PPWORK -DPPLOG=$PPLOG com.interlink.powerpack.eventdeamon.EventDeamonJM 500 200
3. Save the file.
4. Recycle the EventDaemon (ppStop/ppStart -n EventDaemon)
In the above example, the first alert will be generated when the EventDaemon queue exceeds 500, then, further alerts will be created in queue increments of 200.