System Notification
- DarkLight
System Notification
- DarkLight
Article summary
Did you find this summary helpful?
Thank you for your feedback
Campaign Manager is equipped to send Simple Network Management Protocol (SNMP) traps from any configured core components. When a configured event occurs, the respective component generates an alert and sends it to a list of third-party monitoring applications. These alerts include both the event code and a description of the event. You can configure up to three third-party monitoring apps to receive these alerts. Campaign Manager also features a built-in SNMP receiver, which counts as one of the three allowable monitoring apps. Using this built-in app as one of your third-party monitoring apps allows events to be displayed directly on the Campaign Manager home page.
Alarm Detection and Notification
When an Agent detects an alarm condition, it performs the following actions:
Logs information about the time, type, and severity of the condition.
Generates a notification message and sends it to a designated IP host.
Types of SNMP Notifications
SNMP notifications can be sent as either:
Traps: Unreliable messages that do not require acknowledgment of receipt from the SNMP manager.
Informs: Reliable messages that remain in memory until the SNMP manager issues a response, though they consume more system resources than traps.
Configuring SNMP Notifications
To use SNMP notifications, you must specify the recipients. These recipients are the designated locations to which Network Registrar notifications are directed. By default, all notifications are enabled, but no recipients are defined initially. Therefore, no notifications will be sent until you define the recipients.
Notification
The Notification section shows the number of alert events. The Dismiss All icon lets you dismiss all notifications at once. You can use the search box to filter results from the Campaign Name and Alert Event columns based on your search string. Additionally, you can dismiss individual notifications by clicking the Dismiss icon next to each one.
To view notifications, go to Alert > System > Notification.
Settings
Use the Settings tab to control all components and the specific events under each component that you intend to monitor.
Expand any component to view the listed Alert Event Code and Alert Event.
To monitor events in a component, turn the Component Enable switch ON. The application will start monitoring logs for selected events within the component and send notifications only if this switch is turned ON.
To monitor specific events and receive alerts, turn the Enable switch ON for each specific event.
Make sure to complete this setup for all the components you need to monitor.
The following table lists the Monitored Components and their Alert Codes:
Components
Code
Alert Codes From
LCMFeedEngine
2
2.10000
LCMContactRescheduler
3
3.10000
LCMGenericService
4
4.10000
LCMScritpEngine
5
5.10000
LCMReportingService
6
6.10000
LCMLicenseManager
7
7.10000
LCMContactsUploader
8
8.10000
LCMScriptDesigner
9
9.10000
LCMWebservice
10
10.10000
LCMGlobalUploader
12
12.10000
LCMComplianceUploader
13
13.10000
LCMAgentStateMachineFinesse
14
14.10000
LCMTenantService
15
15.10000
LCMITREngine
16
16.10000
LCMIVRThrottle
17
17.10000
LCMReportsByMail
18
18.10000
LCMAlerter
19
19.10000
CRMConnector
20
20.10000
Dialer
21
21.10000
LCMCampaignECT
25
25.10000
LCMEmailEngine
26
26.10000
Email Settings
The alerts listed by the SNMP Receiver can be sent to selected recipients via email, assisting them in troubleshooting specific events.
To send notifications by email:
Go to Alerts > System > Notification > Email Settings.
Activate the Email Notification switch to send notifications by email.
Note:
A restart of the SNMP Receiver service is required only if this switch is turned OFF or ON. No restart is needed for changes made in the following steps.
Enter a value in the Suppress Duplicate Events (In Minutes) field to prevent duplicate alert notifications for the same event within the configured period. For example, if this is set to 15 minutes, an exception logged at 11:30 am will not be logged again if it occurs before 11:45 am.
Enter Recipient Email addresses, separating multiple addresses with a comma. This is a mandatory field. Note that the sender's email address is taken from the Alert section and populated in the From field of the email.
Enter an Email Subject, which will be used as the subject line for email alerts sent out for exceptions. This is also a mandatory field.
Click Save.
Monitoring App
The SNMP Receiver service monitors all components and receives exception data. Based on the Email Settings, this data is then transmitted via email. Configure the Monitoring App to activate the SNMP Receiver service by following these steps:
Go to Alerts > System > Notification > Monitoring App.
Enter the App Name, IP Address, and Port.
Note:
The SNMP Receiver service configuration file contains two properties: SNMPTrapMgrIP and SNMPTrapMgrPort. The IP and Port mentioned in the Monitoring App must match the values configured here.
Click Save.
If you have other apps monitoring the Campaign Manager, you may configure details in App 2 and App 3 as required.
Alert Message Details
When configured third-party apps are monitoring the application, the SNMP alerts are sent out to those apps in the Object ID (OID) format: 1.3.6.1.4.1.52914.8.200020
Number | Label | Details |
1 | ISO | The Group that established this standard. In this case, it is ISO. |
3 | ORG | This is an organization. |
6 | DOD | This indicates the US Department of Defense, the organization that established the earliest form of the Internet. |
1 | Internet | This is the communication Mode, most frequently the Internet. |
4 | Private | This is a device manufacturer’s nature of organization. In this case, it is a private Entity. |
1 | Enterprise | The classification of the private entity. In this case, it is classified as a private enterprise. |
52914 | Enterprise Number | The enterprise number for the product. |
8 | Component ID | The component ID within the product being monitored. In this case, there are three components. Feed Engine (ID 2), Contact Rescheduler (ID 3), and Contact Uploader (ID 8). |
200020 | Event ID | This is the event ID within the component. For all events, the last digit 0 indicates Failure; 1 indicates Success. |
Fields
Fields | Description |
Component Name | Name of the component. |
Alert Event Code | Displays alert even code. |
Alert Event | Displays alert event name. |
Occurred | Displays date and time when an event has occurred. |
Dismiss | Allows you to dismiss a notification. |
Suppress Duplicate Events | It is used to suppress duplicate alert notifications for the same event within the configured period. |
Email Subject | Describes what an email is about. |
Recipient Email | Receiver email address. |
Was this article helpful?