Configure notifications for events that come from a data source to the Event Manager.
Configure notifications for events that come from a data source to the Event Manager. The incoming events are evaluated against the conditions that you configure for the notification criteria. Only when the criteria are met does Event Manager take a notification action. If an event does not trigger a notification, you can still display the event in the Event List.
A user only configures and receives notifications for events for an item in a group to which the user has access.
Consider the following information:
- Users cannot see the notifications of other users.
- The action to delete event notifications does not affect the actual or future events.
When you configure notifications, you can specify the following actions.
Send email notifications to one or more recipients when an event is raised or cleared. The email provides a link to the context page for the device or component that triggered the alarm.Email
To use the hostname in the URL instead of the IP address of the
CA Performance Centerhost, configure the
Web Site Host. For more information, see Update Performance Center Website Settings.
Supported roles:Users with a role that contains the Create Notifications role right and Event Manager access can configure email notifications. However, the Administrator role must first specify an SMTP server.
In the Email tab, select Enable, and configure the email notification settings.
Send trap notifications to fault or network management system (NMS) in your environment, such as
CA Spectrumcan receive traps, this method is not the preferred method to integrate with
CA Spectrum. For more information, see the CA Spectrum documentation.
Create an SNMP profile with the outgoing trap port (typically 162) before creating the notification.
Supported roles:Users with the Administrator role (global administrators) can configure trap notifications. Administrators must also have product privileges to Event Manager and data sources that create events.
The trap receivers must be preconfigured to receive traps. Each destination can have its own configuration regarding SNMP community and IPV4 destination. To receive and decrypt SNMPv3 traps, the SNMP profile for the trap receiver should match this notification configuration. For more information, see SNMP Profiles. For more information about trap formats, see the corresponding NMS documentation for your trap receiver.
Define a script. Scripts can store events to a database, forward notifications to multiple systems, send specific types of notifications to some specific system, and so on. You can log output from scripts that you own. Script return codes are logged in the standard PC log file. Script notification actions are executed serially to ensure that sets are processed before clears. If the queue of unprocessed script notification actions exceeds a certain size (5000 by default), any new incoming script notification actions are dropped. An event is generated when events start dropping and when the processing of new script notification actions restarts. If a script takes too long to complete execution (300 seconds by default), it is killed and an event is generated. The script notification action events are generated on the Data Aggregator item in
CA Performance Center. For information about changing event properties that are related to script notification actions, see Change Event Properties.
Store scripts in the
The following video examines automatic script execution:
The following parameters are automatically passed to script notification actions:
Event-specific properties are also available and prefixed with "
CA Performance CenterIDs. The script parameters and notifications are always in English regardless of the
CA Performance Centerlanguage.
Supported roles:Users with a role that contains the Create Notifications role right can create or edit script notification actions.
You can define a script that prints environment variables to a file and a CPU utilization threshold event can trigger the script.
- Define the followingprintenv.shscript in the/opt/CA/PerformanceCenter/NotificationScripts/directory:printenv > /opt/CA/PerformanceCenter/NotificationScripts/out.txt
- Make the script executable by running the following command:chmod u+x printenv.sh
- Configure notifications so that a CPU utilization threshold event triggers theprintenv.shscript.The script creates the following output:CAPM_EventCategory=PERFORMANCECAPM_EvProp__Severity=1CAPM_IPAddress=10.253.223.1CAPM_ItemNameAlias=cisco2621-10.253.223.1CAPM_EvProp_AlarmRuleID=5,313CAPM_EvProp_AlarmAggregationMethod=No AggregationCAPM_ItemId=118CAPM_EvProp_AlarmProfileName=Test cpuCAPM_ItemDesc=Cisco Internetwork Operating System Software ^MIOS (tm) C2600 Software (C2600-IK9O3S3-M), Version 12.3(9), RELEASE SOFTWARE (fc2)^MCopyright (c) 1986-2004 by cisco Systems, Inc.^MCompiled Fri 14-May-04 14:37 by dchihCAPM_EventState=OPENEDCAPM_EventType=ThresholdViolationPWD=/opt/CA/PerformanceCenter/EM/binCAPM_EventDesc=A Threshold Violation event has been raised. (Profile Name: Test cpu, Rule Name: test cpu)CAPM_ItemName=CPU 2CAPM_ItemParentId=118CAPM_EvProp_ThresholdProfileFolderId=5,311CAPM_EvProp_AlarmDuration=60CAPM_EvProp_AlarmProfileId=5,314CAPM_EvProp_AlarmViolationRuleDetail=Utilization > 50.0SHLVL=1CAPM_EvProp__Alarm_ID=1500CAPM_ItemType=DEVICECAPM_ItemParentName=cisco2621-10.253.223.1CAPM_EventSeverity=MAJORCAPM_EvProp_AlarmMetricFamilyName=CPUCAPM_EventOccurredOn=Thu May 24 10:39:00 EDT 2018CAPM_EvProp_AlarmRuleName=test cpuCAPM_EventDataSource=Data [email protected]CAPM_ItemUrl=http://10.237.15.180:8181/pc/desktop/page?pg=r&DeviceID=118&timeRange=-1&startTime=2018-05-24+10%3A09+America%2FNew_York&endTime=2018-05-24+11%3A09+America%2FNew_YorkCAPM_ItemSubtype=routerCAPM_EvProp_AlarmWindow=60CAPM_EventSubType=Raised_=/usr/bin/printenvIf an error occurs during the script execution, the errors are logged in thePC_Install_Directory/PerformanceCenter/EM/logs/EMService.log
You can define a script that prints environment variables to a file and any device life cycle change can trigger the script.
- Define the followingprintenv.shscript in the
directory:/opt/CA/PerformanceCenter/NotificationScripts/printenv > /opt/CA/PerformanceCenter/NotificationScripts/env.txt
- Make the script executable:chmod u+x printenv.sh
- Configure notifications so that any device life cycle change event triggers theprintenv.shscript.The script creates the following output:CAPM_EventCategory=CONFIGCAPM_EvProp__Severity=UnknownCAPM_IPAddress=126.96.36.199CAPM_ItemNameAlias=188.8.131.52 - aliasCAPM_EvProp_User=adminCAPM_ItemId=110CAPM_EvProp_CurrState=RETIREDCAPM_EvProp_PrevState=ACTIVECAPM_ItemDesc=RS 38000 - Riverstone Networks, Inc. Firmware Version: 184.108.40.206 PROM Version: prom-220.127.116.11CAPM_EventState=CLOSEDCAPM_EventType=LifeCyclePWD=/opt/CA/PerformanceCenter/EM/binCAPM_EventDesc=LifeCycle - ChangeCAPM_ItemName=rs38000-96.2CAPM_ItemParentId=110SHLVL=1CAPM_ItemType=DEVICECAPM_ItemParentName=rs38000-96.2CAPM_EventSeverity=CAPM_EventOccurredOn=Mon Dec 18 16:20:58 EST 2017CAPM_EventDataSource=CA Performance CenterCAPM_ItemUrl=http://10.237.10.219:8181/pc/desktop/page?pg=r&DeviceID=110&timeRange=-1&startTime=2017-12-18+15%3A50+America%2FNew_York&endTime=2017-12-18+16%3A50+America%2FNew_YorkCAPM_ItemSubtype=routerCAPM_EventSubType=Change_=/usr/bin/printenvIf an error occurs during the script execution, the errors are logged in thePC_Install_Directory/PerformanceCenter/EM/logs/EMService.log
To send a message that is related to events automatically, configure a notification.
Follow these steps:
- Do one of the following tasks:
- Hover overAdministration, and clickConfiguration Settings: Notifications.
- Click the name of your user account in the upper-right corner and clickManage Notifications.
- Specify a name and description, and clickNext.
- Select the groups that generate events to trigger the notification, and clickNext.
- Select conditions for the notification, and clickNext.
- Specify the notification actions:
- Send email notifications.To include the device name for events that are triggered on components, use the Item Parent Name property.To create or update a notification email template, select Save or Update Email Template. Changes to templates do not affect existing messages.
- TrapSend trap notifications. Multiple destinations are supported, but the first destination is required.Two MIB choices are available in the Notifications wizard to provide compatibility for existing customers.
- ScriptSpecify the script file name. All scripts must be executable.You can use a script in another language like Python or Perl.Store scripts in the/opt/CA/PerformanceCenter/NotificationScriptsdirectory.
- ClickNext.CA Performance Managementsaves the notification and sends messages when the selected conditions occur.
Administrators can view, create, or delete notifications from the Administration, Notifications menu in the user interface. The Notifications option only appears when Event Manager is enabled and in a synchronized state of Available.
As a Default Tenant Administrator, you can work in a real user context to create a notification for a tenant administrator or tenant user. Log in as a tenant administrator or tenant user. The Default Tenant administrator can also administer the tenant, and then proxy to the user to create a tenant-scoped notification.
Users can create email notifications by clicking the name of their user account in the upper-right corner and clicking Manage Notifications.