Is there a way to start Spectrum AlarmNotifier in debug to trouble shoot an issue with Spectrum Alarm Notification (SANM) filter issues?
search cancel

Is there a way to start Spectrum AlarmNotifier in debug to trouble shoot an issue with Spectrum Alarm Notification (SANM) filter issues?


Article ID: 57592


Updated On:


CA Spectrum


If SANM filters are enabled any alarms that don't pass the filters are discarded and not passed to the associated notifier.out log.

Enabling AlarmNotifier tracing is an effective method to determine if conflicting filter logic is preventing the alarms from being sent out via AlarmNotifier.



Any version of Spectrum


Spectrum AlarmNotifier can be started using the "-tl details" parameter to trouble shoot SANM filter issues. The following is the command line syntax for starting AlarmNotifier.

AlarmNotifier [-r resourcefile] [-n application][-tl summary|details] [-tn tracefile] [-ts size]]


-r resourcefileLets you specify a resource file other than the default resource file .alarmrc.

-n application  - Lets you override the application name value that is specified by the APPLICATION parameter in the resource file. You can specify a different name for an AlarmNotifier application instance. This option lets you start multiple instances of AlarmNotifier and associate each of them with a different SANM alarm-filtering policy. If a name is not assigned to the APPLICATION parameter in the resource file, use the -n option at start-up to specify an application name.

-tl summary | details Lets you activate tracing at a specified level, summary or detailed. The default format for an AlarmNotifier trace file is the application name together with the date when the trace file was created.

-tn tracefile   - Lets you specify a trace file name other than the default name, which is provided when only the -tl option is used so use this option in conjunction with -tl. When using the trace file option, the output file is written by default to the $SPECROOT/Notifier/trace directory. To explicitly name an output file and path, use the [-tn filename] option. If <filename> is a relative path, trace output is written to a file that is relative to the current directory. If <filename> is an absolute path, trace output is written to the absolute path.

-ts sizeLets you specify the number of lines in the trace file. Use this option with the -tl option. The application writes this number of lines to the file and then wraps around to the beginning of the file. Entries are numbered sequentially, and an END OF TRACE line follows the last entry. The default number of lines in a trace file is 10000.


The Detailed Trace File

A detailed trace file includes entries for alarms that meet and that do not meet the criteria of a policy. An alarm entry includes the alarm attribute values, which that are compared to the filter parameter values. An arrow symbol under MATCH between ALARM VALUES and FILTER VALUES indicates a match. The arrow is absent if the values do not match.

The following is an example of a trace file that indicates that an alarm passed a policy:

Additional Information

Please reference the "Tracing Policies" section of the documentation for more details:


In the output above the Alarm ID that is given in the debug  (8982) is the Integer Alarm ID.

In order to know what alarm this corresponds to, you will need to enable the Integer Alarm ID in OneClick by following this techdoc.