Fix Alarm filtering using REST API

Idea created by franktonjes Champion on Mar 1, 2016
    New
    Score7
    • lutelewis
    • franktonjes
    • Prashantha.Nagaraju
    • Frank_Elliger
    • rosjo12
    • ElioteArg
    • mwegner

    Currently there is a bug/defect that you can't filter out Spectrum alarms using REST which are not dynamic alarm titles.

     

    e.g.: We have some traps coming from Cisco Prime/Zabbix (using SBGW) which when I do something like:

     

    <?xml version="1.0" encoding="UTF-8"?>   <rs:alarm-request throttlesize="1000"   xmlns:rs="http://www.ca.com/spectrum/restful/schema/request"   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"   xsi:schemaLocation="http://www.ca.com/spectrum/restful/schema/request ../../../xsd/Request.xsd">     <rs:attribute-filter>     <search-criteria       xmlns="http://www.ca.com/spectrum/restful/schema/filter">         <filtered-models>           <has-substring>             <attribute id="0x12b4c">               <value>L2TP</value>             </attribute>           </has-substring>         </filtered-models>     </search-criteria>   </rs:attribute-filter>     <rs:requested-attribute id="0x11f9c"/>   <rs:requested-attribute id="0x12b4c"/>   <rs:requested-attribute id="0x11fc5"/>   </rs:alarm-request>

     

    This works and displays the alarms fine if the text is from Cisco Prime/Zabbix alarms. If we change the 'L2TP' to some alarm that is built-into spectrum e.g.: 'MANAGEMENT AGENT LOST' then it doesn't work. So it filters dynamic alarms from other NMS's but not it's own!

     

    I see this as a defect and would like this to be fixed. We would like to use this to create different views based on user filters but can't because the root cause of problem is due to the design of Spectrum in that it don't populate static alarm titles to an attribute on the SS so they are not available to be filtered on. Only dynamic alarms are populated to an attribute so static titles are not available on the SS when queried from rest.

     

    You can run a query to get ALL alarms from every landscape in a domain and filter it - but this chews up resources and takes away the power of the API of being able to query it for only information and attributes you want.

     

    I have raised a ticket and have been advised to raise an enhancement (even though I see this more as a bug or defect) - Ticket Ref is: 00262158: REST QUERY HELP