| Anchor | ||||
|---|---|---|---|---|
|
| Include Page | ||||
|---|---|---|---|---|
|
Description
This option will allow you to change alert management settings as shown below:
Settings
Select alert mail mode (HTML/TEXT)
Alerts are by default sent in HTML format. With some mail clients, HTML mails are not correctly displayed or even rejected. This option is used to switch between HTML format and pure TEXT format.
HTML mail example:
TEXT mail example:
Update alert mail recipients list
All alerts coming from monitoring scripts and checks scripts are sent using a common alert script which by default sends a ‘wall’ message to all connected users and an email to the recipient list that can be customized using this option
It is edited using ‘vi’ editor or if installed, the ‘nano’ editor, or, if possible, the ‘gedit’ graphical editor (Windows notepad like) or ‘emacs’.
Notes:
- No comments allowed
- No blank lines
- One recipient per line
Create/update alert mail footer
Used to add comments at the end of the mail. HTML tags like new line, font and bold can be added within the file, in case the format is switched to TEXT, these tags will be automatically removed from the text mail.
Example:
Enable/disable wall alert messages
Alert are by default sent via email (sendmail) and also warns the connected user via a wall message.
This option enables or disables these wall messages.
Update/reinstall common alert script
All alerts coming from monitoring scripts and checks scripts are sent using a common alert script.
If this script does not exist, it is initialized by copying an example provided.
If it exists and is different from the original one, you are invited to reinitialize it from the default one:
- use this if you did not change the original script file and you updated the Linux Utilites kit
- do not use this if you customized your own alert script
Example:
This script can be customized to send alerts the way you want, adding for example commands to link with your monitoring tool. It is based on an alert code passed as parameter 1. All other parameters are information used to send alerts by default with a ‘wall ‘ command and an email sent to the alert mail recipients list described above. The script uses templates in order to send emails and wall messages (templates/*.mail and templates/*.wall files)
It is edited using ‘vi’ editor or, if possible, the ‘gedit’ graphical editor (Windows notepad like).
Parameter1 can be the following:
Parameter 1 | Severity | Description |
| ABORTED | CRITICAL | Guest has stopped without user or service request |
AKSUSBFAIL | CRITICAL | If the dongle is detected as removed whereas it is disconnected, the askusb daemons are restarted. If the restart fails after 15 tries, this message is sent |
BOOTDUPL | WARNING | Tried to start a guest that is already running or a guest is found more than once in the guests list |
BOOTNOTFND | CRITICAL | The file containing the guests to |
...
start is empty or not found | ||
EMULSTART | INFORMATIONAL | Emulator has been started |
EXPCHK | CRITICAL, MAJOR, MINOR, INFORMATION | The license is about to expire |
FOUND | INFORMATIONAL | License dongle found at startup |
HASPWARN | CRITICAL | Warning messages found in the license, guests cannot start |
| IFCFGADDR | CRITICAL | The network interface defined in the configuration has already an assigned IP address, cannot be used for guest |
| IFCFGCRIT | CRITICAL | One parameter in the ifcfg-ethN file is not configured correctly (mandatory value) |
| IFCFGUNKN | CRITICAL | The interface name defined in the configuration file is not valid (not found with 'ifconfig <eth>' command) |
| IFCFGWARN | WARNING | One parameter in the ifcfg-ethN file is not configured correctly (recommended value) |
INVALID | CRITICAL | Invalid configuration on dongle to start the guest |
NOTFOUND | CRITICAL | The guests have not been able to start at boot due to dongle disconnected |
REMOVED | CRITICAL | Dongle has been removed: the guest sees the dongle as disconnected and will stop after the defined interval if the dongle is not replaced |
REMOVRESET | ERROR | Dongle seen as removed whereas not disconnected (aksusb driver failure). In this case the USB is reset and drivers are restarted ( |
STOPPED | CRITICAL | Guest has been stopped, reasons explained in parameters 4, 5 and 6 |
| STOPPEDREQ | INFORMATIONAL | Guest has been stopped, requested by user or shutdown |
| TESTMAIL | INFORMATIONAL | Used to test email mode when setting HTML or pure TEXT |
TOEXIT | CRITICAL | The guest is about to exit, reasons explained in parameters 4 and 5 |
USBDISCONNECT | MAJOR | Dongle has been removed (immediate detection) |
Select guests log alert level
Select the alert level to send alerts when events are found in the guest log file:
| Level | Information | Warning | Error |
|---|---|---|---|
| 0 |  | | |
| 1 |  | | |
| 2 | | | |
| 3 | | | |
Requires the charon_logevent entry activated in the crontab file => menu option 5 - Manage recursive jobs: license expiration check, log events (cron)
This does not affect guest startup alerts. You will receive alerts when a guest starts whatever the level is
| Include Page | ||||
|---|---|---|---|---|
|