How-To Guides
...
Configuration Guides
Configure Monitoring & Alarm

Alarm Configuration

5min

Setting Alarm Thresholds

You can see the default threshold values for CPU, Memory, Storage, License Count, Time to License Expiry, and Latency in Alarm Configuration. Change these values as desired.

Document image


Setting Mail Notifications

To add an alarm notification:

  1. Open the Mail Notification tab.
  2. Define the alarms that should be included in the notification.
  3. Write the email address where you want to receive the notification.

Should the defined alarm case occurs, a notification mail is sent to the given email address.

Document image


List of Available Alarm Types

Alarm Type

Definition

CPU Critical

This alarm is triggered if CPU usage is higher than the Critical CPU Threshold.

CPU Major

This alarm is triggered if CPU usage is higher than the Major CPU Threshold.

CPU Minor

This alarm is triggered if CPU usage is higher than the Minor CPU Threshold.

Latency Critical

This alarm is triggered if Latency is higher than the Critical Latency Threshold.

Latency Major

This alarm is triggered if Latency is higher than Major Latency Threshold.

Latency Minor

This alarm is triggered if Latency is higher than Minor Latency Threshold.

LDAP Server Connection Job status Critical

This alarm is triggered if there is a connection problem to the LDAP server.

License Count Critical

This alarm is triggered if license usage is higher than the defined Critical License Count.

License Count Major

This alarm is triggered if license usage is higher than the defined Major License Count.

License Count Minor

This alarm is triggered if license usage is higher than the defined Minor License Count.

License Expiry Critical

This alarm is triggered if the License Expiration time is sooner than the defined Critical Time to License Expiry value.

License Expiry Major

This alarm is triggered if the License Expiration time is sooner than the defined Major Time to License Expiry value.

License Expiry Minor

This alarm is triggered if the License Expiration time is sooner than the defined Minor Time to License Expiry value.

Memory Critical

This alarm is triggered if Memory usage is higher than the Critical Memory Threshold.

Memory Major

This alarm is triggered if Memory usage is higher than Major Memory Threshold.

Memory Minor

This alarm is triggered if Memory usage is higher than the Minor Memory Threshold.

Database Replication Error Critical

This alarm is triggered if there is an error generating in the replication tool’s logs.

Database Replication Service Critical

This alarm is triggered if the replication tool is down.

HTTP Proxy Service Critical

This alarm is triggered if the HTTP Proxy service is down.

LDAP Device Import Job status Critical

This alarm is triggered if LDAP Device Import Job could not be executed.

LDAP User Import Job status Critical

This alarm is triggered if LDAP User Import Job could not be executed.

Mobile Server Service Critical

This alarm is triggered if the Mobile Server service is down.

Time Synchronization Service Critical

This alarm is triggered if the Time Sync service(NTP) is down.

PostgreSQL Service Critical

This alarm is triggered if the Database service(PostgreSQL) is down.

Radius Service Critical

This alarm is triggered if the Radius service is down.

RDP Proxy Service Critical

This alarm is triggered if the RDP Proxy service (guacd) is down.

SAPM Change Password Job status Critical

This alarm is triggered if an error generates during the SAPM Change Password Job.

SAPM Password Reservation Job status Critical

This alarm is triggered if an error generates during the SAPM Password Reservation Job.

SFTP Service Critical

This alarm is triggered if the SFTP Proxy service is down.

SMTP Server Connection status Critical

This alarm is triggered if the Integrated mail server is not accessible.

SQL Proxy Service Critical

This alarm is triggered if the SQL Proxy service is down.

SSH Proxy Service Critical

This alarm is triggered if the SSH Proxy service is down.

Superset Service status Critical

This alarm is triggered if the superset service(reporting) is down.

TACACS Service Critical

This alarm is triggered if the TACACS service is down.

Web Gui Service Critical

This alarm is triggered if the WebGUI service is down.

Storage Critical

This alarm is triggered if disk space usage is higher than the Critical Memory Threshold.

Storage Major

This alarm is triggered if disk space usage is higher than Major Storage Threshold.

Storage Minor

This alarm is triggered if disk space usage is higher than Minor Storage Threshold.

Unreachable Within Critical

This alarm is triggered if a registered instance is not reachable after the Critical Unreachable Within Time.

Unreachable Within Major

This alarm is triggered if a registered instance is not reachable after the Major Unreachable Within Time.

Unreachable Within Minor

This alarm is triggered if a registered instance is not reachable after the Minor Unreachable Within Time.

Alarm SNMP Configurations

In order to fire SNMP traps to a centralized SNMP server, you need to configure the following SNMP parameters. This feature is deactivated by default, so you need to add the following parameters to System Config Parameters to enable SNMP traps for alarm generation.

After defining these parameters, copy the KRON-MIB.txt file from /u01/netright-tomcat/netright/scripts/ path to your SNMP server. Kron PAM sends alarm IDs to the SNMP server. SNMP server can recognize the sent alarm IDs by this MIB file.

Parameter Name

Parameter Value

snmp.target.ip

Target IP to send the SNMP trap to. If not defined, “localhost” is used as the default target IP to send the traps.

snmp.target.port

Target port of the target IP to send the SNMP trap to. If not defined, “162” is used as the default port.

snmp.community.string

Define the preferred community string. Otherwise, it defaults to “public”.

monitoring.snmp.trap.enabled

Set to true to enable sending SNMP traps. It defaults to “false”.

Document image