How to exclude Symptom alarms in the Spectrum Web Services output
search cancel

How to exclude Symptom alarms in the Spectrum Web Services output


Article ID: 48750


Updated On:


CA Spectrum


Web Services are used to get the total count of alarms from OneClick using GET or POST methods so that we can pass the same to third party database. By default the symptom alarms are hidden in OneClick but the same are visible in Web Services output when you send a GET or POST request to SpectroSERVER.

This solution helps you with filtering these symptom alarms from the output of Web Service.


Release: Any


The following REST verbs are supported in the CA Spectrum Web Services API. All operations respect standard CA Spectrum user security.

  • POST (Create)

  • GET (Read)

  • PUT (Update)

  • DELETE (Delete)

We use the Alarms resource to read, modify, and delete CA Spectrum alarms. Asynchronous responses are supported.

Base URL


This solution will use the Get Tunneling (POST) to filter the Symptom alarms. All the symptom alarms will have the "CauseCount" value greater than ' 1 '. In this solution you will use a condition in the xml to get the actual count of alarms in Oneclick. All the alarms reporting an issue will have the "CauseCount" equals to '0'.

This Solution uses Google Chrome rest client to execute the xml file.


  1. Download Google Chrome

  2. Once done open Google chrome -> Web store

  3. Search for Simple rest client .It will get added automatically to Google Chrome if you follow the actions on the window.

  4. Now an icon will appear on top right corner in Google Chrome which is simple rest client.

  5. Follow these fields in the client

     URL: Give http://<OC hostname:port> /spectrum/restful/alarms? Method : POST Headers: content-type:application/xml Data: <?xml version="1.0" encoding="UTF-8"?><!-- CA Technologies, Inc. One CA Plaza Islandia, NY 11749 USA Copyright (c) 2012 CA Technologies, Inc. All rights reserved.
     IN NO EVENT SHALL CA TECHNOLOGIES INCORPORATED BE LIABLE FOR        ANY INCIDENTAL, INDIRECT, SPECIAL, OR CONSEQUENTIAL DAMAGES  WHATSOEVER (INCLUDING BUT NOT LIMITED TO LOST PROFITS) ARISING OUT OF OR RELATED TO THIS SOFTWARE, EVEN IF CA TECHNOLOGIES INCORPORATED HAS BEEN ADVISED OF, KNOWN, OR SHOULD HAVE KNOWN, THE POSSIBILITY OF SUCH DAMAGES.  --> 	ENVIRONMENT PROFILE EXISTS = <rs:alarm-request throttlesize="10" 	xmlns:rs="" 	xmlns:xsi="" 	xsi:schemaLocation=" ../../../xsd/Request.xsd"><!--   This xml can be posted to the Alarms URL to obtain 	attributes on the specified alarms --><!-- Attributes of Interest --><rs:attribute-filter><search-criteria 	xmlns=""><filtered-models><equals><attribute id="0x12a07"><value>0</value></attribute></equals></filtered-models></search-criteria></rs:attribute-filter><rs:requested-attribute id="0x11f53" /><rs:requested-attribute id="0x10000" /><rs:requested-attribute id="0x11f56" /><rs:requested-attribute id="0x12b4c" /><rs:requested-attribute id="0x11f4d"/><!-- Alarms of Interest --></rs:alarm-request>Click on send.

The output is displayed in the data column at the bottom of the same page. This contains the actual alarms displayed after filtering the symptom alarms. The output can be fed into the third part database or dashboard with some sort of scripting.