Nodeum Docs
HomepageBlog
  • ✨What is Nodeum?
    • Data Management Software
  • 👣GETTING STARTED
    • Step by Step
  • 🏨ARCHITECTURE
    • Standalone
    • High Availability
    • Fully Scalable & Resilience
  • Install and Deploy Nodeum
    • Platform Support
    • Nodeum v1
      • Ansible based installation
    • Nodeum v2 - Data Mover
      • Ansible based Installation
        • Customize your Installation
      • Docker Based Deployment
    • SLURM Integration
    • Software License Application
  • Interfaces
    • ND Client
    • Console
      • Manual for Administrator
        • Login
        • Dashboard & Reports
        • Catalog
        • Data Mover Management
        • Advanced Task Management
        • Data Container
        • Primary Storage Configuration
        • Pool Management
        • TCO Calculator
        • Toolbox
        • System Settings
          • Information
          • Configuration
          • Date & Time
          • Backup
          • Services
          • Hostname and DNS Configuration
          • NAS Storage Configuration
          • Object Storage Configuration
          • Tape Library Configuration
          • User Management
          • Audits
      • Manual for End User
    • For Developers
      • RESTful API
      • Configuration through RestAPI Console
      • Software Developement Kits (SDK)
      • Nodeum API
        • API Terms of Use
        • release v1.x
        • release v2.x
  • DATA MOVER
    • Policy-Based Task orchestration
      • Pool Management
      • Scheduler
      • Data Integrity
      • Priority Management
      • Filtering (Basic or Advanced)
      • Hook service (callback)
    • Content traceability
    • Metadata Management
  • IDENTITY MANAGEMENT
    • Right - Authentication & Authorization
    • LDAP Plugin for JWT Token
  • Container Configuration
    • Prerequisites
    • About Container
    • Authorization and Authentication
    • Access your Container
  • HYBRID STORAGE MANAGEMENT
    • File System Managment
    • Object Storage Management
      • Customize your S3 connection
    • Tape Library Management
      • Tape Writing Format : LTFS
      • Tape Compression
      • Tape Rehydratation
      • Import a LTFS Tape
      • Task Maintenance for Tapes
  • ⏰Alert & Monitoring
    • Alerts
    • Monitoring
    • Log Management
  • 🏥Recover after Hardware Failure
    • Failover - Active/Passive
    • Failover Procedure - One Site
    • Backup & Restore
  • 🔐Security Guide
    • Advanced Network Configuration
    • Add a SSL Certificate on Web Console
    • Enable SSL Certificate Container accessible on S3 Protocol
  • Compatibility guide
    • Software requirement
    • Supported Storage
  • PRODUCT SPECIFICATIONS
    • Character Set Support
    • Limitations
    • Files Status
    • Task Status
Powered by GitBook
On this page
  • Email Notifications
  • Configuration : own ISP SMTP relay
  • Configuration : Office 365 SMTP relay
  • Configuration : Google Mail SMTP relay
  • Email Recipients
  • SNMP server configuration
  • Trap Destination List
  • Definitions of Level of Severity

Was this helpful?

  1. Alert & Monitoring

Alerts

Last updated 3 months ago

Was this helpful?

The notifications services can be sent by Email or SNMP Trap. Both can be configured to send information and alerts to notify specific misusage or misconfiguration of the software.

Email Notifications

System -> Notifications -> Email Tab

The Email notifications must be filled in on time. The Email recipients is where the different recipient must be configured.

When an event occurs, an automatic email alert is sent to the admin user. The email contains specific details about

Configure notification services and set the severity level for email alerts

Email Recipients

For each user, activate the email address if needed and choose the notification level as defined.

See Point 3 for the level definition.

Configuration : own ISP SMTP relay

Hostname

relay.edpnet.be

From Email address

any type of email address

User Name

empty if your SMTP server doesn’t required any authentication

Password

empty if your SMTP server doesn’t required any authentication

Configuration : Office 365 SMTP relay

Hostname

smtp.office365.com

From Email address

this has to be an email address which is recognized into your Office 365 account.

User Name

This has to be an authorized email address from your Office 365 organization.

Password

This is the password linked to the Username specified below.

Configuration : Google Mail SMTP relay

Hostname

smtp.gmail.com:587

From Email address

this has to be an email address which is recognized into your Google Mail account.

User Name

This has to be an authorized email address in your Google Mail organization.

Password

For passwords, it is required to create an App password in Google portal. This will allows to by pass the 2FA mechanism.

Email Recipients

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 Trap Destination List is the section where the Trap configuration is defined.

SNMP server configuration

System -> Notifications -> SNMP 

The following parameters are required to define the host SNMP configuration:

Version

SNMP version you want to configure.

Community

The community string you want to use; by default public should be used.

System Location

not mandatory but can be useful to define the solution location.

System Contact

not mandatory but can be useful to define the solution point of contact.

Trap Destination List

You can add or remove an SNMP trap destination for SNMP traps and configure threshold and alarms for SNMP traps.

SNMP traps are typically sent to a Network Management System or to an Infrastructure Monitoring System.

Complete the following information

Destination address

Hostname or IP address of the server where the trap has to be sent.

Community

The community string which is configured in your trap handler software.

Version

SNMP version which is supported by your trap handler software.

Notification level

Define the level of severity that will trigger the SNMP trap messages. (see point 3)

Definitions of Level of Severity

0

Message

This is a specific message which is triggered by the system to notify users about an action status.

NB: Require to activate the level 0 to receive the notification when a task is finished.

1

Information

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.

2

Warning

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.

3

Error

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.

4

Severe

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 4). The results of the operation are not valid.

5

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.

6

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.

7

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.

8

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.

9

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.

10

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.

⏰
System Notifications
SNMP