Nodeum provides 2 notifications options :
Both can be configured to send information about the usage of the solution and send alert to notify specific misusage or misconfiguration of the solution.
To receive by email the Notification about the system, complete the form with the following informations:
- Hostname / IP address: SMTP server to use.
- From email address: the sender email address.
if your SMTP server requires authentication to send emails, you need to specify Username and Password.
Once you have configured the SMTP server, you can add email recipients:
Enter the email address of the recipient and select the level of severity that will trigger the email notification.
Simple Network Management Protocol (SNMP) is a communication protocol that enables network administrators to manage network equipment, monitor and diagnose network and hardware problems remotely. Nodeum allows to send SNMP trap to SNMP collector(s).
The following parameters are required to create SNMP server configuration:
- Community: The community to use; by default public should be used.
- You can also fill in the System Location and System Contact if required.
Once you have configured the SNMP Community, you can add trap destination:
Enter the destination address of your SNMP server and select the level of severity that will trigger the SNMP trap messages.
Definitions of Level of Severity
A message of this severity is for information purposes only; no error was detected and no reply is needed. The message could indicate that a function is in progress or that it has reached a successful completion.
A message of this severity indicates a potential error condition. The software may have taken a default, such as supplying missing input. The results of the operation are assumed to be what was intended.
An error has been detected, but it is one for which automatic recovery procedures probably were applied, and processing has continued. A default may have been taken to replace input that was in error. The results of the operation may not be valid. The function may be only partially complete; for example, some items in a list may be processed correctly while others may fail.
The error detected is too severe for automatic recovery, and no defaults are possible. If the error was in source data, the entire input record was skipped. If the error occurred during program processing, it leads to an abnormal end of the program (severity 40). The results of the operation are not valid.
|40||Abnormal End of Program or Function||
The operation has ended, possibly because it was unable to handle invalid data, or possibly because the user ended it.
|50||Abnormal End of Task||The task was ended or was not started. A routing step may have ended abnormally or failed to start, a job-level function may not have been performed as required, or the job may have been ended.|
|60||System Status||A message of this severity is issued only to the system operator. It gives either the status of or a warning about a device, a subsystem, or the whole system.|
|70||Device Integrity||A message of this severity is issued only to the system operator. It indicates that a device is malfunctioning or in some way is no longer operational. You may be able to restore system operation, or the assistance of a service representative may be required.|
|80||System Alert||A message of this severity is issued only to the system operator. It warns of a condition that, although not severe enough to stop the system now, could become more severe unless preventive measures are taken.|
|90||System Integrity||A message of this severity is issued only to the system operator. It describes a condition that renders either a subsystem or the whole system inoperative.|